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
1) type of project: Team Managed
2) Restrictions are applied to issues (for example Administrator and member)
the Actor “Automation for Jira” can’t perform rules properly (no action performed), results aren't found in Audit Log section using for example JQL conditions in the rule.
I think the issue is related to Actor's permissions, since without issues restrictions all is working properly.
How can I solve the problem?
Sounds like you pretty much have solved it. You will either have to:
Hi @Curt Holley I appreciate your time, but the assumption in my Use Case obviously can't be changed!
If I use a normal user with administrator privileges I had already verified that it works, but it is not the same. The idea of an automatic action is lost.
I thought that somewhere I could give the privileges to Automation for jira, but I learn from your answer that unfortunately there is no way.
I don't get how changing the actor to say...you means "The idea of an automatic action is lost".
If you want to keep the actor not related to a person, say....you. Then create a new service account that you can control and add to the relevant groups etc to empower it to run any such restricted issue type automation rules.
Call it "Admin automation for Jira" or "Admin Actor".
Bottomline, it can be done, you just need the right actor.