SLA threshold breached - Not triggering

[Kyle Cooke]

I'm wanting clarification on the trigger "SLA threshold breached"

I have 250 tickets that have breached their SLA, however on enabling this trigger to run my automation, it did not run against them. 

Does this trigger run retrospectively or for only newly created tickets after the rule was created?

Also, does this run for all tickets, all just portal ones?

[Dirk Ronsmans · Accepted solution]

Hi @Kyle Cooke ,

The trigger for automation will not go retroactively. When the SLA is breached, at that point in time the trigger will be well..triggered. (and that's also how you would want it to not get ancient tickets to trigger something).

If you need to do some kind of historical cleanup you could look in to a scheduled or manual trigger and run a JQL against that of the breached SLA.

As to the scope of the tickets, this will be for all tickets, not just portal ones. As long as they have an SLA that is for them it will trigger.

[Fabian Lim]

Hi @Kyle Cooke

Here you can find an article on how you can send sla breach notifications: https://community.atlassian.com/t5/Jira-Service-Management-articles/JSM-Jira-Automation-How-to-Send-SLA-Breached-Notifications/ba-p/1894625

Regards

[Kyle Cooke]

Thank you for the rapid response, very much appreciated.