Blog
A bug triage workflow for small teams
A 15-minute bug triage workflow for small teams: reproducibility check, severity, priority, owner, and a clear rule for when Fixed means Closed.
2026-06-01
Keep triage short
Triage is not a debate club. For each new defect ask: Can we reproduce it? How bad is it for users? Who fixes it this sprint? If you cannot answer in two minutes, send it back for better repro steps.
A bug triage process only works if the meeting has a hard stop. Fifteen minutes, standing optional, three questions per ticket.
Bug triage workflow
This is the defect triage flow most small teams can run daily or every other day.
- New defect: Logged during run
- Reproducible?: Dev can repeat it
- Severity / Priority: Impact and urgency
- Assign owner: Dev picks it up
- Fix + Retest: QA on new build
- Closed: Fix confirmed
- Reproducible? may move to Send back: Need better repro steps
- Severity / Priority may move to Defer: Acknowledged, not this sprint
- Fix + Retest may move to Reopened: Fix failed retest
Three questions
- Severity: what breaks for the user if this ships?
- Priority: does it block release or can it wait?
- Owner: which dev picks it up first?
15-minute defect triage meeting agenda
Bug triage meeting agenda for small teams
| Time | Activity | Outcome |
|---|---|---|
| 0–2 min | Open New defects since last triage | Queue only, no discussion yet |
| 2–10 min | Each defect: repro, severity, priority, owner | Assigned or sent back |
| 10–12 min | Review Fixed awaiting retest | QA schedules retest tasks |
| 12–15 min | Release blockers and defer list | Risk list updated |
Worked example: triaging one defect
BUG-1042 — Coupon trailing space
QA logs: Checkout fails when coupon has trailing space. Screenshot attached. Build 408.
Triage — Reproducible? Yes, dev reproduces in 1 minute.
Severity: High (checkout blocked). Priority: High (release Friday). Owner: Alex.
Friday build 410: Alex marks Fixed. QA retests same steps Monday → Pass → Closed.
If retest failed: status Reopened, note "still spins on build 410", back to Alex.
The retest rule
"Fixed" is not "Closed". QA retests on a build that contains the fix, same steps, same data. If it passes, close it. If not, reopen with a note.
QA Workspace nudges you here: resolved defects show up as retest suggestions on the Tasks page so they do not sit in limbo.
End of week hygiene
Export open defects with your execution report. Anything still Open or Fixed-but-not-retested goes on the release risk list. Takes five minutes and saves the Friday surprise.