SLA Compliance Rate by Issue Type(2.7.8)

Different issue types carry different expectations. A Bug should be fixed faster than an Epic. A Task has a different delivery rhythm than a Story. This visual compares actual delivery times against type-specific SLA targets, showing you which categories of work are consistently meeting expectations and which are falling short.

An 80% compliance rate for Bugs means 1 in 5 delivered bugs took longer than its target.

What you can conclude

• Issue types staying below 80% are missing target on more than one issue in five, which points at how that type of work is handled rather than at any one issue.
• A type with high compliance but a rising trend of breaches is heading toward a problem — worth catching early.
• All types consistently above 90% means at least nine in ten delivered tickets of every type met their target.

How this chart works

Stacked bar chart showing SLA-met versus SLA-breached counts of delivered tickets per issue type, with compliance percentage annotated above each bar. SLA targets used: Bug = 5 days, Task = 7 days, Story = 10 days, Epic = 30 days. Use the project filter to focus on specific teams.

Only tickets whose closing status counts as delivered under your organization's terminal-status settings enter the compliance numbers (a MetaFrazo default reading of the status name applies until configured); tickets whose terminal status is classified abandoned are reported in a separate abandoned count. Each ending is counted where it happened: an abandonment counts on its abandonment day, and a ticket later delivered counts in the delivered totals on its delivery day. A day whose endings were all abandonment shows no compliance percentage rather than 0 or 100. The same holds for a day on which fewer than five tickets of a type were delivered: the day keeps its delivered, met and breached counts and shows no percentage, because a rate over one to four tickets moves by 25 points or more on a single ticket. The percentages on the panel and on the Overall compliance card are pooled over every delivered ticket in the selected window and are likewise shown only once five or more have been delivered; a type with fewer shows its delivered count instead.