Stuck Status Detector(1.8)

This tile highlights tickets stuck in one status longer than is healthy, across all your projects. Spotting them early is how you keep a localized stall from spreading into a sprint-wide bottleneck.

What you can conclude

• Tickets parked in review or QA for days point to a flow bottleneck that needs a nudge.
• A rising count is an early warning that delivery for the sprint may be at risk.
• A low count suggests work is moving through statuses at a healthy pace.

How this chart works

The tile counts tickets that have remained in the same status more than twice as long as that status usually holds a ticket, aggregated across all your projects. Each ticket is counted once: it is followed by the issue itself rather than by the key it carries, so a ticket that moved to another project and took a new key there is listed under the key it has today, and the key it no longer uses does not appear beside it as a second stuck ticket. What counts as usual is read from the status's own history in your workspace: every stay any ticket has ever made in that same workflow status, matched on Jira's own status ID rather than on the status name shown on the board, including the stays that are still running today, so a status most tickets never leave is not mistaken for a fast one. The reference is the point at which half of those stays had ended (a survival median), and it is never shorter than one day. Two statuses in different workflows can carry the same label and behave nothing alike, so comparing a ticket against the wrong one is how a slow-by-design stage gets flagged while a genuinely stalled ticket does not. A status with fewer than five recorded stays, or one where fewer than half of them have ended yet, has no usual duration of its own; its tickets are compared with the workspace-wide reference instead, the time within which nine in ten stays across all your open-work statuses had ended, and each listed ticket shows which reference it was compared against. Where the workspace has no such reference either, the status is shown as information, with its ticket count and median age, and nothing in it is flagged. An empty tile is a measured answer, not missing data: it means no ticket is currently sitting more than twice as long as its reference.