G’day Atlassian community!
We’re excited to announce the addition of 2 new permissions to replace the “Browse Projects” permission. This is meant to give Jira administrators more fine-grained control over who can view the projects and issues.
As you may know, the “Browse Projects” permission has dual functionality. It is used to check both
if a user can view projects
and if a user can view the issues within the project.
In other words, it can be used to act at the Project Level e.g. permission to view the projects directory, and at the Issue Level e.g. the ability to view an issue. Since all the other permissions either work at the Issue Level (e.g. "Edit Issues") or at the Project Level (e.g. "Administer Projects"), the current way of working with the “Browse Projects” permission is unique and problematic.
By splitting the “Browse Projects” permission into two, we can give users more fine-grained control over Jira’s permissions. Each of the new permissions can have its own distinct role and that’s what we have done.
“View Projects” is a project-level permission for viewing projects in Jira. It is the permission to view the projects directory page and the ability to select that project in various dropdowns such as in JQL.
“View Issues” is issue-level permission for viewing the issues within a project.
Therefore, “View Issues” can be used to control who can view issues within a project and “View Projects” can be used to control who can view projects in the projects directory.
Since we have introduced these two new permissions that fulfill the same purpose as the “Browse Projects” permission, we are deprecating the “Browse Projects” permission. We will stop supporting it eventually.
Firstly, you will notice some changes to Jira’s permissions scheme page. These are as follows:
The “View Projects” permission will appear under the “Project permissions” category, with a “New” tag.
The “View Issues” permission will appear under the “Issue permissions” category, with a “New” tag.
If a grant is made to “View Issues” permission, the corresponding grant should be added to the“View Projects” permission as well. For eg: If you want the “administrators” group to have access to issues for a project, the grant has to be made to both “View Issues” and “View Projects” permission.
A “Deprecated” tag will be shown next to the “Browse Projects” permission. This means we strongly encourage you to avoid using the “Browse Projects” permission. Instead, use the “View Projects” permission and the “View Issues” permission.
If you were to use the “Browse Projects” permission, internally it would still translate to “View Projects” and “View Issues” permissions, but that support will go away after some time, so please don’t use it!
Getting information on permissions of a project will return information on “Browse Projects” as well as about “View Projects” and “View Issues” permissions. However, since support for “Browse Projects” permission will eventually be withdrawn, it is highly recommended to use “View Projects” and “View Issues”.
We will roll out this change to all of our customers in phases over the next few weeks. Since this change involves a deprecation, we strongly recommend and urge all customers to plan for and adopt the above changes. Meanwhile, we welcome feedback from you.
Here are some screenshots from the Permission Schemes page that indicates the changes mentioned above.
Thank you in advance for working through these changes and for your continued support. Please reach out to us in case of any concern by commenting on this post.