Exporting Issues - Simplified Explanation
Exporting Issues - Comprehensive Explanation
In certain cases, you may want to export the issue reports to an external file or your Bug Tracking System. For that, you need to use the Export feature briefly mentioned in the previous course.
There are a number of methods for exporting issues from the Applause platform to a third-party Bug Tracking System (BTS) like JIRA, Mantis or Bugzilla. In order to export bugs automatically or manually, BTS integration must be set up when creating or editing the Product associated with the test cycle.
This feature can be enabled/disabled when creating or editing a test cycle.
Note: Remember to save the test cycle after editing is completed.
You can export issue reports manually using two options, which will be explained in this section.
In certain cases, you may want to export the results to an external CSV file. The file may be then used to upload into a different system, recordkeeping and/or for further analysis.
When an issue is set to be exported to a Bug Tracking System, the issue’s "Export" field will be updated with the following possible values.
Note: If the bug belongs to a product that’s associated with multiple BTS Integration Connectors, you may select the connector to be used for the export. For your convenience, the default Connector will already be pre-selected.
This indicates that the issue is in the process of being exported. However, if this value seems ‘stuck’ on Queued, this indicates that either integration hasn’t been configured with a BTS or that there is a problem with the current configuration.
Following a successful export, the corresponding BTS issue ID will be displayed allowing for easy look-up within the BTS, e.g., “ABC-123 – SENT”.
The issue export failed, due to either a configuration or a connection issue. You may fix the issue and retry.
For Jira connectors (only), the BTS ID will serve as a hyperlink, allowing you to open the Jira issue directly from the Applause platform.