We are having issues with granting global sprint management rights via an AD-group. The need for that is because some of the board managers dont limit their querys with projects and use labels and a custom field value for the board filter. That means, that if a project is added to the filter, the sprint manager can´t start/close/manage their sprints until they get added to the project role depending on the permission scheme. We tried to solve this by creating a group called "global sprint managers" in our AD and adding it to every permission scheme on our instance with rights to manage sprints and browse projects, but a case came up, where closing the sprint doesn´t work on one of such boards, although the user is in said group.
We are aware, that Jira now checks the rights against the query, not only the issues/projects found by it, but we would greatly appreciate, if anyone could point out some kind of a workaround or any setup changes, that could help us achieve the purpose of the group.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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