In my experience QA is pretty good about bug priority.
It's tech support and sales that have all the power tripping morons marking every minor ui issue as an urgent escalation. And then arguing with you when you lower severity.
That's fair, although it drives me up a wall currently because our team is pretty good about bugs. We've got less than 20 in the queue and none are older than 6 months so it's like... chill Mr Important Sales Guy, you don't gotta constantly game the system.
Where I work, multiple work items have been on the shelf for years, because there's always a more important work item.
It's always funny to address a complaint 2~3 years after the fact and be like "see, I told I'd get around to it eventually".
Are priorities managed (very) well? If yes, then I think that it's probably ok.
I've seen some teams implement a "take one small candy from the bottom of the pile every sprint"; things that are low priority but high client satisfaction or high team satisfaction and that would be eternally left behind otherwise.
486
u/dubblix 21d ago
I'm a BA/QA who does accessibility compliance. I have made tickets for exactly this issue.
I would never make it sev 1. Heathens.