As far as I understand, every installed Atlassian Connect application (add-ons) is granted a special role "atlassian-addons-project-access". Through this role, project permissions can be configured, enabling a set for authorized actions for all installed add-ons. What we'd like to find out is whether this configuration could be more specific about what add-ons can access what projects.
Let's imagine we have two Jira projects P1 and P2, and let's say we want to use 2 add-ons A and B, that both have authorization scope allowing them to edit issues.
Can I limit the the access for add-on A only to issues of project P1, while I still need the add-on B to access both projects P1 and P2?
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events