The life cycle is a journey, and so is the bug life cycle. It is the journey of a defect from getting identified to getting fixed at the end. The process following which an organization finds a flaw and rectifies it may vary. It varies for different projects as no two bugs are identical, and their rectifying procedures are also different. Any bug detected by the team goes through a series of phases before it gets fixed. The process that the bug goes through includes the following steps. 1. New It is when a bug gets identified during the testing phase or by the end user. This newly identified bug gets assigned the status NEW. 2. Assigned It is the phase of bug identification by the tester and gets assigned as a task to an expert. The experts in the developer team with relevant experienced get the job. 3. Open In the open phase, the bug gets opened, and the developers start working towards fixing them. 4. Fixed Once the developer feels like he has found and fixed the issue, it travels to a fixed state and goes to the testing team again. 5.Re-Test Once the testing team runs different software tests to verify whether the bug has got fixed or not, it is the re-test phase. 6. Verified/closed If the tests run successfully, it gets verified that the bug doesn’t exist, and the task gets closed. However, if the tester needs more information, he can ask for it before closing the bug project. 7. Re-opened Phase If even a few of the tests are unsuccessful, the testing team sends it back to the developer, and they reopen the bug to fix it. This process continues until the bug gets fixed and the product is good to go into the market again. Every bug goes through this same phase before it gets fixed, and the system is good to use for the end user.