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 misses its targets at the top of the queue, not across its delivery. This heatmap shows you exactly where the SLA breaches are concentrated.

What you can conclude

• A dark cell at High or Highest priority for a specific project means its most urgent delivered work missed its target most often; a reviewer could ask what held that work up.
• A project where only low-priority issues are breaching is meeting its targets on urgent work while low-priority work waits past them.
• A uniformly light heatmap means low breach rates across every rated project-priority combination.
• The date filter selects which cells are drawn, keeping those whose tickets were active during the period; the breach rate and the average target shown in a cell are computed over all of that cell's tickets, not only the ones inside the period.

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. A cell with fewer than five delivered issues is likewise unrated—the rate is withheld rather than drawn from one or two tickets—and its delivered count is reported instead. The Unknown row groups tickets whose priority never appears in the event stream; read it as unmeasured, not as a middle tier. The priority MetaFrazo reads from Jira for open issues is a current priority, not the priority at delivery, so it is never used here. 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.