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.
Set up the Bitbucket Issues integration by selecting it from the Available integrations section of the settings (Project Settings -> Configure Integrations -> Available Integrations).
The integration requires a Bitbucket username and password, and the Bitbucket repository name.
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 -> Bitbucket Issues -> 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 Bitbucket 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 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 the following options in the Automation section of the settings (Project Settings -> Configure Integrations -> Bitbucket Issues -> Automation):
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.