Using groups to associate to Product Roles is not working as expected

[Mike Haney]

We are using the Default Permissions Scheme for each project. The Default Permissions Scheme has been set up by Role instead of by Group. We are adding users and adding those users to applicable groups that we have created. When we go into any project and in the People section we select View Project Roles, we select the groups we have set up, which contain the people that are applicable to the groups. Then we associate those groups with the roles that have been set up. We are expecting that everyone in those groups will inherit the permissions associated with the particular role associated with the groups. But we have found that the users in the groups are not able to perform the activities associated with those roles and the only way to give them those permissions is to add each user individually instead of in a group. I think we have followed the appropriate JIRA documentation but the system does not appear to be working as expected. Are we missing some configuration or are our expectations wrong? It seems senseless to have the groups associated with the Product Roles if we can't use them and we don't want to have to associate users individually with the roles they need to be in. So I have to suspect that we are not setting up something correctly and we really need some feedback on this issue. Our JIRA implementation is pretty young with not many users but we are creating dozens of user accounts every day now that will now require that we take the users out of their groups and put them in individually until this issue is resolved.

[Harry Chan]

Hi, please check that for your permission scheme, you have assigned the permission required to the roles and NOT the groups.

For each project, in the "people" section where you assign users/groups to roles, ensure that the groups have been mapped to the respective roles.

Cheers,