Automation: Keeping on top of SLA's not triggering

Emmanuelle Guia

We have the SLA espera informacion cliente (waiting for client information), a rule that creates a comment when the sla is about to breach, and a rule that triggers when is breached that comments and closes the isue.

According with this article JSM Jira Automation: How to Send SLA Breached Noti... - Atlassian Community, my implementation is ok, but I found out that if the notification rule is processed, the other rule does not work in the same issue. 

There are no errors in the logs. And both rules allow another rule to trigger them. Someone else had this problem?

Kateryna_v_SaaSJet_

Hi @Emmanuelle Guia 
I once saw a similar request in the community, but unfortunately, I can't find it now. I didn't have such a problem because we use the SLA Time and Report for Jira add-on (which we developed), where in one window, you can configure the conditions for SLA execution and immediately SLA goals with automatic actions. Below is an example of how it looks in the add-on.

You can also configure the automation rules described in the request: comment on the task, status change, and others. The app has a 30-day trial, so give it a try.