Sobes.tech
Interview Help
Resources
Interview Preparation
Resources
Job Search
Resources
Legal
Back to questions
Junior

What happens to a bug report after it is created?

sobes.tech AI

Answer from AI

After a bug report is created, it goes through the following lifecycle:

  1. New / Open: The bug report is created and awaiting review.
  2. Assigned: A responsible developer is assigned to fix the bug.
  3. In Progress / In Development: The developer is working on fixing the bug.
  4. Fixed / Resolved: The developer has completed the fix and submitted the code for testing.
  5. In Testing / To Be Verified: The bug report is handed over to the tester for verification of the fix.
  6. Verified / Closed: The tester confirms that the bug is fixed and no longer reproduces. The lifecycle is complete.
  7. Reopened: The tester finds that the bug still reproduces and returns it to the developer for further work.
  8. Rejected / Declined: The bug report is rejected by the developer or manager due to:
    • Not a bug
    • Duplicate
    • Cannot reproduce
    • Obsolete / Won't fix
    • Suggestion
  9. Deferred / Postponed: Fixing the bug is postponed until the next release or sprint due to low priority or other reasons.

This cycle may vary slightly depending on the bug tracking system used (e.g., Jira, Bugzilla) and the processes adopted by the team.

PreviousNext