Unowned High-Priority Issue Clock(3.1.9)

A high-priority issue with no assignee carries urgency and no ownership, and the event stream records both—whether the priority was set when the issue was created or raised later. For an open issue whose events record no priority, MetaFrazo reads its priority from Jira and uses it as it stood on the day it was read. A Highest-priority issue counts as past its window from the moment it has no owner. For High-priority issues, the SLA window is four hours. After that, the issue has gone longer without an owner than the threshold allows, regardless of whether any work has been done on it.

This visual shows which of your most critical issues have no owner right now, and for how long.

What you can conclude

• For a Highest-priority issue listed here, a reviewer could ask who is expected to own it and whether its priority still reflects the work.
• Large values in the Hours Unowned column are the longest stretches in the period during which a high-priority issue had no assignee.
• A project cluster in this visual that grows over time means the unowned issues are concentrated in that project rather than spread across the portfolio.

How this chart works

Ranked table showing current unowned High and Highest priority issues. An issue counts as open when the latest status its events record is in Jira's To Do or In Progress category. An issue deleted in Jira, or in a project moved to the trash or deleted, is not counted, and an issue whose events record no status at all is left out. Highest-priority issues are listed first and, within each priority, the issue that has been unowned longest is at the top. SLA thresholds: Highest = 0 hours (immediate), High = 4 hours. Hours Unowned is highlighted red when the SLA threshold is breached. Hours at Priority counts from the last recorded priority change, else from creation; a priority read from Jira had no change recorded since the issue was created, so it counts from creation. Hours Unowned counts from the first event that records the issue without an assignee after it last had one, else, for an issue that never had an assignee, from creation. An issue counts as owned when the latest assignee its events record is set, from a recorded assignee change or from the issue details an event carries; an assignee whose account was later erased, an app, or a customer account still counts as an owner. Creation is the one MetaFrazo recorded or, for an issue created before MetaFrazo was installed, the creation time Jira records; a dash means neither MetaFrazo nor Jira recorded when the issue was created.