Understanding how project permissions affect project visibility in Jira Cloud

Still need help?

The Atlassian Community is here for you.

Ask the community

For Atlassian eyes only

This article is Work In Progress and cannot be shared with customers.


Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.


Summary

There are several areas of a Jira Cloud site in which you can see projects mentioned by name. This article describes how their visibility is determined by project permissions.

Company-managed projects

To see a project in the Projects > View all projects list, a user must have the "Browse Projects" project permission *or* be a site admin. Note there is a bug that means you can be a site admin and still not see all projects on that page JRACLOUD-82231 - Getting issue details... STATUS

To see a project in the Project dropdown in the Create issue modal (i.e. the popup that appears when you click the Create button), you need to have the "Create issue" project permission. Therefore it sounds like the behaviour is indeed different to what you experience in Server, and you may therefore wish to update the  "Create issue" project permission so that it is granted to fewer people.

Note for company-managed

If you are using either of the following in your project permissions, you may be affected by the bug JRACLOUD-75053 - Getting issue details... STATUS :

  • User custom field value
  • Group custom field value

Team-managed projects

It's not possible to hide a team-managed project from the Projects > View all projects list.

To see a project in the Create issue modal you need a role with the "Create issue" permission:







Last modified on Oct 27, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.