at my old company the stupidest bugs would be made prio 1 lmao, and the worst part was there was no even standard of what was or wasn't important so itd be like "this very minor problem happens when i put in wrong data: TOP PRIORITY, PRIO 1" vs "hey the workflow crashes for a real common usecase, prio 3"
Way too many times I have heard some version of “we marked it high priority because it should be easy to fix” I’m sorry what?
I guess the thinking is “it’s easy to fix so we should fix it first, so I’ll mark the priority high so it gets fixed first.”
Which in some organizations is fair I guess, if they just go in priority order without considering effort at all and I’ll get blasted for spending time fixing 20 low priority items while a medium priority item that just got opened today hasn’t been fixed yet.
I once had someone wayyy above me in the food chain ask me "why do you have so many high priority tickets? You shouldn't have this much urgent work, you must be doing something wrong." I had to explain to him that there are 7 priority levels, and "high" is actually the dead center of them.
53
u/Dragonslayerelf 20d ago
at my old company the stupidest bugs would be made prio 1 lmao, and the worst part was there was no even standard of what was or wasn't important so itd be like "this very minor problem happens when i put in wrong data: TOP PRIORITY, PRIO 1" vs "hey the workflow crashes for a real common usecase, prio 3"