Bug flow statuses and transitions

When we are setting up bug statuses and transitions for the first time, it’s easy to get carried away and try to include status and transition for any possible scenario. While this might seem like a good idea in theory, in practice it rarely works. We already learned earlier in this chapter that bugs flow through many hands. Your team members have lots of duties, and if you create very complex and lengthy transitions, most people will start to feel uncomfortable using them, especially if there is no easy way to see the exact meaning and purpose of every transition. For that reason, it’s always recommended to make them as simple as possible but sufficient to support your team’s development methodology.

We need to consider that every game development team is utilizing some type of methodology, such as Scrum, Kanban, Waterfall, and so on, but there are many variations on how work is actually executed within the methodology framework...