Bug Life Cycle in Software Testing (States That Stick)

The bug life cycle is the set of states a defect moves through from discovery to closure: New/Open, Assigned, In Progress, Fixed/Resolved, Retest, Reopened, Closed, and sometimes Deferred/Won’t Fix. Tools differ; the contract between QA and eng should not.

US startups often start with too many statuses. Prefer fewer states with clear owners over a flowchart nobody updates.

QA (or whoever finds it) opens with severity recommendation and evidence. Triage assigns owner and priority. Engineering marks Fixed with build/PR link. QA retests the fix (retesting) and runs nearby regression. Only QA (or a named release owner) closes. Product can Deferred with a written reason and target window.

Reopen is not a personal attack. It means the fix failed verification or a related failure appeared. Require a comment with what still fails — avoid silent status flips.

Include environment, build, account role, steps, expected, actual, attachments, and whether data was corrupted. Link the requirement or story. Suggest severity; do not invent priority unless you own it. Duplicate search before filing saves everyone a cycle.

Track cycle time from Open to Closed and reopen rate. Rising reopens usually means weak fixes, weak environments, or weak reproduction steps — not “QA being picky.”

If your board is full of bugs stuck in Fixed for weeks, you have a retest capacity problem. That is a staffing or partner problem, not a Jira plugin problem.

TestSync Lab runs defect intake and retest inside retainers from $999. Ask for a free QA audit via /contact. AI model failures use a related but separate defect taxonomy when you add that lane.