Cannot add atlassian-addons-admin to a board filter share

[Jean-Charles Trottier]

When trying to automate the assignment to the current sprint of a board through the automation of a project, i'm getting this error :

Unable to access the selected board. Please ensure that the rule actor has permission to access that board.

The Actor of the automation is Automation for Jira but I cannot add the role atlassia-addons-admin to the board.

I'm gessing the reason behind that is that my current user does not belong to that role but I cannot add myself to the role group either.

Could you help me find a solution?

[Azrain]

Hi,

I recently switched from team-managed to company-managed, and several of my automation rules broke. I received this error notice as a result of one of the automation rules "Unable to access the selected board. Please ensure that the rule actor has permission to access that board.". FYI, I have all of my rules set Actor with the user Automation For Jira.

I double-checked my Permission Scheme and adjusted the "Manage sprints" permission to "Project Role (atlassian-addons-project-access)" but the problem persists.

I'm using a custom filter for my board, and the problem persists even after I added the Administrators role. It worked perfectly if I added for All Roles. That's the strange thing.

Hope that anyone have solution for this because I don't want to use my user account as Actor.

Thanks.

[Chris Buzon]

I think that could be a few things - first check the share permissions on that board query to make sure it's not private, but I think you may need to refer to the permissions scheme for the project(s) that the tickets on that board reside in.  The Automation actor will need to have permissions to make the expected changes to all the tickets on the board (therefore all the projects involved), so you may need to do some digging to see what is missing for each project. 

Try using the permissions helper to narrow down the problem (press "." while in jira to access the helper, then just search for permissions)

You can set the automation to use your account as the actor, but it will appear as though you made all the changes, and that can be confusing too

Just a note, permissions are a bit confusing - and the answer isn't always obvious.
Hope that helps.

[Jean-Charles Trottier]

Hi Chris, thank you for your help. For the permissions on the board query, if I change it to "all project role", the automation works just fine. The issue comes when i'm trying to set the permissions on the board query for a specified project role.

What i'm thinking is that I need to add the project role "atlassian-addon-admin" to the query permission but I am not able to see that project role in the selection since my user does not belong to that project role. When i'm trying to add my user to that role under project/people, i can't.

That project role do show up under permission to the project and has already all the permissions. (which is why the automation works when i'm setting the permission on the board query to "all project role")

Using the permissions helper does not help since the user automation for jira does not show up in the search query.

For now, I can make it work using my account as the actor but like you said, it is a bit confusing.

For my understanding, I need either to find in which golbal group "Automation for Jira" belong in order to add it to the board query permissions, or I need to find a way to add my user to the project role "atlassian-addon-admin" in order to add it to the board query permissions.