Learn how to setup a Bugsnag integration with Jira.
The Jira integration allows an issue to be created in Jira for errors that are reported to Bugsnag.
In Bugsnag, set up the Jira integration from Project Settings > Issue tracker, then select Jira from the Available integrations section.
Configuration of the integration requires a Jira instance URL, project prefix key, email and API Token.
See Access permissions for a list of required permissions for the Jira user.
Isuess can be create manually or automatically. Once an error has a linked issue, a comment will be added to the issue when the error changes between open and fixed, and when a comment is added to the error in Bugsnag.
Create an issue manually by clicking on the ! icon on the Bugsnag dashboard.
To link an error to an existing issue, select Link to an existing Jira issue and enter the issue’s URL.
An issue can be created automatically when a new error is received. Select Create an issue for each new error.
Filters can be configured to define which errors should automatically create an issue in Jira. An issue will be created the first time an error occurs in a matching release stage, if there is no existing issue.
Basic filtering is provided for severity, type, and release stage.
Advanced filtering leverages Bookmarks to enable you to create issues based on any field you can filter on using the filter bar. Advanced filtering is available on Standard and Enterprise plans.
The Jira integration has two way sync capabilities which means that errors in Bugsnag can be kept in sync with the linked issue in Jira.
To enable two-way sync select Two-way sync and enable the automations you require.
The first two settings define the state that the linked Jira issue should be transitioned to when an error in Bugsnag is marked as fixed or when it is reopened.
The last two settings define the behavior when a Jira issue transitions to or away from certain states.
With the default configuration a linked Bugsnag error will be marked as fixed when the JIRA issue is transitioned to either Closed or Resolved. Correspondingly when a Jira issue is transitioned away from Closed or Resolved to any other state, the linked Bugsnag error will be reopened.
As Jira workflow states are entirely configurable, any state names can be entered and separated by commas.
The user credentials must have the following permissions:
If enabling two-way sync, the ‘Jira Administrators’ global permission is required for automatic configuration. A user without the 'Jira Administrators’ global permission can be used for two-way sync but a Jira webhook will need to be created manually by a Jira administrator. Instructions on how to do this are presented when setting up two-way sync.
If your server’s security policy denies access from external IP addresses and websites, you will need to allow access to Bugsnag’s IP addresses below.