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

[Girish Jagdale]

Please let me know if my understanding is correct:

Prom project setting, user has been added with a role of Scrum Master. He/she shouldn't be able to do sprint related tasks if -

The role of Scrum Master is not listed in the 'Manage Sprint' permission of the project permission scheme.

That is the reason probably we add someone as administrator to make him manage sprint, as that role exist in all permissions by default.

So (if above assumption is right) it would have been better if Scrum Master role was default role in permission scheme (which gets created by default on project creation) so adding person as scrum master role would have been more appropriate.

[Alexey Matveev · Accepted solution]

Hello,

What do you mean by "default role"? All roles are available for a project. If you created a scrum master role, then you will be able to set a value for this role in any project.

If you want to create such a role with the manage sprint permissions, you can do it. It all depends on your requirements.

[Girish Jagdale]

Ok forget about default roles and all which wasn't my original question.

A simple question is: How to provide access of manage sprint to someone?

Also suggest if this can be done from multiple ways. If there is any dependency on Project Dashboard or so?

I was testing with a user which neither have any role assigned in project nor a part of any group that is mentioned against Mange Sprint Permission scheme and still able to create sprint.

[Alexey Matveev]

You provide access to the Manage sprints permission by opening the project permission scheme and granting  a user (directly or via a group or a role) the Manage sprints permission.

You mentioned that a certain user does not have this permission but still can create a sprint. Could you open a project, from which the issues are selected for the board, go to the Project Settings -> Permissions. You will see there the Permission Helper button. Push it and choose the Manage Sprints permission, provide the user and an issue and you will see, if this permission is granted or not.

[Girish Jagdale]

Thanks Alexey for reminding me about permission helper that not only solved my queries but also revealed potential risk of using group 'Anyone' that was there in default permission scheme which would allow anyone to perform all operations on project/issues.

conclusion for my original question is: Even if we add user as Scrum Master in project roles, we still need to give him permission from the projects permission scheme to enable the required permissions.