You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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!
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.
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?