Versions Compared

Version Old Version 1 New Version Current
Changes made by

Pranav Barar (Unlicensed)

Pragyan Sundarray

Saved on

Key

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

Overview

Definition (Hover Text)

It tracks issue progress and identifies areas for improvement by calculating work versus wait time percentageshows 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

Line

Y-Axis: Days

X- Axis: < 1 week, < 2 Weeks, <1 Month, < 3 Months, <6 Months

Filters

Issue type

Hover Format on KPI

<X> %

Fields on Overlay

Enhancement requiredSingle Stats

  1. Reopened defects/ Total closed defects (fraction)

  2. Reopen Rate (in percentage)

  3. 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

Directly Proportional - Higher Flow Efficiency is considered good; Lower Flow Efficiency is considered badNA

Maturity Levels

N/A (To be defined in future)NA

Instance level thresholds

N/ANA

Configurations

Processor Fields

NA

KPI Specific Mandatory fields

Status to identify Wait statusesStatus to identify Closed statusesClosed 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.