Recently a bunch of atlassian addon projects showed up in our Issue Assignee list - unfortunately at the top of the list.
I found the atlassian-addons-project-access role in the permissions for Assignable User. Can I just remove it, or will that (potentially) break something?
Take a look at Add-on permissions update:
When you install or update an add-on, JIRA will automatically grant the add-on the correct permissions for its scope through the atlassian-addons-project-access role. It will also check the permissions of existing add-ons across all JIRA and JIRA Service Desk projects, and grant them the correct permissions as well.
How does the atlassian-addons-project-access role use project permissions?
When you install an add-on, JIRA 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 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.
Hopefully that clears things up a bit.
I understand why it's doing that, I'm just wondering what the repurcussions are if I undo a bit of it. Unless Jira App for Chat can fix bugs for me, I don't see why we would ever assign any issues to it, but maybe that's needed behind the scenes for some other reason. Is it going to break anything if I remove that one permission?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs