Interactive tool · Part 4
The Defect Triage Board.
You are the QA lead the day before a release, and this is the open bug backlog. Triage it the way a real team does: give each new defect a severity and a priority, move it along its lifecycle, and retest every fix before you close it. As you work, the board answers one question, the only one that matters at the gate, is this build safe to ship?
0Open defects
0Critical / High open
0%Reopen rate
0Avg age of open (days)
Triage in progress
Drag a card between columns, or use the buttons on each card. A new defect needs both a severity and a priority before it can be triaged.
Tester
Team
Developer
Tester
Closed / Deferred
The two axes
Severity is impact. Priority is urgency.
They are different questions, and the interesting defects sit in the corners. The tester usually owns severity, the product owner owns priority, and triage is where the two meet.
P1 urgent
P2 high
P3 / P4
Critical
Fix now, block the release
Fix this release
Rare: re-check the priority
Major
Fix this release
Schedule the fix
Backlog
Minor / Trivial
High visibility, low impact: a typo on the homepage
Backlog
Defer or accept