Create a single automation rule for *ALL* SLAs

[Mariano]

Greetings everyone!

I'm pretty sure this is a no-no, but just asking to make sure I'm not missing anything due to my n00b status:

I have created an automation rule based on a library item called "Send notification when SLA is about to breach".

However I think I misinterpreted it. I though any and all SLAs were included but turns out you need to pick one from the list:

Is there a way to do one rule for them all?

I don't think it's convenient to have several rules for all of the SLAs, and what about if I create new ones? I will be forced to remember to automate that new SLA again.

I know, not a big deal, but also not ideal.

Thanks for any help, and wishing you a nice week!

[Daniel Ebers · Accepted solution]

That's a valid suggestion from my point of view.
If you want you could give feedback to Atlassian to get probably a "Suggestion" opened on jira.atlassian.com on that - you could do that by opening a formal support request and linking to the discussion here.
There is apparently also the chance to open one by yourself but I guess double checking by support would not do any harm.

[Mariano]

Thank you @Daniel Ebers ! I will do that then. 
One thing worth mentioning is that I have seen many tickets open (and suggestions and feature requests) That are extremely essential to the functioning of a service management team, and yet they haven’t been replied to for years :-/

do you think this will eventually get to the point where at least we get a reprioritisation of all the requests or open suggestions?

[Jack Brickey]

Correct, there is no “any sla” option.

[Mariano]

Oh, that is kinda bummer. At least a way you could choose which SLAs you want included in the notification. :'-(