Rapid Multi-Transition Issues(5.1.7)

This visual flags issues that were transitioned through multiple workflow states within a very short time window. Two or more state changes within an hour are uncommon in day-to-day work; when they recur, a reviewer could ask whether the status history matches how the work moved.

This pattern is hard to spot manually, because each individual transition looks normal. The signal only becomes visible when you look at the timing between transitions on the same issue.

What you can conclude

• Issues with 4 or more rapid transitions (critical bucket) are the ones a reviewer would open first, to compare the status history with the work recorded on the issue.
• Clusters in specific weeks may coincide with sprint closures or reporting deadlines.
• A low or empty chart means few issues changed status several times within an hour.

How this chart works

Weekly stacked bar chart of issues that had 2 or more status-transition events within a 1-hour window on the same issue. Buckets: ≥ 4 transitions (critical), 3 (high), 2 (medium). Rapid cycling is detected by measuring the gap between consecutive status events per issue. Each burst's transitions are also counted by the type of account Jira reports for whoever made them (person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded). The bars still count issues, because one issue's bursts can mix types; the transition counts by type are listed beside them, people's first.

The week in progress is shown at its value so far. Because the week is not yet complete, it covers only the events recorded so far and can move in either direction as the week closes. A week that falls only partly inside the selected date range is drawn and marked partial, so a short first week is visible as a short week rather than read as a fall.