SLA Breach Escalation Alert Log(3.5.10)

This is the compliance audit trail for SLA breaches. Every delivered issue that exceeded its SLA target (resolved from your configured SLA policy by issue type, or a MetaFrazo default) is logged here with its breach multiplier — how many times over the target it took to resolve. A ticket that took 2.8 days when the SLA was 1 day is a 2.8× breach. For regulatory compliance, this log provides the evidence that breaches occurred and documents their severity.

What you can conclude

• Breach multipliers above 3× represent the most serious SLA failures — these warrant formal documentation and root-cause review.
• A pattern of moderate breaches (1.2–2×) across many issues suggests a systemic capacity gap rather than isolated failures.
• A log with no entries in a period means no delivered ticket exceeded its target in that period; check the abandoned counts on the breach rate trend before reading a quiet period as delivery discipline. Tickets whose terminal status is classified abandoned are excluded from this log: stopping work on a ticket is a scope decision, not a late delivery.

How this chart works

Audit table showing all delivered issues that breached their SLA target. Columns: resolution date, issue key, project, priority, SLA target, actual resolution time, breach multiplier, and severity classification (minor, moderate, or critical). The SLA target resolves from your organization's configured SLA policy by issue type where set, and a MetaFrazo default otherwise; the priority column shows the last observed priority change and is blank when the events carry none. Use the project and date filters to scope the audit period.