Absolutely! Here’s a clear explanation of the Bug Life Cycle in Manual Testing:

---

📌 Bug Life Cycle in Manual Testing

A bug life cycle (also called defect life cycle) is the path a defect follows from discovery to closure. It ensures that all bugs are tracked, fixed, and verified.

---

1. Phases / States of a Bug

1. New

• When a tester finds a bug and logs it in a tracking tool (JIRA, Bugzilla).
• Status: New

2. Assigned

• The bug is assigned to a developer to fix it.
• Developer analyzes and starts working on it.
• Status: Assigned

3. Open / In Progress

• Developer starts fixing the bug.
• The bug is marked as Open or In Progress depending on the tool.

4. Fixed / Resolved

• Developer fixes the issue and marks it as Fixed or Resolved.
• The fix is now ready for testing.

5. Retest

• Tester retests the bug in the application.
• Checks if the defect is fixed and working correctly.

6. Verified / Closed

• If the bug is fixed successfully, tester marks it as Verified.
• Finally, the bug is Closed in the tracking system.

7. Reopened

• If the bug persists after fixing, the tester reopens it.
• Status changes to Reopened, and the cycle repeats.

8. Rejected / Deferred / Duplicate

• Rejected: Bug is invalid or not a defect.
• Deferred: Bug is postponed to a later release.
• Duplicate: Same bug already exists in the system.

---

2. Bug Life Cycle Diagram (Conceptual Flow)

New → Assigned → Open → Fixed → Retest → Verified → Closed
            ↘
          Reopened
            ↘
          Deferred / Rejected / Duplicate

---

3. Key Points

• Every bug must have a unique ID for tracking.
• Important fields in bug tracking: ID, Summary, Steps to Reproduce, Severity, Priority, Status, Reporter, Assignee.
• Helps manage defects systematically and ensures software quality.