Versions Compared

Version Old Version 1 New Version Current
Changes made by

Pragyan Sundarray

Pragyan Sundarray

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Definition (Hover Text)

It shows the number of defects reopened in a given period against the total number of defects closed.
The average reopened time to reopen is also available for all the reopened defects.

Source Tools

Jira

Graph type

Single StatsLine Chart

Filters

Priority

Hover format on KPI

  1. Sprint name

  2. Reopened defects/

  3. Total closed defects (fraction)

  4. Reopen Rate (in percentage)

  5. Average Time to Reopen (in hrs)

Filters

Priority

Fields on Explore

  1. Issue ID

  2. Issue Description

  3. Issue Status

  4. Priority

  5. Closed Date

  6. Reopen Rate

  7. Time taken to reopen

Business Logic

Calculation Formula

All defects created in the last 12 months are considered in the calculation

Trend

NA

Maturity Levels

NA

Defect 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

  1. Improves Code Quality: Tracking the defect reopen rate highlights recurring issues, enabling teams to focus on improving the initial fix quality and reducing the number of rework cycles.

  2. Identifies Process Gaps: It helps identify testing, requirements, or communication weaknesses that may lead to incomplete fixes or misunderstandings during development.

  3. Enhances Team Accountability: Monitoring reopen rates fosters accountability among team members by making the quality of resolutions visible and encouraging more thorough reviews and testing.

  4. Optimizes Resource Allocation: By reducing reopened defects, teams can save time and resources, allowing them to focus on new features and enhancements rather than rework.

Best Practices

How to avoid/reduce reopening of defects

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.