Page Comparison

Definition (Hover Text)

measures number of defects for each priority defined in a project

Source Tools

Jira, Azure Boards

Graph type

Line

Filters

Hover Format on KPI

Sprint Name:

P1: <<Value>>

P2: <<Value>>

P3: <<Value>>

P4: <<Value>>

Fields on Overlay

Sprint Name

Defect ID

Issue Description

Priority

Business Logic

Calculation Formula

No. of defects linked to stories in the iteration grouped by priority

Trend

Lower the count, better is the ‘Quality’

Maturity Levels

-

Instance level thresholds

-

Global Configurations- (Field Mapping)

Processor Fields

NA

Mandatory fields

Issue Type Mapping

Whenever we update the defect mapping and issue type mapping, whether we add or remove any issue type, we must run the processor. This is necessary to show the changes in the KPI.

Defect Mapping :

Image Added

Mandatory fields

Project Settings

1. Navigate to Project Settings: Start by going to the Project Settings in your application.

2. Access the Mapping Section: Within Project Settings, find and click on the Mapping option.

3. Mandatory Field: In the Mapping section, you’ll find the Mandatory Field. This is where you’ll configure the necessary global mapping fields.

4. Configure the Fields:

Defect Mapping :

• Issue Type to identify Defect - all the issue type that signify defect

Image Added

How to Validate KPI

Suggested ways of working

Sample JQLs

project = "Your Project Name" AND issuetype = Bug AND Sprint in openSprints() ORDER BY priority DESC

Benefits of KPI

How does the KPI help

The Defect Count by Priority KPI helps teams prioritize and allocate resources effectively by measuring the number of defects based on their priority level. This leads to improved product quality, reduced costs, and increased customer satisfaction by addressing high-priority defects promptly and identifying areas for process improvement.