Permission scheme failing when user is in group but not project role

[Kathy Barton]

Jira server v7.3.5

I am using a permission scheme with a group that has manage sprints permission. There's also a project role defined for this permission for "atlassian-addons-project-access" that was created automatically by something. My problem is, the people in the group that has that permission still can't actually manage sprints. I found a bunch of bugs around this that say they are resolved in previous versions. 
https://jira.atlassian.com/browse/JRASERVER-45968

https://jira.atlassian.com/browse/JRASERVER-45210

I have about 20 projects like this so manually adding individual people to that role in each of them is not an option. Does anyone know the workaround for this? 

[Andy Heinzer · Accepted solution]

That group name is not native to Jira Server.  However it can occur in Jira Cloud instances.  If you migrated your Jira Cloud into a Jira Server instance, I can see how that group name might have been transferred during this migration.

This document explains why this group exists in Jira Cloud: https://confluence.atlassian.com/servicedeskcloud/blog/2017/02/add-on-permissions-update

But given the error you are seeing, it appears that the project role requirements are still not being met.

I suspect that your project roles only list the 'atlassian-addons-project-access' group for some project role that is indirectly granting access to this in the permission scheme.  What I am thinking is that you would need to add that 'Operational Analytics Admins' group to the same project role where that 'atlassian-addons-project-access' group exists for that project.  That is one way I believe will resolve this.

[Kathy Barton]

Thanks! I wasn't sure where that role came from but now that I know it's from our cloud migration, I know I can delete it, I have a path forward.