Bug life cycle have following stages. 1. New ---> when QA member identify and raise a bug. 2. Assign --> this stage we assign the bug 3. OPEN --> When member of dev team to which it get assinged accepts the bug. 4. REJECTED -->if bug is not relevent according to development team member status changes to rejected. under rejection stage it can be move to two different status. 1. Duplicate --> if the same bug is raised by someone else also. 2. Defered --> when it is deicided that that particular functionality will move to production in next release cycle. 5. Fixed--> after performing the fixation in code and after doing unit testing development team member changes the status to fixed and assigned to tester. 6. Test OK --> after performing the testing process if tester finds that bug is fixed. it closes the bug issue raised. 7. Reopen --> if tester finds the same bug again it's status changes to reopen and get assigned to developer with proper evidences. 8. Close --> After doing testing if issue get resolved . QA team member closes that bug after providing proper evidences.