Every software project generates bugs, and regardless of whether you use Jira, Azure DevOps, or a simple spreadsheet, each defect follows a predictable path. Understanding the states, ownership, and best practices helps teams move faster, keep quality metrics honest, and avoid the common pitfalls that turn defect tracking into a nightmare.
The Core States
New → Assigned – When a tester discovers an issue, they log it as New and provide clear reproduction steps and evidence. The triage lead reviews the report, assigns a severity, and hands the defect to a developer, changing the status to Assigned.
Fixed → Retest – The developer investigates, writes a fix, and updates the defect to Fixed. At this point the responsibility shifts back to QA, which must retest using the original steps. The status becomes Retest to signal that verification is pending.
Retest Outcomes
Verified → Closed – If QA confirms that the fix resolves the problem and no side effects appear, the defect moves to Verified and then Closed. The issue is considered done.
Reopened – When the fix does not hold—perhaps the bug reappears in a different scenario or the original steps fail—QA changes the status to Reopened. The defect returns to Assigned for another round of investigation.
The Other Exits
Duplicate – Occasionally a defect is already recorded under another ID. Marking it as Duplicate consolidates effort and keeps the backlog clean.
Won’t Fix / Deferred – Some defects are accepted as risk or postponed for a later release. They receive a Won’t Fix or Deferred status, but should still be reviewed periodically to ensure the decision remains valid.
Who Owns What
- QA owns New, Retest, Verified – QA is responsible for initially finding the defect, confirming that a fix works, and finally verifying closure.
- Dev owns Assigned, Fixed – Developers diagnose the root cause, implement the fix, and update the defect accordingly.
Do / Avoid
Do
- Attach reproducible steps and supporting evidence at New; never wait until later stages.
- Re‑verify the exact original steps during Retest; a quick glance can miss regressions.
- Track the reopen rate per component; a high rate signals deeper quality issues.
Avoid
- Closing a defect without an independent retest; this creates hidden technical debt.
- Letting Won’t Fix become a dumping ground; periodically review these items.
- Skipping severity logging at creation time; severity drives prioritization and resource allocation.
A well‑defined defect life cycle keeps the whole team aligned, reduces waste, and turns bugs into measurable improvement signals.
Top comments (0)