Critical stuck issues(3.1.2)

How many open tickets, open by the latest status their events record, have sat in their current status more than 5× the reference stay for that same status: the survival median of every stay recorded in that workflow status in your workspace, never shorter than one day, or the workspace-wide reference where the status has too little history, where that same status means the same workflow status matched on Jira's own status ID rather than on the status name. The Stuck-in-Status Detector below lists everything past 2.5× the median and this counts only the far tail of it, so the table can hold rows while this reads zero. Each ticket is counted once, 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 counted under the key it has today and not a second time under the old one. A ticket whose move into its current status was never captured is not counted, because its time in that status is unknown. The severity classification (Warning, Critical) is the view's own, not a second calculation on the page.