Bug Life Cycle Explained
The bug (or defect) life cycle refers to the process that a software bug goes through from its
initial discovery to its final resolution and closure. Understanding and managing this cycle is
crucial for effective software quality assurance.
Stages of the Bug Life Cycle
1. New
The bug is reported for the first time, usually by a tester or user.
2. Assigned
The bug is assigned to a developer or a team for analysis and fixing.
3. Open
The developer starts analyzing and working on the bug. It is now in development.
4. In Progress (optional, sometimes merged with "Open")
Developer is actively working on the fix.
5. Fixed / Resolved
The developer believes the bug has been fixed and marks it as "Fixed" or "Resolved".
6. Testing / Retest / Ready for QA
The bug is handed over to QA/testers to verify if the fix works and does not cause other
issues.
7. Reopened
If the bug is not fixed as claimed or if the problem persists, QA reopens the bug.
8. Verified
If QA confirms the bug is fixed, it is marked as "Verified".
9. Closed
The bug is closed after successful validation.
10. Rejected / Not a Bug / Duplicate / Won’t Fix
In some cases, the bug can be rejected, marked as duplicate, or decided not to fix
(e.g., for low priority or risks).
Bug Life Cycle Flow Diagram
New → Assigned → Open → In Progress → Fixed/Resolved → Testing → Verified → Closed
Possible steps: Reopened (if still present), Rejected/Duplicate/Won’t Fix at any reasonable
stage.
Tips for Effective Bug Management
Write clear, reproducible steps: Provide detailed steps, environment info, and expected
vs. actual behavior.
Prioritize bugs: Classify as Critical, Major, Minor, etc., according to business impact.
Keep communication open: Testers and developers should collaborate to clarify
misunderstandings.
Leverage issue tracking tools: Use tools like Jira, Bugzilla, or GitHub Issues for
transparency.
Retest after fixes: Always check if the bug is truly resolved and hasn’t caused regressions.
Attach screenshots/logs: Visual evidence and logs help speed up diagnosis.
Example Bugs
Bug Summary Description Severity
Login button doesn’t Clicking the "Login" button has no effect; no error is shown, and
Major
respond user is not logged in.
App crashes on file
The application crashes when uploading a file larger than 10MB. Critical
upload
The error message for invalid password reads “Pasword incorrect”
Typo in error message Minor
(should be “Password incorrect”).
Search results don’t After changing search criteria, the results panel does not refresh
Major
update unless the page is reloaded.
Incorrect calculation in Sales tax is not included in the final invoice total for international
Critical
invoice orders.
Slow response on The dashboard takes over 20s to load metrics even with a fast
Major
dashboard connection.
Mobile layout breaks on On small screens, the navigation overlaps the content, making it
Major
iPhone SE unusable.
Duplicate user creation User management allows two users with the same email to be
Critical
possible created.
Logout link redirects to Clicking on "Logout" takes the user to a non-existing page, breaking
Major
404 page sign-out flow.
By carefully tracking each bug through its life cycle, providing clear reports, and maintaining
communication between teams, software quality can be systematically improved and customer
satisfaction increased.