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 (100% or more). Each ticket ages from the creation time Jira records for it, against a target resolved from your configured SLA policy by the ticket's current issue type where set, and a MetaFrazo default otherwise; a ticket whose recorded events carry no creation time cannot be aged, so it is counted in its own age-unknown band rather than in one of the four graded ones—the graded bands never guess an age, and the ticket is never dropped from the chart. 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 calls for triage first — many open issues are already past their target.
• 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" means most open issues are well inside their targets.
• A large "age unknown" segment is about evidence coverage, not health: none of those tickets' recorded events carries a creation time, so no age can be computed for them. While that segment is non-empty the other four bands are a floor rather than a full count, and the in-breach figure is the number most likely to be understated.

How this chart works

Segmented bar chart showing the count of open issues in each SLA health state per project: on track, caution, warning, in breach, and a neutral age-unknown segment. An issue counts as open when the latest status MetaFrazo recorded for it is in a to-do or in-progress category; issues whose deletion was recorded, issues whose latest recorded status is done, issues with no recorded status at all, and issues in a project that was moved to the trash or deleted and not restored are left out, and an issue moved between projects is counted once, under its current project. An issue closed or deleted in Jira without MetaFrazo receiving the event is still counted until a later event shows its new status. The bars count the same issues the SLA Breach Probability per Open Issue table lists. The five segments always add up to the project's open-issue count, so the bar height is the whole open population. The rows behind the chart, which Deep Analysis reads, group each project's open issues by current priority, the one the SLA Breach Probability per Open Issue table shows: the latest recorded priority change, else the priority the issue was created with, else, for an open issue whose events record neither, the priority MetaFrazo read from Jira on the day it read it. Issues with none of these group under Unknown, and priority never changes an issue's band. Use the project filter to focus on specific teams.