Restricted Tickets - Automation for Jira as Project Role

[Daniel Wrigley]

I have a use case where all the tickets within a project are restricted to Administrator, Member or Viewer and some tickets have less restrictions to allow external contractors to see and use only the tickets related to their project. This has caused automations to fail as the "Automation for Jira" role is not a member of Administrator, Member or Viewer and cannot be added via the project settings, project access screen .

How can I restrict tickets & allow automation to occur via this role? I'd prefer not to have dependency on a single user in the automation space.

Thanks

[Trudy Claspill · Accepted solution]

Hello @Daniel Wrigley 

Welcome to the Atlassian community.

What type of project does this concern? I think it might be a Team Managed project based on you mentioning the Administrator, Member and Viewer roles.

If so, this is a Bug documented and acknowledged by Atlassian here:

https://jira.atlassian.com/browse/AUTO-401

The work around is to change the rule actor to one that can be already is or can be added to the project roles.

[Yogesh Mude]

@Daniel Wrigley Welcome to the community!

Most of the time all the installed add-ons default user has the default admin rights and they can access all projects and also can do the actions.

Even tho you can check whether "atlassian-addons-admin" user/group have access to the required project with required permission.

Thank you.