On: Don’t Confuse a Bug’s Priority with Its Severity

[ska]

How would you signal the difference between:

1. We have the wrong .png asset in the database

2. Our entire rendering infrastructure is suspect

[daveFNbuck → ska]

That would be extremely obvious from the bug title and description, which are presumably being read by the person who sets priority.

[ska → daveFNbuck]

So instead of a severity rating, you are saying severity is encoded in the language of the description? Using descriptors a potentially non-technical PM can understand unambiguously?

I'm not saying this is the wrong approach by the way, it's just interesting how people approach this differently.

[daveFNbuck → ska]

If the PM doesn't have enough expertise to understand how severe a bug is, how are they supposed to accurately assess the business impact?