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 by selecting it from the Available integrations section of the settings (Project Settings -> Configure Integrations -> Available Integrations).
The integration requires a Jira instance URL, project prefix key, username and password.
Alternatively you can create an API Token for the Atlassian ID and use it instead of your password.
See Access permissions for a list of required permissions for the Jira user.
An issue can be created automatically when a new error occurs by enabling it in the Automation section of the settings (Project Settings -> Configure Integrations -> Jira -> Automation)
or 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.
Once an error has been linked to an issue, we will add a note to the issue when the error changes between open and fixed, and when a user adds a comment to the error.
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 the following options in the Automation section of the settings (Project Settings -> Configure Integrations -> Jira -> Automation):
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 policy denies access to external IP addresses and websites, you will need to whitelist the IP addresses below. A whitelist provides access to designated IP addresses and sites that would otherwise be prevented by your security policy.