This post is example of wrong usage for bug priority. We provide explanation what is wrong with this definition.
Wrong usage of bug priority by software testers is one of the most frequent mistakes in software development team. This blog post gives an example of bug triage process. It gives wrong definition of bug priority:
Wrong definition of bug priority: Of the people who experience the bug, how badly does it affect their experience with the product?
This is wrong, because this is definition of bug severity: what is scale of negative impact of this bug.
Why this wrong definition of bug priority is dangerous? Because bug priority is determined on bug severity. Bug priority is project manager responsibility, and bug severity is tester responsibility! Bug could have high severity, but low priority. Example is when project manager does not have programmers with knowledge how to resolve this bug.
Why is that so important? Only project manager has resources to determine when this bug will be put into sprint (priority), while tester has the most knowledge to determine how this bug affects the user.
Remember that when you will get question from project manager: What is priority of this bug?