Punctuality of Reported Defects

Step 1: Begin by adding two distinct Data Sources, labeled as ‘All Bugs’ and ‘False-Positive Bugs.’ Ensure that the ‘False-Positive Bugs’ Data Source is configured to display only issues with the appropriate Resolution, as demonstrated in the data segmentation screens below.

Step 2: Proceed to select the ‘Number of Issues’ metric.

Step 3: Opt for Data Source ‘B’ (named False Positive Bugs) for the ‘Number of Issues’ metric.

Step 4: Choose ‘Resolved by Week’ for Display by.

Step 5: Choose ‘Reporter’ for Group by, to group the data by the individuals who raised the Jira issues.

Step 6: Employ the Cumulative mode, allowing the data to accumulate with each passing week.

Step 7: Activate the Target feature and choose the ‘% of Total’ target type.

Step 8: Select the ‘Per x-axis item’ results presentation, allowing you to track the KPI’s progression towards the predefined target.

Step 9: Set the max acceptable false positive rate per reporter to ‘5%’.

Step 10: For target value calculation, choose Data Source ‘A’ – ‘All bugs’.

Step 11: Toggle the ‘Exceeding is’ option to ‘Bad,’ signifying whether the objective is positive or negative. If the target is surpassed, the outcomes will be highlighted in red.

Step 12: (Optional) In the ‘More Settings’ section, activate and set the ‘Warning Threshold’.

Open

Step 13:  (Optional) Activate the ‘Custom Target Label’ and assign a label indicating that the target is negative. This communicates that exceeding the target is deemed a failed objective.