Severity versus priority
Severity and priority are sometimes used interchangeably, and that causes even more confusion in understanding what they really are. In fact, severity and priority are very different, and they should be looked at separately when writing bug reports. Priority indicates how urgent it is to fix or address something. Severity indicates how big an impact this bug has on the end user. When QA reports bugs, they act as a representative of the player, and they should have a good grasp of the severity of the bug. But a decision about priority is rarely in the hands of QA. While QA can certainly recommend how quickly something should be fixed, it’s up to the producer to decide the final priority of the bug. The producer will have the full picture of the roadmap, stakeholders’ interests, and team capacity and will make decisions based on those factors.
In the following table, we can see what the main distinctions between priority and severity are:
...
