Using Bugsnag with your issue tracker


SKIP AHEAD TO

Integrate Bugsnag with your issue tracker

Bugsnag integrates with the most popularly used issue trackers. In this guide, learn why it’s valuable to integrate Bugsnag with your tools and some best practices for getting the most out the integration. See all integrations.  

Why integrate Bugsnag and my issue tracker?  

Errors are dynamic — their states frequently change with new releases or your own progress bug fixing, but tracking these changes in multiple tools can be a challenge. When you integrate Bugsnag with your issue tracker, some of this work is automated for you. It also makes your error data immediately actionable, giving you a clear path forward anytime you identify a bug that needs fixing.

Simply, create an issue for your team with a single click from the Bugsnag dashboard to get it moved into your debugging workflow.

  • Save time context-switching between applications
  • Avoid manual issue/ticket creation
  • Stay accountable for bugs that need fixing
  • Establish a clear debugging process
Integrating Bugsnag with your issue tracker is simple and easy and will only take you a few minutes. For step-by-step instructions, please visit our documentation.

Once integrated, you can:

  • Create a corresponding issue/ticket for any error in the dashboard
  • Link the error to an existing issue/ticket in your issue tracker  



Tips and Tricks  

Tip 1: Save time with two-way sync

Bugsnag’s two-way sync integrations ensure your error statuses are up to date across your tools automatically. You can update the status in Bugsnag and it will be reflected in your issue tracker. Alternatively, you can update the status in your issue tracker which will reflect the change in Bugsnag. This makes staying up to date on the status of errors much easier.

  • Mark an error fixed it Bugsnag. The ticket in your issue tracker is closed or resolved automatically.
  • Mark an error resolved in your issue tracker. The error in Bugsnag is marked ‘Fixed’ automatically.  
  • Bugsnag detects a regression in a new application release and reopens the error. The ticket in your issue tracker automatically reopens.

Tip 2: Establish a clear debugging process

Once you’ve integrated Bugsnag and your issue tracker, take some time to establish a clear process for using the integration. Here are some things to consider when establishing the process:

  • Who will be responsible for triaging errors on a regular basis? Will you have a bug rotation? Should triage in Bugsnag happen daily or weekly?
  • Keep your inbox focused by taking action on all incoming errors. Bugsnag has workflow features to help you move errors through different statuses. Create issues for the errors that need fixing, but either Snooze, Ignore, or Fix everything else to keep your inbox actionable.
  • Keep error statuses updated. When errors that have been prioritized are fixed, be sure to update the status in either Bugsnag or your issue tracker.

Tip 3: Get accountable and assign errors to your teammates

Make sure no important errors slip through the cracks. Once you’ve created an issue or ticket, you can use the Assign function in Bugsnag to make sure the relevant person sees the bug. They’ll be able to go to the ticket directly from the Bugsnag error.

Using Bugsnag with your issue tracker

Speaker(s)
No items found.

Using Bugsnag with your issue tracker

Download PDF
LISTEN ON Host website