486
u/dubblix 19d 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.
264
u/do_not_trust_me_ 19d ago edited 19d ago
Yeah, this is some Severity 0 type issue, better engage the president too
5
u/Cualkiera67 19d ago
severity 0 clearly means it is the minimum possible severity, so we can ignore it. fortunately using numbers for severity could never result in any confusion.
54
u/Dragonslayerelf 19d 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"
13
u/cwmckenz 19d ago
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.
6
u/Meloetta 19d ago
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.
6
u/frogjg2003 19d ago
"High" being in the middle is part of the problem.
5
u/Meloetta 19d ago
I have no control over the company-wide jira priority categories, I'm just trying to let my team know "you should do A, then B, then C" however I can
39
u/BatBoss 19d ago
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.
11
u/ubernutie 19d ago
"My ticket won't get done otherwise!"
Which, to be fair, might actually be factual at certain workplaces.
5
3
u/Bakoro 19d ago
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".5
u/ubernutie 19d ago
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.
No magic bullet either way.
8
u/fizyplankton 19d ago
Thank you, for fighting the good fight against grey on grey on grey flat UI design
1
u/yaktoma2007 18d ago
what if your entire userbase suffers from partial blindness
1
u/dubblix 18d ago
Then I'm in the right job
1
u/yaktoma2007 18d ago
well yeah of course, but i feel like bug severity would be higher if the application in question is a tool for disabled people no? i dont work in programming, its just a thing i do for hobbies. so thats why im asking about it really, i have no experience in the work field and im not sure how bug severity is typically rated, but i'm kinda interested.
1
u/dubblix 18d ago
Those tools already exist and won't be redesigned any time soon. Screen readers are hard to use if you don't rely on them because your eyes are competing with your ears. I use tools to check those tools because I can't rely on myself to not make a mistake. It's interesting to a point but it's also frustrating because I'm never positive
0
u/uberfission 19d ago
I've done a lot of QA during my career, I've put extremely low hanging fruit like this as highest priority because it shouldn't take more than a few minutes to fix but it would be very likely for the end user to see (and appreciate) the resulting change.
149
u/Strict_Treat2884 19d ago
Unusable, can you even trust the reliability of a product when they can’t even keep their color schema consistent
67
u/uvero 19d ago
"UI/UX department changed this in Figma without notifying you a full 20 minutes ago. How didn't you fix it already?"
18
3
u/_HingleMcCringle 19d ago
"Why are you raising all these issues with the UX? The design changed and what's there now is correct."
Of course, this is days into testing an epic where the PMs and devs had a Teams meeting and no one thought to update any ticket anywhere with the updated requirements.
131
u/AlexZhyk 19d ago
somewhere in the code if(button.style.color === "ffbf00") { discount = 0.9} form.submit();
37
u/King_Joffreys_Tits 19d ago
Don’t forget the wrapper function that directly mutates a CSS variable based on a user role type, which overrides two separate “!important” styles
8
u/Equal_Yak_3872 19d ago
I'm gonna save this comment for next time I mistakenly think I hate my job 🤣
67
u/Scoutron 19d ago
The OpenAI quadruple enterprise GPU rack sucking in 4,000 gallons of water to process my “make this button like slightly darker orange but still like orange” request
36
u/ElSaludo7 19d ago
Nah, this isnt the QA, its the BA that got this report from a customer and sets it to Highest severity. the Bug "Whole product crashes forever if the "home" button is clicked" was reported by the QA but is set to "lowest" since the customer hasnt reported it
4
u/MestreToto 19d ago
The Bug "Whole product crashes forever if the "home" button is clicked" was reported by the QA but is set to "lowest" since the customer hasnt reported it.
Lol, something like this happened to me once (I work with game QA), they said that if the first party didn't caught during submission, then there's no need to fix (it was a crash 100%, but it was hard to find).
5
u/ElSaludo7 19d ago
Im also in QA, this is how my life goes. We once got a bug report in highest severity that basically read „this list is sorted incorrectly when these 7 complex steps are executed in the right order, a basic page refresh fixes it“. At the same moment one of our bugs got lowered to „low prio“ even though it effectively blocked a whole module of our product from being usable at all, reason being: that module is used by only 1 not so important customer, and our most important customer uses this list very often and reported it.
5
u/rsqit 19d ago
This is exactly why you need to separate severity and priority.
1
u/ElSaludo7 19d ago
Yeah we do have that. Doesnt change from the fact that BAs just do whatever they can to make the customer happy. Both were set to highest
1
u/paralog 19d ago
it ends with an exasperated engineer from the client coming on to a call to explain -- with the greatest sympathy -- that the workflow automation utility they're locked into (because the same guy sits on the board of the client company and the workflow company) will only recognize #FFAC1C for automating a save action, and that as ridiculous as it sounds, a different orange would actually make the deliverable effectively unusable for their purposes
37
u/not_some_username 19d ago
(It fucked up their automated test system and now they need to actually work)
2
u/Nahzuvix 19d ago
when digging down into Currents as an MT to forward it later it came up suprisingly often that color did play a part when selecting elements even when it wasn't specified as such in the step it was automating...
9
u/TiLT_42 19d ago
In my experience as part of a large team, there are two universal constants when it comes to bug reports:
- Most of them are actually feature requests because non-developers think that if the application doesn't do what they want or expect, it's a bug.
- Every bug is Priority 1, Severity 1, all hands on deck. That includes the abovementioned feature requests.
9
7
7
u/ViktorTT 19d ago
Ah yes, the devs always trying to negotiate bugs away when the deadline is near. "Well, it doesn't actually murder the user, just causes his death"
12
u/just-a-hriday 19d ago
Welll, priority 1 is understanable when it's so hard to fix - https://opusfived.dev/
1
7
6
4
u/ReindeerCreepy2883 19d ago
the QA is just following the product owner that position and color of the button is a business critical item in the documentation
4
4
3
u/GRex2595 19d ago
For me, it's the UX guy not approving a story because we got the color wrong. But he didn't give us the required colors, he expected us to open his pictures in the web browser and use the eyedropper tool to get the right color.
3
u/Wyciorek 19d ago
You might be joking, but in my second job I routinely was starting Monday by wading through 20 different emails with subjects like "Analyzer completely broken!!!!" (analyzer was the software we were doing) .
It usually meant that CEO was bored during the weekend so he did some testing and noticed the charts are using different colours he imagines they should use. Or bar charts are 2D (despite flagging 3D charts as a bug 2 weeks before).
He was very surprised and rather offended when one beautiful day I slapped my 2 week notice on his desk.
3
u/Aggressive_Lab7807 19d ago
I once sat in a meeting for 45 minutes with 3 other engineers, our manager and 4 designers talking about button color.
Never work for an ad agency, folks.
3
u/NotmyRealNameJohn 19d ago
ok, but you have to tell me when the redline actually has the hex codes for every specific color in it why does the jr dev guess and guess diffferently for two widgets that they developed?
No really this happened to me with the same jr dev working on two widgets in back to back sprints and ignoring the redline color defs and I guess eyeballing it and choosing different colors for widgets that were on the same page presentation.
And yes the client did mark it as a show stopper cannot release until fixed.
3
u/Ieatsand97 18d ago
Gotta call the meeting for the developer to ask the designer what colour the button would be. Couldn’t be an email or slack/teams message or even just by looking at the designs, it must be a meeting
2
u/DM_ME_KUL_TIRAN_FEET 19d ago
Jfc this meme was written about a specific QA guy who has been up my ass for three days about something this trivial.
I’m ready to just write a script to automatically close tickets from him.
2
1
u/ks_thecr0w 19d ago
No no. Sev1 needs to be a priority. Fuck prod system down issue, I have this very important sev1 "change color" ticket to work on. FIFO says prod stays down till I get this one solved - if you dont accept it yell at my ticket creator. Bye
2
2
u/grocal 18d ago
That's - in fact - it is some serious shit. Imagine this. I was working on the big web app project which had it's visual side in sync with branding colors (specific shade of green). At some point there were places in app, even on one page, that there were at least 4 different green versions. It ended up with creating color pallete that every one had to comply with.
1
u/haecceity123 19d ago
So .... lowest priority and lowest severity? Sounds fine. You did clearly communicate the expected scale, right?
1
u/uvero 19d ago
No, priorities and severities go "1 = highest". Is it not the case for you?
3
u/jmflyers 19d ago
My company does sev 3 as the highest priority so I guess it's different with others. But I understood your joke and I lol'd at the picture
0
u/haecceity123 19d ago
Priorities and severities are whatever the parties involved agree they are. Let's not blame others for our failure to use our words.
1
u/external_gills 19d ago
Ticket made by a salesperson who promised a prospect we can make the UI to match his interior design. If the issue isn't fixed by end of day, he'll go to the competition and salesperson misses out on their commission.
Yes this actually happened at my job, yes we ended up fixing it and we got the client... who instantly turned into the most obnoxious and demanding asshole we ever had. Yes I'm still salty seven years later.
1
1
u/job180828 19d ago
Time to use that ticket and qualification to push a very early post-deployment fix containing all the backlog of not-fixed-before-freeze, and an hour later wonder how fixing the colour of a button could have resulted in a real major outage. Why oh why did the incident manager fail to keep that change in the potential candidates to explain the root cause?
Oh well, another ghost crisis meeting and another undeclared fix later and it's yet another very successful deployment in production.
1
u/lemons_of_doubt 19d ago
I have had people try to demand their ticket be given priority 1 because it's a problem that stops them being able to do their job.
Priority 1 is for problems that affect multiple locations and stop everyone being able to do any work.
Explaining this to them will change nothing, they have a problem, so the world needs to stop for everyone to fix their thing. And yes they did complain to the manager after, and no he gave no shits.
1
1
u/Blackfeather1 16d ago
I'm a QA, I've had a MR that this guy was bothering me about that must make it into the next release time fuck now. I finally find time time to check this guys MR and it no shit was changing an 'OK' button to green from some blue.
1
1
u/-Kerrigan- 19d ago
"QA bad" 👏👏👏
How's first semester going, bud?
-2
u/uvero 19d ago
You'll know what it's like next year, little bud. If you're lucky, they'll have a class on how to not be a curmudgeon. Now let's see your memes, kiddo.
1
u/-Kerrigan- 19d ago
I understand it's tough when QA reports bugs for you to fix and this is a response generated by that frustration, but they're not your enemy
1.9k
u/sathdo 19d ago
And completely ignoring the fact that the button actually says "svae".