For basic integration information, please see: ‘Integrating With Third-Party Bug Tracking Systems’.
Applause supports the following versions of JIRA:
- JIRA (REST API) Versions 5.0 or later
Integration with JIRA Implementation
Select the ‘JIRA v5+‘ option in the ‘Connector Type‘ menu.
Helpful Hint: For easier tracking, create a new user within your user system with Applause in the name. This will help you quickly locate bugs exported from Applause into JIRA. It is important to assign project visibility in JIRA to the account being used for the connection in order for bugs to appear.
After selecting JIRA for your new connector, you will be presented with a number of fields.
- URL: Configure your web-based access to JIRA.
- User: Case sensitive. Requires the username to have create and save permissions within the JIRA system.
- PLEASE NOTE: If using an Atlassian API token for authentication, you must use the associated email address for the user.
- PLEASE NOTE: Newer JIRA instances may be using ATLASSIAN accounts, instead of JIRA ones. The username for that is typically the email address minus the “@###.com”. If still not working, go to your JIRA profile page and look for it there. JIRA usernames are seldom an email address.
- Password/API Token: Case sensitive.
- Customers using JIRA Cloud will need to provide an API Token in this field. All other JIRA users will use a password.
- Jira Project Key (v5+): Case sensitive, and needs to exist within the JIRA system prior to seeing up a new connector. Assign where you would like Applause SDK-exported bugs to be located in the JIRA system.
- Issue Type: The default issue type for bugs sent from the Applause platform.
‘Labels‘ JIRA field: If you’d like to export particular labels for a product, simply write the label(s) (space-separated —- therefore 2-word labels are not possible) in the ‘Labels’ field mapping field on the product’s BTS connector setup screen.
Please Note: Jira’s new view (2019) encodes URLs with special characters. This will affect many Applause bug attachment URL links and cause an error upon clicking the link from within your Jira’s new view of an exported bug. There are 2 workaround options you can do … 1.) Go back to the old Jira view. – OR – 2.) Copy/paste the attachment URL in the bug to a new browser tab w/o directly clicking on the link.
Lastly, if your BTS server uses the TLS SNI (Server Name Indication) extension and you run into errors, enable this setting on your product’s BTS connector setup and test/refresh your connection.
Next: Instructions for setting up Two-way Jira Integration.
For information on further customizing your BTS integration, please see: “Working With Bug Tracking System (BTS) Integration Connectors”