Group members are not able to view project

[sourabharvikar3]

Hi,

I am new to the JIRA cloud and I don't have an idea about it as I am application developer and don't have admin experience much.,

I have created the project then a group to allow the access related to a particular project.

e.g.

project name: qlbp

user group: qlbp_grp

then create project role named as qlbp_prj_role

Also, a new permission scheme is created, named as qlbp permission.

Then in QLBP project, I have added qlbp_grp with qlbp permission.

Still, users from qlbp_grp are not able to see the QLBP project.

Also verified with permission checker, a user from the group has the project browse permission.

Please help me out, I am stuck here.

[Anup]

I don't think you need this for this purpose since you're already using Group. i.e project role named as qlbp_prj_role

In the qlbp permission, is the browse project permission given to the group and project role both?

[sourabharvikar3]

yup , the browse project permission given to the group and project role both. but still project is not accessible to the user. 

And yes, according to the permission checker the given user has the permission to browse the project.

[sourabharvikar3]

Also, I have observed that if I allow JIRA application access then user able to see the projects.

But allowing jira application access gives full power to the another user to do whatever with my projects.

What I am trying to achieve is:

• Create a project e.g. ABC
• Create the group ABC_group

Now only users from ABC_group able to see ABC project and manage that project only, other project say XYZ will not be accessible to ABC_group members.

[sourabharvikar3]

I have searched a lot documentation and youtube videos but no luck 

[Nic Brough -Adaptavist-]

Yeah, videos vary between mostly useless and plain wrong for instructing Atlassian admins.

All you need to do is read the permission scheme and match the rules for users correctly.

Look at the permissions for ABC and XYZ.  Make sure that ABC_group matches the permission for Browse project in ABC, and does NOT in XYZ. Also for XYZ, you need to ensure there are not other access rules that let the users in in other ways (eg, if it allows group XYZ_group, and Dave is in both ABC_group and XYZ_group, then he'll be able to see both projects)

If you've gone with the default scheme and the best recommendation (use roles, always use roles), then your scheme is very likely to say "Browse project: Role (users)".  You need to make sure only ABC_group is in the role of users in ABC, and only XYZ_group is in the role of users in XYZ