Permissions vs people - company managed project

Melanie Leclerc

Once you add users to a group and assign the group to a project role in a permission scheme, and then assign the permission scheme to a project, the users are supposed to have access to the project. Right ?

 

In my instance, on top of the above, I need to add the group/project role into the people section of the project settings in order for the users to get access to the project. That is not supposed to happen.

 

Anyone have a clue why this problem might happen ? thanks

Miguel Ramon

Hello @Melanie Leclerc!

From what I understand, you don't need roles for what you're trying to achieve.

Project Roles (documentation) are meant to enable granular access configuration on a project per project basis. That is to say that you could grant a given role certain permissions in a permission scheme, and then use that same permission scheme in several projects, but the roles will allow you to say who, in the end, will actually have the permission, by assigning that role to someone in a given project.

For example, if Project A and Project B have the same permission scheme with the Browse Projects permission granted to the role "Users", but your user only has the "User" role in Project A, then you'll only be able to view issues in that project.

Have you tried adding the group directly into the permission scheme instead of assigning a role? Say that the group is called jira-users. Go to the permission scheme, click on Grant Permission, click Group, and search for the group in question. Then, verify that permission scheme is assigned to the Project you're looking to grant access to.