Process Library

Bug Triage

A triage process that turns a noisy bug queue into a prioritized list with severity, reproduction, and a clear owner per item.

Product & Engineering 6 steps
When to use

On a recurring cadence, and immediately for anything severe.

Trigger
Runs when: New bugs arrive in the queue

The procedure

6 steps

  1. Confirm each report is reproducible; close or send back the ones that are not, with a question.
  2. Assign a severity based on user impact and how many people are affected.
  3. Deduplicate against existing issues and link related reports.
  4. Route each bug to the owning area with enough context to act.
  5. Escalate anything severe immediately instead of waiting for the next triage.
  6. Keep the queue honest: close stale, unreproducible reports on a schedule.
Outputs
  • A triaged, deduplicated bug queue
  • A severity and owner per bug
  • Severe issues escalated immediately
Tools
Issue trackerLogs / monitoring
Note: Severity is about user impact, not how interesting the bug is. The boring crash that hits everyone outranks the fascinating edge case that hits no one.
Download .md

Use this SOP in OrgTP

Don't just download it. Drop this SOP onto a seat in OrgTP and every AI agent under that seat inherits and runs it at runtime — with the trigger, steps, outputs, and tools already filled in.

Use in OTP → Browse more SOPs
Related searches
bug triage sop issue triage process defect management bug prioritization support escalation

Related SOPs

Product & Engineering
Code Review
6 steps
Product & Engineering
Deploy
6 steps
Product & Engineering
Sprint Planning
6 steps
Product & Engineering
Feature Spec
6 steps
← Back to the Process Library