Generated: 2026-03-02 11:39 EST | Data Source: JIRA | Tickets Analyzed: 1131
Time from defect creation to last transition to Done (Done / Closed / Resolved / Verified). This is the total time a defect exists before being resolved, from the customer's perspective.
This report includes Bug, Defect, and Sub-defect issue types. Other types (Story, Task, etc.) are excluded from the analysis.
Median is the middle value — 50% of defects resolve faster. P85 (85th percentile) is where 85% of defects resolve faster — it captures the typical worst case while excluding outliers.
Defects are assigned to the sprint in which they were resolved (last Done transition), not the sprint in which they were created. This shows when defects were actually fixed.
project = LOPS AND "products[select list (multiple choices)]" IN (tfMRD, "Latitude (tfMRD)") AND "team[team]" = fee007ac-475e-494f-b3b7-91697cf32c09
Median and P85 defect resolution time per sprint. The rolling average smooths sprint-to-sprint variation. Lower is better — faster defect resolution means higher quality delivery.
Number of defects resolved (bars) and story points resolved (line) per sprint. Higher throughput combined with lower resolution time indicates improving defect management.
Median resolution time for each priority level. Higher priority defects should resolve faster. Large gaps between priorities may indicate prioritization is not being reflected in resolution speed.
| Priority | Count | Median (days) | P85 (days) |
|---|
Median resolution time for each defect issue type. Different defect types may have different resolution characteristics.
| Issue Type | Count | Median (days) | P85 (days) |
|---|
Resolved defects sorted by resolution time (longest first), filtered to the selected sprint range. Resolution time cells are color-coded: >21 days, >14 days, ≤14 days.
| Key | Summary | Type | Priority | Resolution (d) | Points |
|---|