Punctuality of Reported Defects

In the realm of Quality Assurance (QA) and software development, ensuring timely and accurate reporting of defects is pivotal for maintaining customer satisfaction and optimizing the overall development process. This article delves into the creation of a comprehensive Punctuality of Reported Defects report in Jira, highlighting the integration of the Performance Objectives app to enhance QA practices, streamline reporting procedures, and ultimately elevate customer satisfaction.

To optimize the process of defect identification and reporting, it’s essential to set clear performance objectives. The primary goal is to minimize the occurrence of false-positive cases reported by the QA team, which can lead to unnecessary delays and resource waste. One way to do this is by getting better at finding and describing repeatable patterns. Performance Objectives and Performance Trend gadgets support Target calculation feature, making it easy to establish clear, real-time, and measurable goals for your QA team directly within your Jira dashboard.

Setting the Performance Objective to Address False Positives

The objective for this initiative can be defined as follows: “Ensure that a maximum of 5% of the total bugs reported by the QA team are categorized as false positives.” This entails actively addressing issues marked with resolutions such as ‘Not a Defect,’ ‘Duplicate,’ ‘Cannot Reproduce,’ or similar. By adhering to this goal, the development team aims to significantly enhance the accuracy and punctuality of reported defects.

Here’s how the rich data segmentation feature of the Performance Objectives: Charts for Jira app can be used to effectively filter issues with the appropriate resolution for creating such a report:

Punctuality of reported defects in Jira False Positives 2

Create Punctuality of Reported Defects Report in Jira

Let’s now generate a sample QA KPIs report within Jira, focusing on the total number of reported false positives over a specific timeframe. In this instance, we will use the Performance Trend gadget, although a comparable report can also be created using the Performance Objectives gadget.

Punctuality of reported defects in Jira chartpng

Below is a comprehensive, step-by-step guide showing the configuration process for generating a Punctuality of Reported Defects report in Jira using our app:

Step 1: Begin by adding two distinct Data Sources, labeled as ‘All’ and ‘False-Positives.’ Ensure that the ‘False-Positives’ Data Source is configured to display only issues with the appropriate Resolution.

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

Step 3: Opt for Data Source ‘A’ (named False-Positives) for the ‘Number of Issues’ metric.

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

Step 5: Choose ‘Reporter’ for Group by, to effectively segmenting 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.

Punctuality of reported defects in Jira settings

Step 7: Activate the Target feature.

Step 8: Choose the target type as ‘% of Total.’

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

Step 10: 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 11: Set the max acceptable false positive rate per reporter to ‘5%.’

Step 12: For target value calculation, choose Data Source ‘B,’ using the Jira issues named ‘All’.

Step 13: In the ‘More Settings’ section, activate the ‘Warning Threshold,’ which defaults to 50% of the target value.

Step 14: 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.

Punctuality of reported defects in Jira settings2

Video recording for QA KPIs report in Jira

Incorporating the Performance Objectives app into the defect reporting process within Jira can elevate QA practices and contribute to a more efficient and customer-centric software development lifecycle.

For additional inspiration on crafting and monitoring QA KPIs in Jira, consider exploring our KPI Examples page.

Start your 30 days free trial of Performance Objectives: Charts for Jira from Atlassian Marketplace.

logo gradient blue marketplace