The Bug Lifecycle: From Birth to Grave
A bug report is not just a document. It's a living ticket that moves through states, changes hands between teammates, and can be born again as a "Reopened" if the fix doesn't hold. Understanding this lifecycle turns you from a passive observer into an active steward of quality — someone who can read a Jira board and know exactly what's happening with every defect.
What You'll Learn
- The standard bug status flow from New to Closed
- The crucial difference between Severity (technical impact) and Priority (business urgency)
- How to handle a rejected or "Not a Bug" verdict professionally
Lessons in This Module
-
Bug Statuses: The Adventures of a Jira Card — Walk through the full status lifecycle and understand who is responsible at each stage.
-
Severity vs Priority: The Most Misunderstood Pair — Learn to classify bugs correctly and understand why a cosmetic typo on the homepage can be High Priority even though it's Low Severity.
-
What to Do When Your Bug Gets Rejected — Develop the professional response toolkit for "Not a Bug," "Works as Designed," and "Cannot Reproduce" verdicts.
Complete all three lessons to earn the Lifecycle Tracker badge.