SLA Breach Probability per Open Issue(3.5.5)

This is the live triage view. Every open issue MetaFrazo has recorded is evaluated against its SLA target and assigned a status: on track, warning, or in breach. This gives you an actionable list of issues that need immediate attention — not a historical chart, but a live exposure snapshot.

An issue that has consumed 207% of its SLA target is well past it. Where your organization has formal SLA commitments, a breach of that size is the kind of event a reviewer may ask you to account for.

What you can conclude

• Issues already in breach are the first candidates for escalation — resolve them, or record the breach with a plan.
• Issues in the warning zone (80–100% of the target used) are the ones to prioritize in the next available work session; they will breach soon if not addressed.
• A list with every issue on track means no open issue is close to its target.

How this chart works

Ranked table showing all open issues with their SLA target, elapsed time, SLA consumption percentage, and status (on track / warning / in breach). An issue counts as open when the latest status MetaFrazo recorded for it is in a to-do or in-progress category: the status in the issue's most recent event that carries one, or its last recorded status change where that event has none. Issues whose deletion was recorded, issues whose latest recorded status is done, and issues with no recorded status at all are not listed, nor are issues in a project that was moved to the trash or deleted and not restored; an issue moved between projects appears once, under its current key and project. An issue closed or deleted in Jira without MetaFrazo receiving the event stays listed until a later event shows its new status. SLA targets follow each issue's current type and resolve from your organization's configured SLA policy where set, and MetaFrazo default targets otherwise (5 days for bugs, 10 for stories, 30 for epics, 7 for anything else); default targets are ours, not a commitment your organization has made. Age runs from the creation time Jira records for the issue, which its events carry, so an issue created before MetaFrazo started recording is aged like any other. An issue whose recorded events carry no creation time has no age, no consumption percentage and no status, and is never shown as on track. The priority column shows each issue's current priority: its latest recorded priority change, else the priority it was created with. When an open issue's events record neither, the column shows the priority MetaFrazo read from Jira for that issue: its priority on the day it was read, which is not necessarily the priority it was created with, and a priority change recorded later replaces it. It is the same priority the SLA Breach Clock groups the issue by, so a reopened issue shows the priority it carries now rather than the one it had when it was closed. Issues read Unknown only when neither their events nor a read from Jira supplied a priority, for example an issue deleted in Jira, and priority never influences the target or the status.