Bug/Defect Lifecycle

What is the Defect Lifecycle?

The defect (or bug) lifecycle describes the various states a defect passes through, from the moment it is first identified to the moment it is closed.

Typical States in a Defect Lifecycle

• New: The defect has just been logged by a tester.
• Assigned: The defect is assigned to a developer for investigation and fixing.
• Open/In Progress: The developer is actively working on fixing the defect.
• Fixed: The developer has made the code change and believes the defect is resolved.
• Retest: The tester re-executes the original test case to confirm the fix.
• Verified/Closed: The fix is confirmed and the defect is closed.
• Reopened: If the retest fails, the defect goes back to the developer.
• Rejected/Deferred/Duplicate: Alternative end-states if the defect is invalid, postponed, or already reported.

Why the Lifecycle Matters

A well-defined defect lifecycle ensures every reported issue is tracked, investigated, and resolved in a consistent, auditable manner, preventing defects from being lost or forgotten.