Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
What you'll learn
Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
Fill out the form on this page to gain access to the free on-demand talk.
Having a solid workflow in place for debugging can make the process much more swift, simple, and straightforward. Many engineers find debugging to be a burdensome task, so having a workflow and process in place can relieve some of the mental load associated with this task.
Establish a process
Decide how to triage and move bugs into your workflow
Will you have a weekly bug rotation? Or maybe you’ll assign someone to be the Bug Warrior 💪 for an entire sprint? Making one person responsible for triaging and moving bugs into your workflow for a set period of time makes it less likely that harmful bugs will go unnoticed. It’s also smart to have as many of your teammates on the rotation as possible so that everyone can see the impact of bugs and feel the pain that users feel when they encounter errors.
Tip: The engineer on bug duty doesn’t necessarily need to be the person fixing the bug. Many times they won’t actually be the best person to do it if they weren’t the last one to change the code. However, having a set of eyes on those incoming bugs will make sure nothing is slipping through the cracks.
Bookmark error segments for debugging
Create a bookmarked searches and share them across your team so that anyone on bug duty can go straight to the most relevant errors with a single-click. This will save time recreating the same searches over and over again.
Using search in Bugsnag, you can surface error segments that need continual monitoring. For example, you can search for:
- production errors seen in, or introduced in, your latest release
- unhandled errors only from the last day
- errors from the portion of code in your app for which you’re responsible
Integrate with Jira to automate the process
Move the bugs that need fixing into your issue tracker. You can integrate Bugsnag with Jira and other issues trackers to automate this process and save yourself some time and hassle.
From your Bugsnag dashboard, you can click to create a ticket in your issue tracker. It will also automatically sync error statuses between platforms, so when you mark an error fixed, its corresponding ticket will also be marked complete.
Workflow
Start your day at the Releases dashboard
Begin your debugging workflow by checking the Releases dashboard first. The stability score for each release gives a high-level indicator of how your app’s stability is looking. If your release stability is average or above, it will appear green. If the release stability is below average, it will appear red so you’ll know to immediately begin investigating. The releases dashboard will even show you a list of the top 5 errors occurring in the release as a place to start.
Investigate errors from bookmarked searches
Since you spent the time setting up shared bookmarks, you can continue your debugging workflow by going to your saved searches to triage errors.
Take action on the error
Use Bugsnag’s workflow states to move errors through your debugging process. You can mark errors as Fixed, Ignored, or Snoozed to clear them away and keep a focused view of errors. You can also create an issue for the bug as we mentioned before, or even assign the bug to a teammate.
This allows you to maintain a concise list of errors, and avoid noise that makes debugging more difficult.
Tip: Errors you mark as Fixed are also monitored in Bugsnag. If they come back in a new version of your application, they are detected as regressions. You’ll receive immediate alerts when this happens, and Bugsnag reopens the error and its issue in your issue tracker.
Collaborate on bug fixes and keep your team updated
You can assign errors to the appropriate team member who will be the best placed to fix it. You can also collaborate in comments to get more context on the error and get to a fix faster. Making sure someone is accountable for reproducing and pushing a fix will ensure the bug doesn’t get lost.
If you need to update your team about the status of the bug, or if there are questions about the fix, having a conversation around the error can also be useful so there’s an easily accessible record of what was done. That way, if the error ever returns, you’ll be able to see a history of what happened.
These simple tips can help you and your team make your debugging workflow smoother and hopefully a more straightforward process. And the more efficient you become at debugging, the more time you’ll have to build better features for your users.
