Priority-Adjusted Breach Heatmap(3.5.7)

SLA breaches are not uniformly distributed. A project that meets its SLA for Medium issues but consistently breaches on High-priority ones has a specific capacity problem at the top of the queue — not a general delivery problem. This heatmap shows you exactly where the SLA failures are concentrated.

What you can conclude

• A dark cell at High or Highest priority for a specific project indicates a top-tier capacity failure — the team cannot keep up with its most urgent commitments.
• A project where only low-priority issues are breaching has a triage problem — high-priority work is being prioritized correctly but low-priority work is being forgotten.
• A uniformly light heatmap indicates consistent SLA compliance across all project-priority combinations — the healthiest possible state.

How this chart works

Heatmap with projects on one axis and priority levels on the other. Cell color encodes breach rate for delivered issues in that combination; a cell whose closures were all abandoned shows no rate and reports the abandoned count instead. The Unknown row groups tickets whose priority never appears in the event stream; read it as unmeasured, not as a middle tier. Each ticket's SLA target resolves from your configured SLA policy by issue type where set, and a MetaFrazo default otherwise; a cell's displayed target is the average across its tickets. Use the date filter to focus on specific periods.