Bug Life Cycle.

1. New ticket logged is always assigned to Manager

2. Manager assigns the ticket to Developer

3. Developer marks the ticket as 'In Progress' and starts working on the ticket.

4. After development, developer moves the code to staging, and verifies code on staging.

5. Developer then marks the ticket as 'Development Complete' and assigns to QA for testing.

6. QA verifies fix on Staging, and if any issues found, generates a separate bug ticket is created and
assigned to Manager for scheduling. Relationship between the two tickets is also appropriately defined.

7. QA marks the ticket as 'Testing Complete' (after locking any bug tickets as above) and assigns back to
original developer.

8. Once the code is deployed to production, Developer verifies it on production.

9. Developer then assigns the ticket to QA to verify on production.

10. QA verifies the ticket on production, assigns it back to original developer and mark the ticket as
'Production Complete'

11. NO tickets is closed by anyone other than QA (or Manager)