# Amount of escalated tickets

**URL:** https://community.zammad.org/t/amount-of-escalated-tickets/20178
**Category:** Technical assistance
**Created:** [May 6, 2026, 10:51am UTC](https://community.zammad.org/t/amount-of-escalated-tickets/20178 "2026-05-06T10:51:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![AlexSmith](https://community.zammad.org/letter_avatar_proxy/v4/letter/a/77aa72/32.png) [@AlexSmith](https://community.zammad.org/u/AlexSmith)
#### Post date: [May 6, 2026, 10:51am UTC](https://community.zammad.org/t/amount-of-escalated-tickets/20178/1 "2026-05-06T10:51:19Z")

</div>

### Infos:

- Used Zammad version: 6.1.0
- Used Zammad installation type: (source, package, docker-compose, …)
- Operating system: MacOS Ventura Version 13.2.1
- Browser + version: Chrome Version 147.0.7727.117 (Official Build) (arm64)

I’ve been trying to gather information on escalated tickets, but I haven’t found a way to get the results I need. My objective is to determine, out of all closed tickets, how many were escalated and therefore breached the established SLAs.

### Current approach:

I first attempted to create a tag that would be applied whenever a ticket escalates. However, since all tickets are created with a predefined future escalation time, the tag was automatically applied to every incoming ticket, making it unusable for tracking actual escalations.

Next, I tried setting up a scheduler to apply a tag when the escalation time is updated. Unfortunately, every time a ticket is closed, the escalation time appears as updated, which again causes incorrect tagging.

### Goal:

I am looking for a reliable way to tag tickets that have truly escalated so that I can build an overview or report. Specifically, I want to identify how many tickets breached the SLAs and were escalated versus those that were resolved before escalation.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [May 6, 2026, 10:58am UTC](https://community.zammad.org/t/amount-of-escalated-tickets/20178/2 "2026-05-06T10:58:42Z")

</div>

> [@AlexSmith](#):
>
> Used Zammad version: 6.1.0

You are **extremely** outdated. The current stable version is 7.0.1 - last security fixed version is 6.5.5 if you have to check the AI changes first. You should upgrade asap to keep your installation safe!

–

To your question.  
What exactly speaks against Grafana Reporting where this kind of metric is already tracked?

> **[Reporting Tools (Third party) — Zammad System Documentation documentation](https://docs.zammad.org/en/latest/appendix/reporting-tools-thirdparty.html)**

We also had this [topic](https://community.zammad.org/t/sla-breach-not-preserved-after-ticket-is-closed/20117) within the last 14 days, basically going into the same direction.

---

<div class="post-metadata">

### Author: ![AlexSmith](https://community.zammad.org/letter_avatar_proxy/v4/letter/a/77aa72/32.png) [@AlexSmith](https://community.zammad.org/u/AlexSmith)
#### Post date: [May 19, 2026, 12:47pm UTC](https://community.zammad.org/t/amount-of-escalated-tickets/20178/3 "2026-05-19T12:47:05Z")

</div>

Thank you for the information.

I will request the software update for a newest version according to your specifications and advice.

We are currently not using Grafana and rely only on data from Zammad reports exported to another internal tool. I have reviewed the topic you linked and will try the suggested approach of using a trigger to add the internal note #{ticket.close\_diff\_in\_min}.

Is there a way to track how many tickets this note has been applied to? We are not specifically interested in the amount of time by which the SLA was exceeded, but rather in whether the SLA was breached at all.