Rapid-transition issues(5.1.3)
KPINumber of tickets with at least one rapid burst: a chain of two or more status changes whose consecutive gaps are each under an hour. A burst records how fast the statuses changed, not why; a reviewer could ask whether the chain matches how the work moved. This total covers every week in the selected range, including the week in progress. The ticket count stays the headline, because one ticket's bursts can mix account types. The transitions behind it are listed beside it by the type of account Jira reports for whoever made them, people's first, then transitions by apps such as Automation for Jira, service-desk customers and accounts Jira returned no type for, each counted on its own.