SLA Breach Rate Trend by Project(3.5.6)

A single week with a high breach rate can be a one-off. Breach rates that rise across several measured weeks are a sustained pattern. This visual tracks weekly breach rates among delivered tickets per project so you can see whether the breach rate is falling, stable, or rising, and see in which week a rise began.

What you can conclude

• An accelerating breach rate (rising week over week) means a growing share of delivered tickets is missing its target. Read the rise across weeks that each carry a measured rate; where the line breaks, the weeks either side of the gap are not consecutive.
• A declining breach rate means a smaller share of delivered tickets missed their target each week; the chart does not show why.
• A stable breach rate, even if elevated, means about the same share of delivered tickets missed its target each week; a reviewer could ask whether the workload or the targets themselves explain the level.
• A break in the line concludes nothing about that week's SLA performance; it says only that nothing, or fewer than five tickets, was delivered to measure. A run of breaks beside a rising abandoned count is a question about how work is being closed, not an answer about breach rate.

How this chart works

Multi-line trend chart showing weekly breach rates per project. Only tickets whose closing status counts as delivered enter the rate, each measured against its resolved SLA policy target (or a MetaFrazo default until one is configured). A week whose closures were all abandoned has no delivered tickets in the denominator: it keeps its place on the time axis but carries no point on any line, and its abandoned count rides in the same row. A week that delivered fewer than five tickets is treated the same way: it is not rated, because one breach among two or three deliveries would swing the rate by 30 to 50 points, and its delivered count rides in the row. The line is not bridged across that gap, because bridging would draw a slope over a week that delivered nothing. A measured 0% is the opposite case and is plotted as a point on the line — tickets were delivered that week and none of them breached — so a point sitting on the zero line is a real reading, while a break in the line is the absence of one. A project whose every week in the window ended only in abandonment or delivered fewer than five tickets has nothing measurable to draw and is left off both the chart and the legend rather than shown as a flat, breach-free line; when no week in the window can be measured at all, the panel says so in place of the chart. Use the project and date filters to compare specific teams or periods.

The week in progress is shown at its value so far. Because the week is not yet complete, it covers only the issues delivered so far and can move in either direction as the week closes.