State-Skip Detection(5.1.9)

This visual detects tickets that jumped directly from an open state straight to done — skipping every step in between. The events show the ticket passed through no working state; whether the work happened elsewhere, or not at all, is the question a reviewer could ask.

State-skipping is one of the clearest signals this data carries at the project level. When it concentrates in a specific project, it often lines up with pressure to close tickets quickly, or with workflow stages the team does not use; which of the two is the question to ask.

What you can conclude

• Projects with a consistently high bar here need a process review — tickets are being closed without going through the defined workflow.
• A single spike may reflect a migration or bulk-close event — check the dates for context.
• Skips made by an app account, such as an Automation for Jira rule that closes issues, are shown with their type beside people's skips; the question they raise is how that rule is configured.
• Zero state-skips across all projects means the workflow is being followed as intended.

How this chart works

Horizontal bar chart of issues that transitioned directly from an open state (To Do, Open, Backlog) to a terminal state (Done, Closed, Resolved) within a single changelog event, bypassing any intermediate states. Each bar represents one project. Each skip also carries the type of account that made it (person, app, customer, unknown, erased, or system where no actor was recorded), so people's skips are counted apart from the others. Use the filters to narrow by date range or specific project.