Defect Life Cycle (Bug Statuses)

Why bug statuses exist

They help teams:

• track ownership
• prioritize work
• ensure QA verification

Common statuses

• New: reported
• Triaged: severity/priority assigned
• Assigned: owner picked
• In Progress: being fixed
• Fixed: dev completed
• Ready for QA: waiting for verification
• Verified: QA confirmed fix
• Closed: done

Optional statuses:

• Reopened (still failing)
• Won’t Fix
• Duplicate
• Cannot Reproduce

Diagram: defect lifecycle

diagram Diagram mermaid

  graph TD
A[New] --> B[Triaged]
B --> C[Assigned]
C --> D[In Progress]
D --> E[Fixed]
E --> F[Ready for QA]
F --> G{Verified?}
G -- Yes --> H[Closed]
G -- No --> I[Reopened]
I --> C

Tip

Always include:

• severity
• priority
• reproducibility