We have a little problem with Jira automation rule.
We use automation rule which edit component and alert user when SLA time remaining: Trigger is Breached.
Sometimes that rule stop working and only way to fix it is to reboot our Jira server. This problem appears once a week or sometimes it works just fine several months. All the other rules works just fine.
Any tips why that rule stop working or how we can track main cause?
1. Just first question, your Automation version is latest?
2. Could you set debug log for Automation plugin?
3. Just check ERRors in Debug logs, it will be nice if you provide.
Looks like we speak about different plugins:
I mean about this one.
Could you provide a product key?
I have checked on out the box plugin (com.atlassian.servicedesk.plugins.automation.servicedesk-automation-plugin) with version 2.4.4 for JSD 3.6.1.
Unfortunately, I can not reproduce it.
Could you test on your env with this version?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs