You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Project admins can now set up and control access to individual issues or set a default restriction to issues of an issue type for a next-gen project.
Until now, the ability to restrict access to an issue was available only on classic Jira projects. Using the issue security feature, admins or users with appropriate permissions can ensure selective viewing rights to issues that should be visible to certain users only and not to every user in a project. Learn more about issue restrictions on classic projects
We are excited to announce that admins or users with appropriate permissions of next-gen projects can now restrict an issue or issues of an issue type to a role or a set of roles for a next-gen project.
Please note, to set issue restrictions for issues in a next-gen project:
You must either be on the Jira Standard or Premium license plans.
You are assigned to a role that has the SET_ISSUE_SECURITY permission. Admins and users assigned to the Member role are given this permission by default. Learn more on how to grant permissions to roles in next-gen.
Customers can choose to restrict issues for the next-gen projects in several ways:
A. Restrict issues individually
For new issues - To restrict access to a system-defined role or a custom role while creating an issue:
Click on the ‘Restrict Issue’ dropdown in the Create issue modal. If the ‘Restrict Issue’ field is not visible to you, please ensure that the conditions specified above are met and that the restrict user field is configured for this screen.
For existing issues - To restrict or modify the access to an issue in your project that already exists:
Open the issue in the issue viewer and click on the lock icon on the top right corner. If the lock icon is not visible to you, please check if the conditions specified above are met.
You can also add or change the restrictions of existing issues from the issue viewer available from the sprint view as well by clicking on the lock icon in the top right corner of the issue
B. Set default restriction for issues of an issue type
If you would like to set up a default restriction for all issues of a certain issue type in a project, you should:
Open ‘Issue Types’ in the project settings of the next-gen project and select the Issue Type for which you would like to configure restrictions for
Please note that changes to the default restrictions of an Issue Type will only apply to new issues that are created. For already existing issues of that Issue Type, you will have to individually change the issue restrictions accordingly.
We hope this feature will give admins of next-gen projects more flexibility and control of their projects. Please do leave your feedback and thoughts in the comment section below. We’d love to hear from you.
Senior Product Manager