SLA Compliance 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. 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.

An 80% compliance rate for Bugs means 1 in 5 bugs is taking longer than it should. Across a quarter, that accumulates into a significant backlog of overdue fixes — and a visible quality problem for users.

What you can conclude

• Issue types with compliance below 80% have a structural delivery problem — the process for handling that type of work needs redesigning.
• A type with high compliance but a rising trend of breaches is heading toward a problem — worth catching early.
• All types consistently above 90% indicates strong SLA discipline across the board.

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.