How to prioritize bugs?

Question

In my current company there isn\'t clear understanding between the test and development teams as to how severe a bug should be? There are arguments which go back and forth to re

Answer 1

I think this is the scale we used at a previous job:

1. Causes loss of files or system instability.
2. Crashes the program.
3. Feature doesn't work.
4. Feature doesn't work, but there are workarounds.
5. Cosmetic issue.
6. Request for enhancement.

Sometimes this was abused - if a feature was so poorly designed that someone couldn't figure out how to use it, that was classified as a 6, and it never got fixed.