Enlisted below are few bug statuses along with their descriptions:

• New: When the defect or bug is logged for the first time it is said as New.
• Assigned: After the tester has logged a bug, his bug is being reviewed by the tester LEAD and then it is assigned to the corresponding developer team.
• Open: Tester logs a bug in the Open state and it remains in the open state until the developer has performed some task on that bug.
• Resolved/Fixed: When a developer has resolved the bug, i.e. now the application is producing the desired OUTPUT for a particular ISSUE, then the developer changes its status to resolved/fixed.
• Verified/Closed: When a developer has changed the status to resolved/fixed then the tester now tests the issue at its end and if it’s fixed then he changes the status of the bug to ‘Verified/Close’.
• Reopen: If a tester is able to REPRODUCE the bug again i.e. the bug still exists even after fixing by the developer, it’s status is marked as reopen.
• Not a bug/Invalid: A bug can be marked as invalid or not a bug by the developer when the reported issue is as per the functionality but is logged due to misinterpretation.
• Deferred: Usually when the bug is of minimal priority for the release and if there is lack of time, in that case, those minimal priority bugs are deferred to the next release.
• Cannot Reproduce: If the developer is unable to reproduce the bug at its end by following the STEPS as mentioned in the issue.

Enlisted below are few bug statuses along with their descriptions: