Inactive High-Priority Issue Detector(3.3.8)

A high-priority issue that hasn't had a single event in seven days is not being worked on. It may be forgotten, blocked, or deliberately parked — but in any of those cases, it represents unacknowledged risk. This detector surfaces those issues directly, ranked by priority and then by how long they have been inactive.

What you can conclude

• Every issue on this list has already gone at least seven days without a recorded event, so the question is not whether it has stalled but why. The rows carrying the tightest response-target band — the 0h target ones — are the ones to ask about first.
• High-priority issues with 7+ days of inactivity should be either reassigned, descoped, or explicitly acknowledged as blocked.
• A clean list with no entries indicates active management of high-priority work — a strong governance signal.

How this chart works

Ranked alert list showing High and Highest priority open issues with no events in the past 7 days. 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. An issue moved to another project is listed once, under its current key, and its days inactive count from its most recent event under any of its keys. Sorted by priority then by inactivity duration. Shows issue key, project, current status, priority, SLA tier, and days inactive. SLA tier is a MetaFrazo-defined response-target band read from the issue's current priority: Highest priority shows as a 0h target and High priority as a 4h target. It describes how quickly this list suggests someone should look, it is not a service-level agreement you hold with anyone, and it does not change as an issue ages — days inactive is the only elapsed-time measurement on the list. An issue's current priority is the latest priority its events record; for an open issue whose events record none, it is the priority MetaFrazo read from Jira, as it stood on the day it was read. An issue with neither cannot appear here.