SLA Calculation Issue

[Makss39]

• Used Zammad version: 4.0
• Used Zammad installation type: (ource DEB
• Operating system: Debian 10
• Browser + version: FF 92.0

Expected behavior:

If SLA is set up, the following fields should be populated:

• first_response_diff_in_min
• first_response_in_min
• close_diff_in_min
• close_in_min

Actual behavior:

Fields stayed empty, “last_contact_agent_at” and “closed_at” are well populated.
*

SLA settings are OK, within the good Groups and Ticket states. Calendar is also OK.

Any tracks ?

Thanks in advance,

Makss

[Makss39]

Here an example, if it can help…

[MrGeneration]

@Makss39

If SLA is set up, the following fields should be populated:

• first_response_diff_in_min
• first_response_in_min
• close_diff_in_min
• close_in_min

Zammad only populates said fields at the moment they’re satisfied.
As an example for close_*:

close_in_min does not mean “You’re supposed to close this in x min” but: “The ticket was closed after X min based on business hours”

close_diff_in_min tells you how your team did behave on overall SLA solving terms.
If you set your solution time to e.g. 60 minutes but your agents took 70 minutes to solve the ticket, the value will be -10. This means that the solution time was not in time (escalation).

Exactly this behavior allows you to tell if a ticket has escalated after.

---

Above completely relies on your business calendars.
Zammad also expects you to use communication type article (phone, email) to address slas.

[Makss39]

Hello,

Yes, totally agree but it’s not working, fields are not populated ! See the example below

Sometime it’s 0, and others time, simply not populated !

Thanks