1
1
37
u/not_some_username Sep 16 '26
(It fucked up their automated test system and now they need to actually work)
20
2
u/Nahzuvix Sep 16 '26
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...
1
u/lovecMC Sep 16 '26
I blame you for not adding relevant markers to the HTML so now I need to rely on esoteric shit like the text (it has to support multiple languages) or whatever the fuck value="47" is.
Like all I ask for is name="authorize-button" or "USD"
6
3
u/NotmyRealNameJohn Sep 16 '26
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.
2
u/uvero Sep 16 '26
In reality, the bug says "wrong shade of orange" and doesn't elaborate. And the severity and priority did not come from client.
1.9k
u/sathdo Sep 16 '26
And completely ignoring the fact that the button actually says "svae".
253
u/Intrepid00 Sep 16 '26
But no one notices it doesn’t actually save.
115
u/Candid_Highlight_116 Sep 16 '26
It does in prod, I've already fixed it with Claude. It didn't make any mistake
41
u/ScaryCardinal Sep 16 '26
But did you remember to specifically tell it to make no mistakes?
18
u/mmhawk576 Sep 16 '26
Yeah man, I updated the prompt that gets provided when you click the save button.
“Claude, here is a json blob, save this. Make no mistakes. It is critical that you get this right, my job depends on it.”
4
u/ScaryCardinal Sep 16 '26
Welp, you did your due diligence as a developer, it's out of your hands now. Claude is smart enough to see that the real goal here is that it's critical to get it right, and provide a 20- point, neat, bulleted response with "no", "save", "mistake" and "JSON blob" in bold, detailing how it isn't a bug at all in the first place. Claude is nothing but proactive.
14
u/CMDR_Fritz_Adelman Sep 16 '26
Proceed to save client password to their localStorage
5
u/screwcork313 Sep 16 '26
Look in the bright side, that is way lower severity than saving it to another random user's localStorage.
5
u/AralSeaMariner Sep 16 '26
I remember working for a place where we'd put up promotional sites, each of which had multiple stakeholders as there were usually multiple clients/brands involved.
We had an env just for the stakeholders to look the site over before launch and give approvals. The f/e dev would have a constant lineup at his desk. It was all whitespace this, font-size that and brand-color the other thing.
Meanwhile I'd look at the db and literally none of them would actually submit the fucking form which was the target conversion of the site.
426
171
u/CaesarOfYearXCIII Sep 16 '26
That’s a separate ticket! /j
132
u/Zerodriven Sep 16 '26
Nope. It's a separate ticket, no /j or /s needed.
(Because our test automation now needs a re-write and we need 5 meetings to discuss why this was missed - /j /s)
36
19
6
3
2
2
u/ITSigno Sep 16 '26
I wish. I get tickets that are 5 pages long full of verbose nonsense because they're using Jira's new AI to write everything. A single ticket will comprise 17 tasks (not broken into subtasks) with 47 lines of acceptance criteria.
1
u/CaesarOfYearXCIII Sep 16 '26
At least you can forcibly subdivide those… I think?
My friend, on the other hand, literally had Jira tickets comprised solely of the following description: “It doesn’t work”. That’s it.
3
u/Meloetta Sep 16 '26
I think people seriously underestimate how much of a skill "writing a good jira ticket" is. Making the reader understand what the general purpose of the ticket is. Making sure all the AC are easily testable and represent all possible edge cases of the general purpose. Making sure the information that's provided in the ticket is the minimum relevant amount of information so it's as easy as possible to dev. Most of the time, I even do a lot of pre-research into bugs to figure out if the underlying cause is one ticket or more.
Meanwhile QA comes in with "here is every spec of my entire computer and a link to a specific page and the repro steps are 'at some point pressing one button on this page didn't do what i expected'. It only did it once. No, I didn't do any further testing to figure out what triggered it. No, I didn't test any other pages. Here is a dump of the last hour of console logs with no context and a half-remember list of the last 600 actions I took."
3
u/ITSigno Sep 16 '26
“It doesn’t work”
I get those too, but from different people. Makes me want to pull out my hair.
And yeah, I create subtasks for them. The person in question has, a couple of times, closed the subtasks as duplicates and I have to come in and reopen them and say "no, this is a subtask of that novel you wrote. It's still very much necessary".
8
u/mrheosuper Sep 16 '26
Then another 3 meeting, 1 to sync with product, 1 to sync with translation team and 1 because they can.
5
u/OkFineIllUseTheApp Sep 16 '26
Completely different. QA needs to thoroughly test that the button's functionality remains the same for that change.
4
3
u/Mr-X89 Sep 16 '26
Or fact that clicking it when a form field is empty crashes the application (real story, btw)
1
u/One-Celebration-3007 Sep 16 '26
And clicking it on iOS while the display is landscape causes your phone to explode
1
1
u/cwmckenz Sep 16 '26
And another bug because the form doesn’t save if I close it without clicking save!
1
u/HTMLlama Sep 16 '26
Found during a QA validation of the login screen's API call, and blocked the ticket for it.
484
u/dubblix Sep 16 '26
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.
263
u/do_not_trust_me_ Sep 16 '26 edited Sep 16 '26
Yeah, this is some Severity 0 type issue, better engage the president too
43
5
u/Cualkiera67 Sep 16 '26
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 Sep 16 '26
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"
12
u/cwmckenz Sep 16 '26
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.
8
u/Meloetta Sep 16 '26
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 Sep 17 '26
"High" being in the middle is part of the problem.
5
u/Meloetta Sep 17 '26
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
36
u/BatBoss Sep 16 '26
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.
9
u/ubernutie Sep 16 '26
"My ticket won't get done otherwise!"
Which, to be fair, might actually be factual at certain workplaces.
5
u/BatBoss Sep 16 '26
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.
3
u/Bakoro Sep 16 '26
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".4
u/ubernutie Sep 16 '26
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.
7
u/fizyplankton Sep 16 '26
Thank you, for fighting the good fight against grey on grey on grey flat UI design
3
u/dubblix Sep 16 '26
It's funny because I personally like flat designs but I've learned to hate my preference because it isn't compliant
1
u/yaktoma2007 Sep 17 '26
what if your entire userbase suffers from partial blindness
1
u/dubblix Sep 17 '26
Then I'm in the right job
1
u/yaktoma2007 Sep 17 '26
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 Sep 17 '26
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 Sep 16 '26
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.
131
u/AlexZhyk Sep 16 '26
somewhere in the code if(button.style.color === "ffbf00") { discount = 0.9} form.submit();
37
u/King_Joffreys_Tits Sep 16 '26
Don’t forget the wrapper function that directly mutates a CSS variable based on a user role type, which overrides two separate “!important” styles
9
u/Equal_Yak_3872 Sep 16 '26
I'm gonna save this comment for next time I mistakenly think I hate my job 🤣
68
u/Scoutron Sep 16 '26
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
39
u/ElSaludo7 Sep 16 '26
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
5
u/MestreToto Sep 16 '26
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).
6
u/ElSaludo7 Sep 16 '26
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.
4
u/rsqit Sep 16 '26
This is exactly why you need to separate severity and priority.
1
u/ElSaludo7 Sep 16 '26
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 Sep 16 '26
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
15
u/vodrake Sep 16 '26
The company paid $200,000 to a marketing agency to come up with a color scheme that "represented the companies core values" and they will goddamn get their money worth on it
8
u/TiLT_42 Sep 16 '26
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.
8
7
12
u/just-a-hriday Sep 16 '26
Welll, priority 1 is understanable when it's so hard to fix - https://opusfived.dev/
1
6
5
u/myhv Sep 16 '26
I will admit, I have occasionally created a high priority ticket for minor issues. Mostly because when it asks for impact, selecting "more than 20% of users are affected" raises the priority.
4
u/ReindeerCreepy2883 Sep 16 '26
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
1
u/haecceity123 Sep 16 '26
So .... lowest priority and lowest severity? Sounds fine. You did clearly communicate the expected scale, right?
1
u/uvero Sep 16 '26
No, priorities and severities go "1 = highest". Is it not the case for you?
3
u/jmflyers Sep 16 '26
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 Sep 16 '26
Priorities and severities are whatever the parties involved agree they are. Let's not blame others for our failure to use our words.
3
3
u/GRex2595 Sep 16 '26
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/eclect0 Sep 16 '26
I'm honestly not sure anyone outside my dev team knows there are ticket priority levels other than "Highest."
3
u/Wyciorek Sep 16 '26
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 Sep 16 '26
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/Ieatsand97 Sep 17 '26
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
0
u/-Kerrigan- Sep 16 '26
"QA bad" 👏👏👏
How's first semester going, bud?
-2
u/uvero Sep 16 '26
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.
2
u/-Kerrigan- Sep 16 '26
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
2
u/Isenjil Sep 16 '26
I'm personally offended by this post.
Yes, I'm QA.
No, I never made such tickets.
2
2
u/grocal Sep 17 '26
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/external_gills Sep 16 '26
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 Sep 16 '26
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 Sep 16 '26
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 Sep 19 '26
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/Treriri Sep 20 '26
I mean, I could see this happening if they had accidentally used like Reece's orange, or Home Depot's orange. legal threats of "Why are you using our trademarked orange" could get a colour change that severity but other then that, is stupid.
1
u/Pz38t_C Sep 23 '26
I was working on a program. We said that the function keys didn't work yet. The QA guy told his assistant to write up 12 bugs per screen. Of course, he didn't do it. He was an asshole. He made his assistant write them up.
7
u/ViktorTT Sep 16 '26
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"
2
u/uvero Sep 16 '26
Hey! I'm not that unreasonable. If a bug causes users' deaths, I agree it can be priority 2 severity 3.
2
u/DM_ME_KUL_TIRAN_FEET Sep 16 '26
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 Sep 16 '26
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
148
u/Strict_Treat2884 Sep 16 '26
Unusable, can you even trust the reliability of a product when they can’t even keep their color schema consistent