Stuck-in-Status Detector(3.1.6)

Transition counts only see issues that are moving. An issue that has sat in "In Review" for 18 days without a status change does not appear in any of them, although it is still open.

This detector lists those issues directly: every open issue that has been in its current status much longer than that status usually holds an issue, ranked by how far past that point it is.

What you can conclude

• Issues at the top of this list have sat in their status longest relative to its usual stay; the open question for each is what it is waiting on.
• A long list of stuck issues in the same status (e.g. all stuck "In Review") puts the wait at that specific stage; a reviewer could ask what that stage waits on.
• The last actor column names the account that moved each issue into its current status, the first person who can say what it is waiting on; it does not say who is responsible for the wait. Where that account is an app by Jira's own record, such as Automation for Jira, the question goes to whoever administers that app.

How this chart works

Ranked alert list showing issues where the time in current status exceeds 2.5× the median time for that status. That median is a survival median over every stay ever recorded in the status, the stays still running today included, so a status most issues never leave is not read as a fast one, and it is never shorter than one day; that status means the same workflow status in your workspace, matched on Jira's own status ID rather than on the status name, so two same-named statuses in different workflows are never averaged together. A status with fewer than five recorded stays, or one where fewer than half of them have ended, is compared against the workspace-wide reference instead, the time within which nine in ten stays across all open-work statuses had ended, and each row names the reference it used. Where the workspace has no such reference either, the status appears as an information row with its issue count and median age, and nothing in it is flagged. Each issue is followed by the issue itself rather than by the key it carries, so an issue that moved to another project and took a new key there appears once, under the key it has today, and a key it no longer uses is not listed beside it. Only open issues are counted: an issue counts as open when the latest status its events record is in Jira's To Do or In Progress category, so deleted issues, issues in a project moved to the trash or deleted, and issues whose events record no status that maps to a Jira status category are not listed. An issue is listed only when MetaFrazo captured its move into the status it is in now, because otherwise its time in that status is unknown: an issue that has sat in one status since before MetaFrazo began receiving events is not listed, and neither is an issue whose move back into its current status was not captured. Columns include: issue key, project, current status, last actor, days stuck, and severity. The last actor is labeled with its type as Jira reports it: person, app, customer, unknown when Jira returned no type, erased, or system when no actor was recorded; information rows carry none. Ordered by days stuck descending.