Bug Tracking & Resolution | Severity-Based Workflow
Bug tracking needs triage workflows and severity-based SLAs. GitScrum connects reported issues to code fixes with Critical (24h), High (1 week), Medium (backlog) prioritization.
6 min read
Effective bug tracking requires more than a simple list—it needs triage workflows, priority systems, and clear resolution paths. GitScrum's customizable workflows, severity labels, and Git integration create a complete bug tracking system that connects reported issues to code fixes and verified resolutions.
Bug Severity Levels
| Severity | Impact | Response Time | Examples |
|---|---|---|---|
| Critical | System down, data loss | Immediate | Login broken, payment fails |
| High | Major feature broken | 24 hours | Export fails, dashboard empty |
| Medium | Feature degraded | 1 week | Slow performance, UI glitch |
| Low | Minor issue | Backlog | Typo, cosmetic issue |
Bug Tracking Workflow
BUG LIFECYCLE IN GITSCRUM
1. NEW BUG REPORTED
┌─────────────────────────────────────────────────┐
│ Sources: │
│ ├── Customer support tickets │
│ ├── Internal testing │
│ ├── Automated monitoring │
│ ├── User feedback │
│ └── QA testing │
│ │
│ Initial Status: [New] │
└─────────────────────────────────────────────────┘
│
▼
2. TRIAGE (within 24h)
┌─────────────────────────────────────────────────┐
│ Actions: │
│ ├── Verify reproducibility │
│ ├── Assign severity level │
│ ├── Check for duplicates │
│ ├── Add labels and assignee │
│ └── Set priority │
│ │
│ Status: [Triaged] │
└─────────────────────────────────────────────────┘
│
▼
3. INVESTIGATION
┌─────────────────────────────────────────────────┐
│ Developer actions: │
│ ├── Reproduce locally │
│ ├── Identify root cause │
│ ├── Estimate fix effort │
│ └── Document findings │
│ │
│ Status: [In Progress] │
└─────────────────────────────────────────────────┘
│
▼
4. FIX IMPLEMENTATION
┌─────────────────────────────────────────────────┐
│ ├── Code fix with tests │
│ ├── Code review │
│ ├── Merge to main │
│ └── Deploy to staging │
│ │
│ Status: [In Review] │
└─────────────────────────────────────────────────┘
│
▼
5. VERIFICATION
┌─────────────────────────────────────────────────┐
│ ├── QA verifies fix on staging │
│ ├── Original reporter confirms │
│ └── Deploy to production │
│ │
│ Status: [Verified] │
└─────────────────────────────────────────────────┘
│
▼
6. CLOSED
┌─────────────────────────────────────────────────┐
│ ├── Notify stakeholders │
│ ├── Update documentation if needed │
│ └── Consider prevention measures │
│ │
│ Status: [Closed] │
└─────────────────────────────────────────────────┘
Bug Report Template
BUG REPORT STRUCTURE
┌─────────────────────────────────────────────────┐
│ Title: [Component] Brief description │
│ Example: [Checkout] Payment fails for PayPal │
│ │
│ Labels: [bug] [severity-high] [payments] │
│ │
│ SEVERITY: High │
│ PRIORITY: P1 │
│ REPORTER: @username │
│ ENVIRONMENT: Production │
│ │
│ SUMMARY: │
│ One sentence describing the issue. │
│ │
│ STEPS TO REPRODUCE: │
│ 1. Navigate to checkout │
│ 2. Select PayPal as payment method │
│ 3. Click "Complete Order" │
│ 4. Observe error │
│ │
│ EXPECTED BEHAVIOR: │
│ Order completes and confirmation displays. │
│ │
│ ACTUAL BEHAVIOR: │
│ Error message: "Payment processing failed" │
│ Order not created, user stuck on checkout │
│ │
│ FREQUENCY: │
│ 100% reproducible │
│ │
│ AFFECTED USERS: │
│ All users selecting PayPal (~15% of orders) │
│ │
│ BROWSER/DEVICE: │
│ Chrome 120, macOS 14 │
│ (also confirmed on Safari, Firefox) │
│ │
│ ERROR LOGS: │
│ │
│ │
│ SCREENSHOTS/VIDEO: │
│ [attached] │
│ │
│ WORKAROUND: │
│ Users can use credit card instead │
└─────────────────────────────────────────────────┘
### Bug Board Configuration
BUG TRACKING BOARD
Columns: ┌────────┬────────┬──────────┬────────┬──────────┐ │ New │Triaged │In Progress│Review │ Verified │ ├────────┼────────┼──────────┼────────┼──────────┤ │ [BUG] │ [BUG] │ [BUG] │ [BUG] │ [BUG] │ │ [BUG] │ [BUG] │ [BUG] │ │ │ │ [BUG] │ │ │ │ │ └────────┴────────┴──────────┴────────┴──────────┘
Swimlanes by Severity: ┌─────────────────────────────────────────────────┐ │ 🔴 Critical (0 in New - target) │ │ ├── BUG-234: System timeout... │ ├─────────────────────────────────────────────────┤ │ 🟠 High (respond < 24h) │ │ ├── BUG-456: Payment fails... │ │ ├── BUG-457: Export broken... │ ├─────────────────────────────────────────────────┤ │ 🟡 Medium (respond < 1 week) │ │ ├── BUG-567: Slow search... │ ├─────────────────────────────────────────────────┤ │ 🟢 Low (backlog) │ │ ├── BUG-678: Typo in... │ └─────────────────────────────────────────────────┘
Labels: ├── [severity-critical] ├── [severity-high] ├── [severity-medium] ├── [severity-low] ├── [regression] ├── [customer-reported] └── [needs-info]
### Bug Metrics Dashboard
BUG HEALTH METRICS
CURRENT STATE: ┌─────────────────────────────────────────────────┐ │ Open Bugs by Severity: │ │ Critical: 0 (target: 0) ✓ │ │ High: 4 (target: <5) ✓ │ │ Medium: 18 (target: <25) ✓ │ │ Low: 45 (target: <100) ✓ │ └─────────────────────────────────────────────────┘
RESOLUTION VELOCITY: ┌─────────────────────────────────────────────────┐ │ Severity Avg Time SLA Status │ │ ────────────────────────────────────────── │ │ Critical 4 hours 8h ✓ Meeting │ │ High 2 days 3d ✓ Meeting │ │ Medium 8 days 14d ✓ Meeting │ │ Low 21 days 30d ✓ Meeting │ └─────────────────────────────────────────────────┘
TRENDS: ┌─────────────────────────────────────────────────┐ │ This Week: │ │ New bugs: 12 │ │ Fixed bugs: 15 │ │ Net change: -3 (improving) │ │ │ │ Escape Rate (prod bugs from sprint): │ │ This sprint: 2 bugs (target: <3) ✓ │ │ Last sprint: 4 bugs │ └─────────────────────────────────────────────────┘
## Best Practices
1. **Triage within 24 hours** of report
2. **Write reproducible reports** with clear steps
3. **Assign severity consistently** with guidelines
4. **Allocate bug capacity** (10-20% per sprint)
5. **Track escape rates** to improve prevention
6. **Close the loop** with reporters
7. **Analyze patterns** for systematic fixes
8. **Celebrate bug-free releases** to motivate
## Anti-Patterns
✗ Bugs without reproduction steps ✗ All bugs marked "critical" ✗ No dedicated bug triage ✗ Bugs languishing untriaged ✗ Fixing symptoms not root causes ✗ No feedback to original reporter
``