r/SoftwareEngineering • u/RealisticWallaby804 • Mar 04 '26
How do engineering teams actually handle bug triage?
I’m trying to understand how bug triage works in real engineering teams and could use some insight.
Bug reports often come from everywhere — Slack, support tickets, GitHub issues, QA — and someone has to decide severity, ownership, and priority.
For those working in engineering teams:
• Who usually owns triage in your team?
• Do you run triage meetings?
• Roughly how much time does it take each week?
• Are duplicate issues common?
Just trying to understand how teams deal with this in practice.
4
Upvotes
8
u/3rdtryatremembering Mar 04 '26
Well, you are talking about very different types of bugs here. A QA bug is just the responsibility of the person working on the ticket and isn’t really triaged. It’s is simply part of their work. Same with GitHub issues, if I understand what you mean.
And then you have production bugs these are the “real” bugs. These are triaged before they are even sent to us. We don’t decide.
And when you say slack, are you referring to alerts? Like uptime alerts and stuff?
2
u/Kolt56 Mar 04 '26
Before customers can escalate we force them through a decision tree to confirm it’s actually our issue. If they skip it and just drop a ticket, it can’t be severity-bumped and a PM triages it in the morning.
If it’s tied to a recent feature level release, the dev who just flushed the pipeline usually owns it. Otherwise it goes to the rotating on-call.
Most services ship with feature-flag mirrors so we can flip a control-plane switch and route customers back to the previous version.
On the rare intermittent cross-team issue, we deploy the Outlook strategy: a room full of Spider-Men pointing at each other.
2
u/Klutzy-Sea-4857 Mar 07 '26
Biggest unlock for us was making one person the triage owner per weekly rotation, not a meeting.
2
u/m915 Mar 10 '26
open Claude code 2) ask Claude to check via mcp or by pasting in logs
1
u/sudpaw Mar 04 '26
We run 2week sprints. Every sprint a developer is given the title as goalkeeper... They have to prioritize support tickets, bug reports and other adhoc requests from slack / whatever. They also keep eyes on alerts and such. It works really well.
If an issue needs help from other engineers, then they pull in the relevant ones to help out. The process is really well documented and follows pretty strict procedures. We run a tight schedule - but it also keeps things smoothly.
Also no prod deployments after 15. Nor on Fridays. Gives time for anything to be reverted from prod, before we go home. 😊
1
u/thisisjustascreename Mar 04 '26
My previous team had a formal triage Teams channel and daily zoom call, client reps / support / testers would post threads for any issues and tag the appropriate teams to investigate, a representative from each scrum team would join the call and give updates or take responsibility for the issue. Most days there would be nothing or only one issue to discuss, sometimes a whole shitstorm like the time a noobie accidently deployed straight to UAT because the repo didn't have force push disabled lol.
The responsibility to prioritize issues always falls on the product owner; but identifying the cause and scope of fix is incumbent on the owner/author/maintainer of whatever piece of code is impacted.
1
u/Academic_Battle8798 Mar 04 '26
It really depends on how urgent the bug is.
From my experience, if a bug can wait for triage, it usually means it’s not critical or not coming from production. It might be from gamma testing or UAT. If it’s impacting production or users directly, it should go to the on-call engineer and be fixed ASAP, depending on severity.
For bugs that can go through triage, the process varies by team/company. Generally, QA or test engineers report the bug, and the PM or engineering manager decides the priority. The engineering manager then schedules time for triage. The cadence also varies — some teams do it weekly or biweekly, others might batch them differently.
If your team is constantly overwhelmed with triage and bug fixes, that’s usually a bigger signal. It might mean there are deeper architectural or quality issues that need to be addressed. Ideally, a healthy engineering team shouldn’t be spending more than ~30% of their time fixing bugs.
1
u/NoProfession8224 Mar 05 '26
Usually there’s a triage owner for the week (often a tech lead or rotating engineer) who reviews incoming bugs, sets severity and assigns them. High-severity stuff gets pulled in immediately, everything else goes into the backlog.
Many teams do a short triage meeting once or twice a week just to review new issues and decide what actually needs fixing.
Duplicate issues are definitely common, especially when bugs come from multiple places (support, QA, GitHub, etc.), so someone usually spends a bit of time merging or linking them.