SLA Breach Clock(3.5.8)

This is the current-state exposure summary. It tells you, right now, how your open issues are distributed across SLA health states: on track, caution (50–80% consumed), warning (80–100%), and in breach (over 100%). Each ticket ages against a target resolved from your configured SLA policy by issue type where set, and a MetaFrazo default otherwise; a ticket whose creation was never observed counts in the total but in no band. It is the aggregate version of the issue-level triage table — useful for leadership briefings and weekly governance reviews.

What you can conclude

• A large "in breach" segment requires immediate triage — many commitments have already been missed.
• A large "warning" segment is the most actionable signal — these issues will breach imminently if not addressed today.
• A distribution heavily weighted toward "on track" indicates healthy SLA management across the portfolio.

How this chart works

Segmented bar chart showing the count of open issues in each SLA health state per project: on track, caution, warning, and in breach. Rows group by the last observed priority change, with tickets whose priority never appears in the event stream under Unknown. Use the project filter to focus on specific teams.