Restrict users to see only assigned or reported issues in Jira Data Center
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When users are granted permission to browse a project, this includes all issues in that project.
If instead, you want them to browse only the issues they are assigned to or they reported, we can Configure issue-level security.
By following the proposed solution, the below will be implemented:
- If user Mary is assigned to an Issue, she'll be able to see it because she'll be the 'Current Assignee'
- If user Mary belongs to the Project Role "Developers" then she will also be able to see it
- If she meets neither condition, she will not see the issue
Configure an issue-level security scheme for your project(s)
- Create an issue security scheme and name it "Assignee and Developers Security Scheme"
- Refer to Configuring issue-level security for full details
- Inside the security scheme, create a security level named: "Assignee and Developers"
- Add "Current Assignee" to that Security Level
- Add Project Role "Developers" to the Security Level
- Set it to "Default"
Assign the security scheme to any projects where you wish to use it
The Project Role "Developers" was used as a generic example. Other project roles will help you use the same Generic Security and Permissions schemes on multiple projects.
You can define different groups into Roles for different projects and still use the same Scheme we just created. Please see Managing project roles for more information.
A Security Level was assigned to the project to restrict access only to Assignees and Developers to the issues on that project. Watchers must be in the Developers' group to have access.
If you have a Watchers Group or Role, also add it to the Security Level. Remember that by using Roles you can use the same Security Scheme for other projects too.
Alternative Solution: Grant browse project to Assignee and/or Reporter
It is possible to set the Browse Project permission to be to Assignee or Reporter
However, due to the below bugs this will make the project (though not any issues inside of it) visible to all users.