Install an add-on before 8 July? This post is for you!
Recently, we made it easier to install add-ons by automatically granting them the correct permissions for their scopes. Today we start releasing a quick permissions fix for add-ons that you installed before this change. The fix checks to see if the project can grant add-ons the correct permissions, then fixes any problems it finds.
If you installed an add-on before 8 July, your project might display a permissions error that looks something like this:
We recommend that you click Fix permissions and let JIRA Service Desk repair the problems. Alternatively, you can fix the permissions yourself by going to > Administration > Issues > Permission schemes.
FAQ
What’s a scope?
You can learn more about add-on scopes in the Atlassian Connect documentation.
What's the atlassian-addons-project-access role?
atlassian-addons-project-access is a project role that grants permissions to add-ons.
How does the atlassian-addons-project-access role use project permissions?
When you install an add-on, JIRA Service Desk creates a corresponding ‘user’ who is assigned to the atlassian-addons-project-access role in each project. If you don’t want the add-on to have access to a project, you can remove it from the role. Additionally, JIRA Service Desk always respects add-on scopes over permissions. This means that add-ons only have access to the APIs defined by their scopes, and only have permission to perform the actions defined by their scopes.
I installed an add-on before 8 July, but I don't see this warning
Stay tuned! We're rolling out this fix incrementally, so it might be a few weeks before it displays in your project.