Every software team eventually asks the same question: “Where is this bug right now?”
Regardless of whether you track work in Jira, Azure DevOps, or a simple spreadsheet, a defect moves through a predictable set of states. Understanding these states, who owns them, and the best practices around them keeps the flow smooth and the product stable.
The Core States
| State | What Happens | Owner |
|---|---|---|
| New → Assigned | A tester or user discovers an issue, logs it with a clear description, and the triage lead hands it to a developer. | QA creates the record; the triage lead assigns it. |
| Fixed → Retest | The developer believes the code change resolves the problem and marks the defect as Fixed. The QA team then picks it up for verification. | Developer marks Fixed; QA takes it to Retest. |
These two transitions are the heartbeat of the cycle. “New” is the entry point, and “Retest” is the first real test of whether the fix works.
Retest Outcomes
| State | What Happens | Owner |
|---|---|---|
| Verified → Closed | QA confirms the defect no longer reproduces using the original steps. The defect is marked Verified and then Closed. | QA verifies; the product owner may give final sign‑off before closure. |
| Reopened | The fix fails under the original repro steps, or a regression is discovered. The defect goes back to Assigned for another round. | QA reopens; the defect returns to the developer. |
A high reopen rate often signals flaky code, insufficient test coverage, or unclear requirements. Tracking this metric helps pinpoint weak components.
The Other Exits
| State | What It Means |
|---|---|
| Duplicate | The same issue has already been logged under a different ID. The duplicate is linked and closed to avoid waste. |
| Won’t Fix / Deferred | The team decides the risk is acceptable, or the fix is postponed to a later release. This decision should be documented and reviewed regularly. |
These exits prevent the backlog from becoming a dumping ground. They also ensure that every decision is visible to stakeholders.
Who Owns What
| Role | Responsibilities |
|---|---|
| QA | Owns New, Retest, and Verified. QA finds defects, adds reproducible steps and evidence, retests fixes, and confirms closure. |
| Dev | Owns Assigned and Fixed. Developers diagnose the root cause, implement a fix, and mark the defect as Fixed. |
Clear ownership eliminates hand‑off confusion and speeds up the cycle.
Do / Avoid
Do
- Attach reproducible steps and screenshots at New; don’t wait until later.
- Re‑verify using the exact original steps during Retest; a quick glance can miss subtle regressions.
- Track the reopen rate per component; treat spikes as a quality signal that needs investigation.
Avoid
- Closing a defect without an independent retest; it creates hidden technical debt.
- Letting “Won’t Fix” become a permanent sink; schedule periodic reviews to reassess.
- Skipping severity or priority logging at creation; it hampers triage and release planning.
Understanding and respecting the defect life cycle keeps teams aligned, reduces waste, and delivers more reliable software.
Master the flow, and the bugs will flow through it predictably.
Top comments (0)