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
Does anyone have any idea why one of my automation rules has started to fail (audit log says "Some errors")? It has been used for over two years without any problem.
The problem started this morning and I haven't done any configurations in a while.
I went through the audit log and chose one story (without an epic), that triggered the rule last week without action and without any problem, and changed it's status to "Open" and then to "In progress" and this time the rule failed. Why? :)
I agree with other posters this symptom may be related to the epic field changes. The earliest posts about those changes indicated Atlassian was going to auto-magically update rules in customers sites. However I wonder if there is some problem in the the over-loading of the parent field for epics in the context of automation rules.
So a couple possible suggestions (in addition to letting Atlassian Support know about this):
@Bill Sheboy Thanks for your suggestions - I will start with number two I think :). It's about 8 am here in Sweden and I got the first notification mail while writing this.
So grateful for this community as I'm the only admin in our instance and have difficulties finding time to catch up with all features/changing coming up
The issue is a bug (SKL-12263) and it doesn't belong to an Epic.
The thing is that the rule has worked fine for two years, without any changes from my side (and I'm the only admin), until this morning.
The rule has handled (triggered) all issue types with or without an epic link.
The only reason I can see now is that something has change within Atlassian.
If you try, your trigger story has a different parent issue type or else this automation will occur even if there is no parent issue.
In your case ,i think the automation has failed because there is no parent(Epic) issue.
let me know if you have any questions.