Part of lp.bugs.externalbugtracker View In Hierarchy
ExternalBugTracker for dealing with Mantis instances.
For a list of tested Mantis instances and their behaviour when exported from, see:
|Method||csv_data||Attempt to retrieve a CSV export from the remote server.|
|Method||canUseCSVExports||Return True if a Mantis instance supports CSV exports.|
|Method||_checkForApplicationError||If Mantis does not find the bug it still returns a 200 OK|
|Method||_findValueRightOfKey||Scrape a value from a Mantis bug view page where the value|
If the export fails (i.e. the response is 0-length), None will be returned.
If the Mantis instance cannot or does not support CSV exports, False will be returned.
This method is overridden so that it can take into account the fact that not all Mantis instances support CSV exports. In those cases all bugs will be imported individually, regardless of how many there are.
If there is no error, None is returned.
If there is an error, a 2-tuple of (code, message) is returned, both unicode strings.
Scrape a value from a Mantis bug view page where the value is displayed to the right of the key. The Mantis bug view page uses HTML tables for both layout and representing tabular data, often within the same table. This method assumes that the key and value are on the same row, adjacent to one another, with the key preceding the value: ... <td>Key</td> <td>Value</td> ... This method does not compensate for colspan or rowspan.
This method is implemented here as a stub to ensure that existing functionality is preserved. As a result, UNKNOWN_REMOTE_IMPORTANCE will always be returned.
This method is implemented here as a stub to ensure that existing functionality is preserved. As a result, BugTaskImportance.UNKNOWN will always be returned.