Stuck Status Detector(FEED:1.8)

Visual
Where to find it:Intelligence Feed
Standard edition
Open in dashboard

This tile highlights tickets that have sat in one status much longer than that status usually holds a ticket, across all your projects. It answers where work is waiting right now, and for how long.

What you can conclude

  • Several tickets listed in the same review or QA status put the wait at that stage; a reviewer could ask what the stage is waiting on.
  • A rising count means more tickets have passed twice their reference than before; the list shows which statuses they sit in.
  • A low count means few tickets are currently sitting more than twice as long as their reference.

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. Only open tickets are counted: a ticket counts as open when the latest status its events record is in Jira's To Do or In Progress category, so deleted tickets, tickets in a project moved to the trash or deleted, and tickets whose events record no status that maps to a Jira status category are not listed. A ticket is listed only when MetaFrazo captured its move into the status it is in now, because otherwise its time in that status is unknown: a ticket that has sat in one status since before MetaFrazo began receiving events is not listed, and neither is a ticket whose move back into its current status was not captured. 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 count of open tickets and their 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. Stuck-in-Status Detector JIRA:2.1.6 on the Workflow behavior page lists the same tickets, with their severity and last actor.