Bug Life Cycle

There are various stages of bug life cycle. The status caption may vary depending on the bug tracking system which you are using. The main stages of the bug life cycle are given as-

New:  When QA find a bug it and files it as new bug.

Open:  When QA files a bug then development team verified this issue and if issue is valid then its status would be open.

Now TL of development team can takes following action against the bug.

Assigned: Bug status is assigned When TL assigned it to a developer.

Deferred:  If the bug is not related to current build or cannot be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred.

Resolved/Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.

 Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as ‘Reopen’ so that developer can take appropriate action.

 Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as ‘Closed’.

Rejected/Invalid: Sometimes developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation.

 

 

                                                                Bug life cycle