/build/static/layout/Breadcrumb_cap_w.png

SLA Violation Mail triggers only once

Hello,

we use the Ticketing System in KACE SMA.

When a Ticket goes over its Due Date it triggers a SLA Violation Mail. Afterwards we work on the Ticket and change the Due Date again. Sadly the second time the Due Date is overstepped it doesnt trigger a SLA Violation mail again.

Is there a Setting we are missing or is this intended? Can this be changed somehow?


Regards



0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: Hobbsy 1 month ago
Red Belt
0

That is probably because the internal rule to alert only happens when the SLA status changes and once the ticket is set to late you cannot set it back.


In truth this is the best practice way to manage SLA's, namely that if you feel the priority is wrong, change it early on and set the enduser expectations. Changing the priority once the SLA has missed, smacks of trying to mess with you reporting figures rather than managing the ticket correctly.


Comments:
  • Ok for now the reporting figures are not that relevant for us since we only use this to send notifications for overdue tickets. Is there any way to reset this SLA missed flag, maybe even via database/custom rule sql script? - lsfweigel 1 month ago
Posted by: lsfweigel 3 weeks ago
White Belt
0

Top Answer

I solved this as well, quick update on how to:

When a Ticket gets over its Due Date it in our case sends a mail and in every case sets its SLA_NOTIFIED Field to the current date. Resetting this Field to its Default Value enables the Ticket to trigger an additional SLA Violation Mail should it overstep the Due Date again. This is how my Custom Rule looks, it triggers on Ticket Save:

SELECT HD_TICKET.ID
FROM HD_TICKET
WHERE HD_TICKET.DUE_DATE > NOW()
AND  HD_TICKET.SLA_NOTIFIED != '0000-00-00 00:00:00'

update HD_TICKET
set HD_TICKET.SLA_NOTIFIED = '0000-00-00 00:00:00'
WHERE (HD_TICKET.ID in (<TICKET_IDS>))

As you can see if a Ticket is Saved and its Due Date is later than the current date and its SLA_NOTIFIED Flag was set, I simply reset the flag to its default value.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ