Definition (Hover Text)

The Defect Count by Priority KPI measures the number of defects for each priority level defined in a project.

Source Tools

Jira, Azure Boards

Graph type

Line Chart

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

A lower count of defects, especially in higher priority categories, indicates better quality.

Maturity Levels

NA

Instance level thresholds

Target KPI Value denotes the bare minimum a project should maintain for a KPI.

Global Configurations- (Field Mapping)

Processor Fields

NA

KPI Specific fields

Workflows 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

Prioritization:

• Helps the team identify and prioritize the most critical defects, ensuring that the most impactful issues are addressed first.

Trend Analysis

• By tracking defects by priority, the team can identify recurring issues and areas that need improvement.

Risk Management

• Helps in assessing the risk associated with defects and planning mitigation strategies accordingly.

Improved Product Quality

• By focusing on and resolving high-priority defects, the overall quality of the product improves, leading to higher customer satisfaction.

Best Practices

Clear Priority

• Ensure that priority levels are clearly defined and understood by all team members to maintain consistency.

Regular Monitoring

• Regularly monitor and review the defect counts by priority to identify trends and take corrective actions promptly.

Effective Communication

• Maintain open communication between the development and testing teams to ensure that defects are accurately prioritized and addressed