Cycle Time KPI

Measuring avg. time between the start and the end of each stage of the process is key to identifying bottlenecks.

Please check below the sample KPI configuration that uses “Create” date for cycle start and “Resolve” date for the end of the cycle.

Find below the step by step configuration instructions:

Step 1: Identify the JIRA issues to analyze and add them to the data source.

Step 2: Select the metric ‘Time between’ with ‘Date from’ field set with ‘Created’, and ‘Date to’ field set with ‘Resolved’.

Step 3: Select average calculation based on the number of issues.

Step 4: Set ‘Display By’ with ‘Components’.

Step 5: (Optional) Set ‘Group by’ field with ‘Created’ date and ‘Month’ granularity.

Step 6: Change chart orientation to vertical. The height area is not restricted and allows more items to fit better on the x-axis.

Step 7: Switch on Target section and keep the ‘Fixed’ tab selected.

Step 8: Select results to be evaluated per x-axis item. They will be visible on the chart for each available combination of Component & Group.

Step 9: Set Target as negative by setting ‘Exceeding to’: to Bad. That means that when the achieved result exceeds the target level it will be considered as negative and will be colored in red.

Step 10: Set target level value.

Step 11: Expand the ‘More Settings’ section and enable the ‘Warning threshold’, that colors in amber values above it and below the target level.

Step 12: Expand the ‘More Settings’ section and enable the ‘Custom Target Label’. Set label that will indicate the target is negative, e.g. Fail.

Recording: Please check the following recording with detailed configuration settings.

Following this 3 min JIRA configuration will help you to enrich your JIRA data by capturing more date events from the workflows, which may be analyzed afterwards with the Performance Objectives dashboard gadgets.