The bug life cycle is the process managing the events starting from creating a new bug until it is closed.
Below are the typical bug lifecycle states but might have different named states based on the bug tool:
- New (state) → sets when filed a bug by QA or re-opened.
- Assign → sets when assigned to a developer by QA/QA manager/Dev Manager/Developer.
- Evaluate and in-progress → sets by the developer during evaluation.
- Fixed → sets by the developer when code change happened for bug fix.
- Duplicate bug → sets by the developer if already that bug exists.
- Not a bug → sets by the developer if it is not a bug.
- Not reproducible → sets by the developer if it is not reproduced.
- Verified → sets by QA after verified as OK.
- Re-open to New → sets by the developer
- Re-open to New → sets by clarifying how to reproduce again by QA
- Closed → by QA/Filer after verification.