Members of a project are not able to access the project

[Nandita Parthasarathy]

Hi Folks! 

I created a new company managed project and added a few people to it, they have been added as developer and they were not able to access. 

So I added them as an overseer too, now they have two roles, a developer and an overseer  and they are still not able to access the project. 

They get the below error message. 

[Tansu Akdeniz · Accepted solution]

Hi @Nandita Parthasarathy 

Please go to Project -> Project Settings -> Permissions and check which users/groups/roles are granted to Browse project permission.

[Nandita Parthasarathy]

Hi @Tansu Akdeniz ,

Thank you for the prompt response. I can see that that these are only two roles added to the browse projects permission. 

• Project Role (atlassian-addons-project-access)
• Project Role (Administrators)

I am not a JIRA admin, is there some document which shows us how do we add the right kind of permissions so that the members of this project would be able to access the project? 

[Tansu Akdeniz]

Well, it totally depends on your requirements. But basically, you can use Administrators and Users roles. Use Administrators role for more critical/powerful actions such as Delete Issue, Delete Comments etc and leave Users role for basic operations (create, assign, assignable, transition, edit etc).

Please observe Default Permission Scheme (Settings -> Issues -> Permissions).

You can also add more roles to Jira such as Developers, Testers, Managers..

Some useful links:

• https://community.atlassian.com/t5/Jira-Software-articles/Jimmy-s-Jira-Permissions-Tips-amp-Best-Practices/ba-p/1922363
• What are project roles?
• https://www.tempo.io/blog/2015/jira-best-practices-jira-permissions
• https://support.atlassian.com/jira-cloud-administration/docs/manage-project-roles/
• https://confluence.atlassian.com/jirakb/permissions-made-simple-for-jira-server-717062767.html

[GNarsimhagowda - Empyra]

Hi @Nandita Parthasarathy ,

Please ensure that the individuals assigned as developers have the appropriate permissions to access the project. If the issue persists, consider adding any of these individuals as a single user with specific "Browse Project" permissions. If this resolves the problem, it may indicate an issue with the roles that have been assigned.

Thanks.