3 ms·
Severity is how the reporter sees the problem: if it interferes with their particular use case, it's of the highest severity. Almost all bugs end up being of t
by bregma 7y ago
Severity is how the reporter sees the problem: if it interferes with their particular use case, it's of the highest severity. Almost all bugs end up being of the highest severity.
Priority is how the developer (or, more likely, the project management team) sees the bug. Highest priority bugs are the ones in the project manager's spreadsheet and ended up there because of the most vocal complainers (paying customers, an inconvenienced CEO, etc). The rest will never get fixed.
It's impractical to use the severity of the bug to rank the priority, because they're not strongly correlated.
- SloopJon 7y agoMy gut reaction to the headline and the article was that it's a mistake to make such a distinction. However, if you look at QA/Support owning severity, and PM owning priority, it potentially reduces conflict--what do you mean this crash isn't critical?! I think they are highly correlated, but they occasionally diverge.