What are the many ways you categorise bugs?

simon_tomes
Tue, 07 Jan 2025 18:08:52 +0000
Discussions

Categorising bugs can often be more complicated than we think.

I once set up a Jira instance and got in a right old muddle trying to cater for everyone’s needs across the product development team. The bug issue type had so many options such as priority, severity, impact, type, likelihood, steps to recreate, expected result, actual result and probably much more. Makes me feel a bit awkward thinking about it.

In another place, we used a bug-tracking process that was established beyond our remit so we couldn’t change it.

And in my current setup, if we find a bug we add it to a dedicated Slack channel for our developer (@testingchef) to investigate/ask questions.

Taking a step back there’s often a debate across development teams about how to categorise an observation. Is it a bug, feature, idea, problem, issue, fault, defect etc?

I’d like to hear about your experiences with the places you’ve worked at. How did you/do you categorise bugs? What did the bug process look like? What’s been your favourite setup and why?

AI-generated replies will be deleted so don’t waste your time and MoTs time. We have better things to be doing with the community than reviewing AI-generated content.

9 posts - 7 participants