Bug triage template
Decide what happens to every incoming bug report: reproduce, size the impact, then schedule.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Link to existing and close
- P0: fix now, page on-call
- Ask reporter for steps
- Duplicate?
- Bug reported
- P1: this sprint
- Can we reproduce it?
- Severity?
- P2: backlog
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Add the next step with Tab. Select a box and press Tab: a new box appears, already linked. Type its label and press Enter.
- Decisions get both branches. A decision diamond is offered a “yes” and a “no” branch for any it's missing, on your device and instantly.
- Catch gaps. Orange badges flag a decision with only one branch, a box that isn't connected, or two boxes with the same label, with a one-click fix.
Good for
- bug
- triage
- engineering
- qa
- Documenting how work actually moves between people and systems
- Spotting missing branches, loops and hand-offs before they cause problems
- Onboarding someone to a process in one picture
Related templates
Basic flowchart
Start, steps, a decision with yes/no branches, and an end — the classic shape to build from.
Approval workflow
A request moves through manager and finance approval, with rejection and rework loops.
Support ticket escalation
How a support ticket moves from first response to tier 2, engineering, and resolution.
Incident response
Detect, triage, mitigate, communicate, resolve and learn — an on-call runbook in one view.
Debugging flow
A disciplined loop for hard bugs: reproduce, write a failing test, isolate, hypothesise, fix the root cause.
Test pyramid (test strategy)
How many unit, integration and end-to-end tests to write, what each covers, and how fast they should run.