Defect Life Cycle

Explanation :
1. When anything thats a deviation from usual behavior/requirement occurs, a tester raises a defect which is in "Open" state. The tester should check in the available prod like environment if this defect is already existing in the production environment before marking the affected version.
2. If this issue is already present in production, then the first step is to check if this issue has already been reported in the previous releases, if not raise and mark the affected version as the current version and the production version in the defect details. Note that if a defect is already in production it may be deferred to the next release based upon the decision from business.
3. If this is not an existing issue in production, then its a new defect based on the code changes from the current release in which case the affected version can be marked as the Current relese version
4. After the tester has raised the defect and assigned to the release owner, the release owner would then assign this defect to the concerned developer who woul start the analysis of the defect
5. If in the analysis, the defect is found to be already reported then the defect is marked as duplicate and closed OR if the developer is unable to replicate the issue, then the developer should discuss it with the tester and if not reproducible then close it
6. After identifying the root cause of the defect, the developer starts fixing the code then the status of the defect is "In Development"
7. When issue is fixed and unit test cases passed, Developer should mark the defect as Development Complete and assign it back to the Release owner
8. The release owner would then check in the fix in the next build and after the deployment in the testing environment assigns it back to the tester
9. Tester would test the defect again based on all the positive and negative scenario around it
10. If the functionality is working fine after the fix, then the developer can mark the defect as closed OR if the defect is still persisting then again re-open the defect and assign it back to the developer