Time Spent in Rework KPI

Time-Spent-In-Rework-KPI-Jira-Dashboard.png

Step 1: Incorporate 2 Data Sources – one encompassing all issues and the other exclusively for Bugs. Use the data segmentation options. Filter your second data source for this report by selecting only the ‘Bug’ Issue Type, as demonstrated in the image.

Step 2: Opt for the metric “Σ Time Spent (h)”.

Step 3: Define Data Source B (Bugs) for the metric calculation.

Step 4: Specify ‘Display by’ as ‘Assignee’ for the x-axis representation.

Step 5: (Optional) Choose ‘Priority’ for Stacked by to get even deeper insights.

Step 6: Activate the Target section and navigate to the ‘% of Total’ tab.

Steps 7 & 8: Define the target level value. In our case it is 20 %. Choose data source A (All Issues) for calculating the target metric. By default, the target metric is ‘Current Metric,’ which translates to utilizing ‘Σ Time Spent (h)’.

Step 9: Specify a negative target by selecting Exceeding is: “Bad”. This configuration means that exceeding the target level will result in a failure to achieve, highlighted in red.

Step 10: (Optional) In the ‘More Settings’ section, enable and customize the ‘Warning Threshold’ option.

 

Time-Spent-In-Rework-KPI-Settings-Screen.png

Watch the video tutorial at our website: Time spent in rework - Track objectives in Jira