Bug Triage Process Flowchart

How a bug report is checked for duplicates, reproduced, prioritised, fixed in a hotfix or the next sprint, and closed with the reporter told.

4 teams14 steps3 decisionsFree download

Edit this flowarrow_forward
Bug triage processReporter4Support4Product2Engineering4YesNoYesNoTry againYesNoBugreported?Already known?3Link to theexistingticketReporterupdated?Can wereproduce it?Ask for stepsandscreenshots8Sends moredetail?Blockingcustomers?10Hotfix nowAdd to thebacklogNext sprint12Fix and review13Release andverifyTold it'sfixed

Free to download. Edit it in Flow Studio to change the teams and steps, ask AI for changes, or export to PowerPoint, Word or draw.io.

Step by step

The same flow as a numbered list, ready for an SOP, a BRD or a ticket.

#Step
1Bug reportedStartReporter · step 2
2Already known?DecisionSupport · Yes: step 3, No: step 4
3Link to the existing ticketSupport · step 5
4Can we reproduce it?DecisionSupport · Yes: step 7, No: step 6
5Reporter updatedEndReporter · Done
6Ask for steps and screenshotsDocumentSupport · step 8
7Blocking customers?DecisionProduct · Yes: step 10, No: step 9
8Sends more detailReporter · Try again: step 4
9Add to the backlogDocumentProduct · step 11
10Hotfix nowEngineering · step 13
11Next sprintWaitEngineering · step 12
12Fix and reviewEngineering · step 13
13Release and verifyEngineering · step 14
14Told it's fixedEndReporter · Done

When to use it

Use it to agree how support, product and engineering handle bug reports, so urgent bugs move fast and the rest wait in the right order.

Who's involved

  • Reporter4
  • Support4
  • Product2
  • Engineering4

Yours works differently?

Describe your own process in a few sentences and Flow Studio draws it, with your teams and your rules.

Describe your processarrow_forward

How to get it right

  1. 1Search for an existing ticket first. Linking duplicates keeps one place for updates.
  2. 2Don't send a bug to engineering until someone has reproduced it or has clear steps and screenshots.
  3. 3Agree one question for priority, such as 'Blocking customers?', and use it every time.
  4. 4Tell the reporter when the fix ships. It's the step most teams forget, and it builds trust.

Questions

What is bug triage?

Reviewing new bug reports to remove duplicates, confirm they can be reproduced, set a priority and decide when and by whom they'll be fixed.

How do you prioritise bugs?

By impact and reach: whether it blocks customers, how many people it affects, and whether there's a workaround. Blocking bugs get a hotfix; others go into planned work.

More process flow templates

See all 34 process flow templates