Definition (Hover Text)

gives an idea about the speed at which the team closes the raised defects.

Source Tools

Jira, Azure Boards

Graph type

Line + Column Chart

Filters

Total Defects, Added defects

Hover Format on KPI

Created Defects - <<Value>>

Resolved Defects - <<Value>>

Resolved Percentage -

Fields on Overlay

• Sprint Name

• Created Defect ID

• Issue Description

• Defect added after Sprint

• Resolved Status

Business Logic

Calculation Formula

Created defects consider all defects which are initially tagged to the Sprint or are added to the sprint in between

Closed defects are the completed defects i the sprint out of the created count

Trend

Higher the Resolved trend, better is the quality

Maturity Levels

Compare Resolved defects with Created Defects

M1: Velocity is 0-40%

M2: Velocity is 40-60%

M3: Velocity is 60-75%

M4: Velocity is 75-90%

M5: Velocity is >90%

Instance level thresholds

-

Configurations

Processor Fields

• Defect Mapping

  • Issue Type to identify defects 

Mandatory fields

• Workflow Status Mapping

  • Status to identify Completed Issue

How to Validate KPI

Suggested ways of working

Sample JQLs

Benefits of KPI

How does the KPI help

The Created vs Resolved KPI measures the balance between new issues or tasks created and those resolved, helping teams track productivity, identify bottlenecks, and ensure efficient work management. By maintaining a healthy balance, teams can improve efficiency, meet deadlines, and deliver high-quality results.