Overview | |||||
---|---|---|---|---|---|
Definition (Hover Text) | It shows the number of defects reopened in a given period against the total number of defects closed. | ||||
Source Tools | Jira | ||||
Graph typeSingle Stats | Line Chart | ||||
Filters | Priority | ||||
Hover format on KPI |
| ||||
Filters | Priority | Fields on Explore |
| ||
Business Logic | |||||
Calculation Formula | All defects created in the last 12 months are considered in the calculation | Trend | NA | Maturity Levels | NADefect Reopen Rate (%) = (Reopened Defects / Total Resolved Defects) × 100 |
Trend | A decreasing trend is desirable | ||||
Maturity Levels | Defect Seepage Rate maturity is assessed by averaging data from the last 5 sprints. This helps in understanding the stability and improvement over time. M1 - >= 20% M2 - >=10-20% M3 - >=5-10% , M4 >=2-5% , M5 <2% | ||||
Instance level thresholds | NA | ||||
Configurations | |||||
Processor Fields | NA | ||||
Mandatory fields | Status to identify Closed defects | ||||
How to Validate KPI | |||||
Suggested ways of working | you can use JQL to find issues where the status transitioned from a closed or resolved state back to an active state. | ||||
Sample JQLs | Project in ("<jira project name>") and issuetype in (Defect) and status CHANGED FROM closed TO open | ||||
Benefits of KPI | |||||
How does the KPI help |
| ||||
Best Practices | |||||
Insudtry-aligned best practices to bring down reopen rate | Improve Defect Triage and Root Cause Analysis | ||||
Enhance Defect Reporting Quality - Clear steps to reproduce ,expected vs actual behavior ,logs, screenshots, and environment details | |||||
Enforce DoD for defect fixes | |||||
Link defects to existing or new test cases to avoid coverage gaps. | |||||
Make quality everyone’s responsibility—not just QA's. |
Content Comparison
General
Content
Integrations