Missing required permissions for Rule Actor with automations

[Brian Harkness]

We already were using Automation for Jira prior to it becoming a feature in Jira cloud. I've started to find previously working automations that are now failing due to permissions.


I'm an admin and have the required permissions so I'm assuming the rule actor "Automation app user" is lacking the permissions. Previously I believe "atlassian-addons-project-access" was used to give Automation for Jira permissions and this does exist in the permission schemes for the referenced projects. I don't see anything that ties to "Automation app user" but tried adding the group "atlassian-addons-admin" and adding "Jira Software" as type Application access with no luck. Any suggestions?

[Ken Siskind]

We stumbled across the same error message.  We had an automation where 1 project was creating an issue in a JSM project. 

It turned out the user who was creating the automation didn't have permissions in the JSM project.  Once they were added to the JSM project the issue was resolved. 

[Rinaldi James Michael]

I have the same issue now. And the actor has permissions to all projects.

Edit: Just found the issue. One of the projects that was listed in the Rule details was archived. I don't think this makes any sense since Jira should automatically detect which projects are active and at least show that in the rule's audit logs.

[John Funk]

Hi Brian - I have found that the atlassian-addons-project-access works well. Make sure that user is in the create issues and browse project permissions. Also check the create transition in the workflow. 

[Brian Harkness]

The user does have those permissions
Looking at the the transition for Create issues, I don't see anything but the Create Issues permission

[John Funk]

That baffles me. I would open a support ticket with Atlassian. 

https://support.atlassian.com/contact/#/

Then please post back here the resolution. 

[Brian Harkness]

Adding Automation for Jira as a user, resolved the issue. I don't see how to do this as a user but Atlassian Support was able to do it.

[John Funk]

Hey Brian - that doesn't seem right at all. I don't have a user for Automation for Jira and things work fine. Did they give you any further explanation as to why they had to add that as a user? That then probably counts against your licenses and shouldn't. 

[Brian Harkness]

Looking at my User list I don't see it but when I go into permission schemes it is available under Single User. Not sure if it was there before or was added then applied to our particular permission scheme. No other details except that it was added to the permission scheme for the affected projects.

[John Funk]

what does the name look like?

[Brian Harkness]

[John Funk]

Really weird. 

[Leon Kupper]

Hi together,

I have the same issue. my automation is not working because of some permissions issue. The actor is "Automation for Jira" But I don't find any possibility to change his permissions. Actually I don't see him as well if I look at project users.

Any clue what I can do?

[John Funk]

Hey Leon - you should open a new question and not post on existing questions as only a limited number of people will see them. 

[Mona aljebreen]

Hi,

Make sure the project you're creating a ticket in it already exists.

[Florian]

Hi. We also have a dedicated user for our automation scripts. This user is granted every right in all our permission schemes. And also in all issue security schemes. The automation user actually as more rights then I have as system admin. For example I am not allowed to delete issues but automation user is allowed. 
With this setting I don’t have to but the automation user in a project role. The automation user (and only the automation user) is always allowed to do everything. 

[Marc Isikoff]

We have the same and it has Service Desk Team which has ASSIGN_ISSUES but Automations suddenly today (worked in the AM, then tweaked one thing and red warnings on everything saying me or the operation does not have ASSIGN_ISSUES yet we do.