Transition Count

To understand where the flaw in the workflow lies, in addition to cycle time and time in status for each issue, it’s crucial to view how many times an issue has transitioned to each status. If an issue transitions to the same status more than once, it may indicate a back-and-forth process. When this happens two or three times, it can be considered part of the normal workflow, but more transitions may signal a problem.

The number of transitions considered "normal" varies from team to team and should be determined based on experience.

Now you can examine the number of status transitions for each issue within the chart's scope and see it broken down by status, allowing you to investigate potential issues:

Open

To analyze patterns and establish health benchmarks, you can sort issues by the number of transitions:

Open

Atlassian Team field support

For those who have adopted Atlassian's new feature to assign work to a specific team, we’ve started supporting the Atlassian Team field in the breakdown and issues list:

Open

Loading progress indicator

Since this version, you can see the loading progress to track how much data has been loaded and when the chart is ready to use:

Open

Fixed an issue with duplicated issue types in the issues filter

Fixed Cycle Time chart crashing for specific settings configuration

Resolved an issue where the Cycle Time chart crashed for specific settings configurations, specifically Time in Status chart view with configured columns in the issue list. The chart now correctly works without crashing as expected.

Fixed Cycle Time chart breakdown data when one interval is available on the chart

Resolved an issue where breakdown data was not visible in the Cycle Time Trend view when only a single interval was present on the chart. The data now displays correctly.