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
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 | Who | Next |
|---|---|---|---|
| 1 | Bug reportedStartReporter · step 2 | Reporter | step 2 |
| 2 | Already known?DecisionSupport · Yes: step 3, No: step 4 | Support | Yes: step 3, No: step 4 |
| 3 | Link to the existing ticketSupport · step 5 | Support | step 5 |
| 4 | Can we reproduce it?DecisionSupport · Yes: step 7, No: step 6 | Support | Yes: step 7, No: step 6 |
| 5 | Reporter updatedEndReporter · Done | Reporter | Done |
| 6 | Ask for steps and screenshotsDocumentSupport · step 8 | Support | step 8 |
| 7 | Blocking customers?DecisionProduct · Yes: step 10, No: step 9 | Product | Yes: step 10, No: step 9 |
| 8 | Sends more detailReporter · Try again: step 4 | Reporter | Try again: step 4 |
| 9 | Add to the backlogDocumentProduct · step 11 | Product | step 11 |
| 10 | Hotfix nowEngineering · step 13 | Engineering | step 13 |
| 11 | Next sprintWaitEngineering · step 12 | Engineering | step 12 |
| 12 | Fix and reviewEngineering · step 13 | Engineering | step 13 |
| 13 | Release and verifyEngineering · step 14 | Engineering | step 14 |
| 14 | Told it's fixedEndReporter · Done | Reporter | 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_forwardHow to get it right
- 1Search for an existing ticket first. Linking duplicates keeps one place for updates.
- 2Don't send a bug to engineering until someone has reproduced it or has clear steps and screenshots.
- 3Agree one question for priority, such as 'Blocking customers?', and use it every time.
- 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
- Incident managementAn incident response flow from alert to postmortem: triage, severity, incident lead, mitigation, status updates and closing the loop.
- IT change managementA change request flow with standard changes, change advisory board review, a scheduled change window, testing and rollback.
- Access requestHow an employee gets access to a system: manager approval, data owner approval for sensitive data, least-privilege access and regular access reviews.
- Software releaseA release process from merged code to everyone: staging, regression tests, go or no-go, a staged rollout with monitoring, rollback and release notes.