For information on how to begin setting up integration with your own BTS implementation, please see the following article: How to Integrate With Bug Tracking Systems
For specific information about configuring integration with a particular BTS, please see any of the following articles:
- JIRA (v.5.0 or later)
- Mantis Bug Tracking (v.1.2.x or later)
- Azure DevOps (formally Microsoft TFS / Visual Studio Team Services)
- Pivotal Tracker
- Generic (email)
- To edit a pre-existing connector: click on the pencil icon next to the connect details label.
- Test/Refresh Connection: After selecting your BTS system when adding a new connector and once you’ve entered in all required fields, or, if you’ve updated information about your BTS connector: (e.g. URL, Username, Password, Project Key), click the ‘Test Connection’ (if new) or ‘Refresh Connector’ (if editing an existing) button. This will allow Applause to (re)test the connection and pull in any custom fields and custom values that may exist within your BTS implementation.
- Required vs Optional Fields: When a connector is selected, and the ‘Refresh Connection’ button clicked, Applause will auto populate the panel with all required fields for the selected BTS. Required fields can NOT be removed. Option fields can be removed by clicking on the ‘x‘ icon to the right of that field.
Fields, Values, and Mappings
The Applause BTS Integration panel allows users to target any and all fields currently configured within their BTS system. Users can also send default Applause values, or, their own custom BTS values. Finally, users can also create custom field mappings and automations.
Adding fields is very easy. Simply click on the ‘+ Add Field’ button, and select from a list of available fields.
Fields are then added to the Field Configuration section of the BTS integration panel.
Note: If you have recently added new fields to your JIRA implementation but do not see them listed as options, you may need to refresh the connector’s database by clicking the ‘Refresh Connector’ button.
Note: As a reminder, any fields that have an ‘x‘ icon to the right of them are optional and can be deleted. Fields lacking the icon are required and can not be removed.
To send a static value for a particular field, simply click on the drop down menu and select the static value you would like to post to that field. Note that this value will be sent for ALL bugs sent from Applause. If an option is NOT selected, Applause will default to whatever mapping is currently configured in the target BTS.
Note: If you have recently added new value options to your JIRA implementation but do not see them listed as options for a particular field, you may need to refresh the connector’s database by clicking the ‘Refresh Connector’ button.
Some fields support dynamic values. Dynamic values are pulled from the corresponding field in the Applause platform. In the below example, the current value of the Product Version ID within the Applause platform, will be sent to the JIRA field ‘uTest Environments’.
Creating Custom Mappings with the [Custom…] Option
In addition to any custom values published into the value option menu for each field, there is also a [Custom…] option. This option will allow you to create more advanced mappings.
In this example, the Applause user wants to customize the bugs Applause sends to their JIRA implementation. They want to customize it in two ways:
1) They want to set up automated routings so bugs of a particular severity level are automatically assigned to specific engineers within JIRA.
2) They want to Customize the Severity value mappings to better match the Applause defaults with their own Severity rating system.
Customizing Assignment Automation
They start by selecting the [Custom…] option in the Assignee menu. The default Applause values (meaning, the values used within the Applause platform) are published on the left of the selection menus). Note that the lack of an ‘x’ icon to the right of the menu indicates this is a required field.
Choose Field: They select the field from which they want to pull target values from.
Next, they simply select the desired targets for each of the various bug severity options. In the below example, all bugs with a ‘Critical’ rating will be sent to JIRA automatically assigned to ‘Administrator’.
Customizing Severity Values
Next, they want to make sure that the bugs’ severity values are being correctly translated from the Applause platform to their own BTS. The presence of an ‘x’ icon to the right of the menu indicates that the field is optional and does not need to be sent from the Applause platform.
They select the [Custom…] option from the Priority menu.
Similar to the above customization example, they simply select an appropriate custom value for each of the default Applause severity ratings.
Finally ending up with the below custom configuration. For example, all bugs rated as ‘Critical’ in Applause, will be posted to their BTS implementation as a ‘Blocker (1)’. All ‘High’ rated bugs will be posted as ‘Critical (2)’.