The Laravel News site has posted a tutorial that offers some advice on how to prioritize fixing bugs and errors in your applications.
One major problem is that prioritizing errors isn’t always clear. Figuring out how much negative impact a bug is really causing is important to answer because not all bugs are worth fixing.
That’s why having a solid workflow in place for prioritizing bugs is so important. In order to confidently allocate your engineering resources on bug fixes and feature building, you need to understand the scope of each application error, and its impact on your customers. Then you can definitively say particular bugs are high enough priority that they should be scheduled into a sprint alongside your work on building new features.
The article is then broken down into a few different sections, each with a few points underneath:
- Get setup with smart error reporting from the start
- Focus your error inbox to keep it actionable
- Prioritize the most relevant errors first
- Prioritize errors by moving them into your debugging workflow
The post is sponsored by Bugsnag so there's some of the content that suggests using their service but the advice is sound for any kind of error handling workflow.