Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for Jira in Team Managed project with Issue restriction

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?


1 answer

1 accepted

0 votes
Answer accepted
Curt Holley Community Leader Feb 03, 2022

Hi @Antonio Calì 

Sounds like you pretty much have solved it. You will either have to:

  • remove the permissions from the issues
  • change the actor to one with the right permissions
  • give the current actor the permissions (though I'm uncertain if this is possible)
Curt Holley Community Leader Feb 03, 2022

Note: option 3 can't be done.

"This user is a system user, and their privileges cannot be modified."

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.

Curt Holley Community Leader Feb 07, 2022

I don't get how changing the actor to means "The idea of an automatic action is lost".

If you want to keep the actor not related to a person, 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.


Like Antonio Calì likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events