Bug Life Cycle

A bug life cycle typically includes the following sequential states:

1. New: When a tester discovers and logs a defect for the first time, its status is set to New.

2. Assigned: The development lead reviews the logged bug and assigns it to a specific developer to look into.

3. Open: The developer starts analyzing the bug and working on a fix.

4. Fixed: Once the developer makes the necessary code changes and verifies the fix locally, they mark the status as Fixed.

5. Pending Retest: The fix is deployed to the testing environment, and it is put back into the queue for the testing team to verify.

6. Retesting: The tester runs the specific test cases again to see if the defect has truly been resolved.

7. Verified: If the tester confirms that the bug is gone and no longer reproducible, the status changes to Verified.

8. Closed: After final validation (and making sure it hasn't broken anything else), the bug is officially marked as Closed.

1. Rejected: If the developer or lead believes the bug is not a valid defect (e.g., it's an intended feature or standard behavior), it is Rejected.

2. Deferred: If the bug is valid but has a low priority and won't be fixed in the current release cycle, it is postponed or Deferred to a future sprint.

3. Duplicate: If the same bug has already been logged by another team member, it is marked as a Duplicate and closed out.