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
Have any Site Admin or Org Admin users changed the permissions for that user?
Have any Project Admin users changed access for the project, removing / altering permissions?
As far as I can tell, "Automation for Jira" is a default rule actor.
I don't think it would be affected by anything done to regular user permission schemes. I can't see it in the list of Users to check what group its in. You don't need to assign it any permissions in a project. But it has stopped being authenticated in some of our automation.
Would you please post images of your complete automation rule and of the audit log details showing the rule execution that failed? Those may provide some context as it is possible that error is not focusing on the actual cause.
Please review the workflow for that issue type and look for any rules on the transition to Done which restrict which users can do so.
I suspect there is a restriction on your workflow to limit which users can move the issue to Done. And, I do not believe the Automation for Jira user can be added to that transition rule. (Or at least I was unable to do so when I just tried it.)
Hmm...That was my last idea of what could cause this...
As you are the site admin for a paid license (Jira Premium) I suggest next submitting a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/
They may notice something we are missing in the rule / site configuration. When you hear back from them, please post what you learn to benefit the community.
Answer from Atlassian - they revalidated that my permissions and automation rule were properly configured, so they suspected it was an index problem.
The re-Index of permissions related to the "atlassian-addons-project-access" project role is done on a daily basis automatically, however, there are scenarios where they are not executed properly and can cause an updated permission to be corrupted or outdated.
There are an undefined number of reasons this may happen in Jira, however, this problem usually happens because of double-entries in the project roles's database table, caused by a failed import or even project role creation. In those scenarios, we must enforce the re-index from our side.
After re-indexing, the automation worked.