Bug & Defect Life Cycle
Dashboard
Topic 4/13
Home โ€บ Testing โ€บ Bug & Defect Life Cycle

๐Ÿ› Bug & Defect Life Cycle

Bug statuses, Severity vs Priority matrix, sample bug report, and JIRA workflows.

Bug Life Cycle Status Flow

A defect transitions through various states from discovery to resolution.

Status Description Action Owner
New Defect logged by QA engineer QA Engineer
Assigned Assigned to developer for review Test Lead / Manager
Open / In Progress Developer analyzing & fixing code Developer
Fixed Code fix committed to build Developer
Pending Retest Deployed to QA test environment DevOps / QA
Closed QA retested fix successfully QA Engineer
Reopened Defect still reproduces upon retest QA Engineer

Severity vs Priority Matrix

Severity measures technical impact on system functionality. Priority determines fix urgency for business deadlines.

Scenario Example Severity Priority
Payment gateway crash during checkout High (Critical) High (Immediate)
Company logo misaligned on Homepage Low (Cosmetic) High (Brand Impact)
Data export fails for rare 10-year old archived user High (Data Failure) Low (Rare Edge Case)
Typo in terms of service modal text Low (Cosmetic) Low (Minor)

Writing a Professional Bug Report

A comprehensive bug report provides clear steps to reproduce for fast developer resolution.

bug-report-jira.txt Text
Bug ID: BUG-402
Title: Checkout button unresponsive when adding duplicate coupon items
Environment: Staging v2.4, Chrome 126 Windows 11
Severity: High | Priority: High

Steps to Reproduce:
1. Navigate to /cart
2. Add item 'PROD-100'
3. Apply coupon code 'DISCOUNT50'
4. Re-enter coupon code 'DISCOUNT50' and click Checkout

Expected Result: Error message 'Coupon already applied'. Checkout proceeds.
Actual Result: UI freezes, Checkout button remains disabled, Uncaught JS TypeError in console.

Logs: TypeError: Cannot read property 'discount' of null at cart.js:142