State-Skip Detection

This visual detects tickets that jumped directly from an open state straight to done — skipping every step in between. In most workflows, this means the ticket was never actually worked on, or the state history was manipulated to make it appear complete.

State-skipping is one of the clearest indicators of governance failure at the project level. When it concentrates in a specific project, it often points to a team that is under pressure to close tickets quickly, or one that has not internalised the workflow process.

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.
• 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. Use the filters to narrow by date range or specific project.