Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

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

-

Configurations

Processor Fields

NA

Mandatory fields

  • Issue Type Mapping

    • Issue types which will have linked defects  eg; Story, TechStory

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.

C

  • No labels