Learn how to setup a Bugsnag integration with Bitbucket Issues.
The Bitbucket Issues integration allows an issue to be created in Bitbucket for errors that are reported to Bugsnag.
In Bugsnag, set up the Bitbucket Issues integration from Project Settings > Issue tracker, then select Bitbucket Issues from the Available integrations section.
Multiple Bitbucket integrations can be configured for Bugsnag projects which allows different issues to be created in different repositories. Contact us to gain access to this feature.
Issues 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.
With the Create an issue toggle selected, create a new linked issue by selecting the issue tracker from the dropdown and selecting the Create issue button.
Alternatively, select Link to existing issue to add an issue using the URL.
You can choose one of two ways to allow Bugsnag to automatically create an issue.
Filters can be configured to define which errors should automatically create an issue in Bitbucket Issues. 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 Bitbucket Issues integration has two way sync capabilities which means that errors in Bugsnag can be kept in sync with the linked issue in Bitbucket.
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 Bitbucket 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 Bitbucket issue transitions to or away from certain states.
With the default configuration a linked Bugsnag error will be marked as fixed when the Bitbucket issue is transitioned to either Resolved or Closed. Correspondingly when a Bitbucket issue is transitioned away from Resolved or Closed to any other state, the linked Bugsnag error will be reopened.
Multiple states can be selected in both lists.
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.