SLA Breach Log(FEED:1.5)
VisualThis tile gives a one-glance read on the rolling 24-hour SLA picture, separating tickets that have already passed their SLA target from those still inside their budget but close to it.
What you can conclude
- A non-zero breach count means that many open tickets passed their SLA target in the last 24 hours.
- At-risk tickets have consumed over 80 percent of their time budget and have not passed their target yet.
- An amber item, such as a Highest-priority bug at 92 percent consumed, has 8 percent of its budget left; a reviewer could ask who owns it and what it is waiting on.
How this chart works
The tile counts breached and at-risk tickets over the trailing 24 hours, where at-risk means more than 80 percent of the SLA budget is already used. A ticket counts as open when the latest status its events record is in Jira's To Do or In Progress category. A ticket deleted in Jira, or in a project moved to the trash or deleted, is not counted, and a ticket whose events record no status at all is left out. A ticket created before MetaFrazo was installed is counted too, and its age starts at the creation time Jira records. A ticket whose events record no creation time at all has no age, so it is never counted as breached or at risk. A ticket moved to another project is counted once, under its current key, and the SLA target of its current project applies.
The tile is measured only for a Jira site whose organization has set SLA targets. Until then it raises no SLA signal of any color, and the feed says the SLA signal is not measured rather than clear, so no ticket is counted against a target nobody at your organization chose. The targets in force are listed under Analysis policies in Settings, where an owner or admin can change them. Once targets are set, a ticket whose issue type has no target of its own has no SLA state: it is never counted as breached or at risk.