Bug triage process flowchart

Bug triage process flowchart

A worked example to adapt. Rename steps, add branches and owners to match how your team actually works.

flowchart TD
  s(["Bug reported"])
  d1{"Duplicate of existing issue?"}
  dup(["Link and close as duplicate"])
  rep["Try to reproduce"]
  d2{"Reproducible?"}
  info["Ask reporter for steps and logs"]
  sev["Set severity and priority"]
  d3{"Critical?"}
  hot["Hotfix now"]
  back["Add to sprint backlog"]
  fix["Fix with regression test"]
  ver["QA verifies fix"]
  e(["Close and notify reporter"])
  s --> d1
  d1 -->|Yes| dup
  d1 -->|No| rep
  rep --> d2
  d2 -->|No| info
  info --> rep
  d2 -->|Yes| sev
  sev --> d3
  d3 -->|Yes| hot
  d3 -->|No| back
  hot --> fix
  back --> fix
  fix --> ver
  ver --> e

About this bug triage process flowchart

Triage decides which bugs get fixed now, which wait, and which need more information. Without a shared flow, critical bugs sit in the backlog and minor ones interrupt sprints.

This example fits a product team that triages new issues daily or a few times a week.

Step by step

1. Deduplicate. Link duplicates to the existing issue so reports aren't lost.
2. Reproduce. Confirm the bug; ask the reporter for steps, environment and logs if needed.
3. Prioritize. Set severity (impact) and priority (urgency).
4. Fix. Critical bugs get a hotfix; others join the backlog. Every fix adds a regression test.
5. Verify and close. QA verifies, and the reporter hears that it's fixed.

How to make it in flow-chart.io

1. Start from the example. Edit the text in the generator box above so it names your own severity levels and tools, then press Generate. The free preview needs no sign-up.
2. Add the branches. Add the decision points that matter for you, for example security vulnerability? or affects paying customers. Each decision becomes a diamond with labeled outcomes.
3. Assign owners. Save the diagram to the editor (free account) and rename steps to show who does what: support, triage lead, engineer and QA.
4. Share or export. Share a read-only view link: people with the link can view the diagram but not edit it. Downloads as PNG, SVG or PDF are part of Flow Pro (see pricing).

Tips

• Define severity levels with examples.
• Time-box the 'needs info' state; close stale reports politely.
• Notify the reporter on close; it builds trust in reporting.

Frequently asked questions

What is the difference between severity and priority?

Severity measures impact; priority measures how soon it should be fixed. A severe bug in a rarely used feature may still be lower priority.

How often should we triage?

Often enough that new bugs are looked at within your response target, commonly daily for active products.

Can I generate my own triage flow?

Yes. Edit the steps in the generator box and press Generate.

Related