Bug triage
Definition
The process of reviewing incoming bug reports, assessing their severity and business impact, assigning priority, and routing them to the appropriate backlog or on-call queue — so that the most critical issues get fixed first and lower-priority issues don't get lost.
Bug triage borrows its name from medical triage: the same resource-constrained prioritization problem. Without triage, every bug report competes for attention at the same level. With triage, severity and priority are assigned systematically, and the team works the most impactful issues first.
Typical severity levels:
- P0 / Critical: Production is down or a critical user path is broken. Fix immediately.
- P1 / High: Major functionality impaired; significant user impact. Fix this sprint.
- P2 / Medium: Feature works but with limitations. Fix in the next few sprints.
- P3 / Low: Minor issue; cosmetic or edge case. Fix when capacity allows.
Who runs triage: Many teams designate a rotating bug triage DRI (directly responsible individual) — one engineer or PM who is the single point of contact for bug prioritization each week. This prevents triage from being everyone's job and therefore no one's job.
The triage meeting: Some teams run a weekly triage meeting to review new bugs together. Others do it async with a shared queue. The meeting format works well when bugs need discussion to assess severity — a known repro rate, user impact data, or customer tier all factor in.
The whiteboard at triage: When bug volume is high and the team needs to map dependencies or cluster related issues, a whiteboard is faster than a spreadsheet. Snap the clustering exercise with BoardSnap to capture the groupings before the board is wiped.
Examples
- An engineering team runs a 30-minute Monday bug triage meeting, processing the previous week's reports and assigning priorities before sprint planning later in the day.
- A mobile app team tracks P0 bugs in a separate on-call queue that bypasses the sprint process — any P0 gets a patch release within 24 hours.
- A PM uses the weekly triage meeting data to report the bug rate trend to leadership — showing whether the codebase is getting healthier or not.
- A B2B SaaS company's triage process includes customer tier as a severity input — a P2 bug for an enterprise customer may be triaged as P1.
Snap a bug triage. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.