How to Restrict New Users from Seeing All Project Names in Jira?

Fabienne_4vfrlk

Limiting Project Visibility for New Users in Jira

Dear Jira Community Management,

We are facing an issue with project visibility in our Jira instance. We have multiple existing projects, and whenever we grant new external users access to Jira, they are able to see the names of all projects, even though they cannot view the details. They can only access the specific issues to which they have been assigned or given permissions (via issue access).

Is there a way to configure our existing structure in Jira so that new users only see the project to which they have access, and hide the titles of the remaining projects entirely? If I remove for those users the permission "Brows Projects" they won't be able to see their tickets at all..

Thank you in advance for your assistance!

Best regards, Fabienne 

Walter Buggenhout

Hi @Fabienne and welcome to the Community!

A couple of things might be at play here. Since you refer to the browse project permission and issue access, I think I may assume you are using company managed projects.

The most likely cause I suspect, based on your description, is a known bug that Atlassian has indicated they are not planning to fix, although a new feature suggestion was raised afterwards for the same. If you grant access to people through a permission scheme by means of a user custom field, this does expose the names of all projects in your instance:

• JRACLOUD-37117 is the bug that was closed back in 2018;
• JRACLOUD-75053 is the related suggestion that is currently still open.

Since Atlassian designs its out-of-the-box permission schemes with openness by default, projects using a template permission scheme may also list "any logged in user" linked to the browse project permission. Any projects with permissions configured like that will be visible to all licensed users in your instance. I do not suspect that this will be the case for you, but it does happen. If it does, it might help to review all your permission schemes with a similar setup and replace any logged in user with permission roles representing your internal and external users respectively.

If you are looking to only make a subset of issues in a single project visible to external users, you might want to grant browse project permission by role (as described in the previous paragraph) and add issue level security (See this support article for more details) to separate internal / external users within a single project.

Hope this helps!