Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Announcement: Control access to your issues on next-gen using Issue Restrictions

TL;DR

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.

 

What has shipped?

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:

 

How do I use it?

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:

  1. 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.
    Screenshot 2020-07-13 at 10.49.06 AM.png

     

  2. Choose the project role you would like to restrict the issue from the list of the project roles available for the project.
    Screenshot 2020-07-13 at 10.51.18 AM.png
  3. You can also restrict the issue to multiple project roles.
    Screenshot 2020-07-13 at 10.53.03 AM.png

  4. Click Create, and your issue with the configured restrictions will appear in your project.

For existing issues - To restrict or modify the access to an issue in your project that already exists:

  1. 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.
    Screenshot 2020-07-13 at 10.55.11 AM.png

  2. Choose the roles you would like this issue to be restricted to
    Screenshot 2020-07-13 at 10.56.40 AM.png

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

Screenshot 2020-07-13 at 10.57.53 AM.png

 

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:

  1. 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
    Screenshot 2020-07-13 at 10.59.01 AM.png

  2. Click on the lock icon on the top right of the Issue Type screen
    Screenshot 2020-07-13 at 11.07.14 AM.png
  3. Select the project roles for which you would like to grant access permission to the Issue Type and click Apply.
    Screenshot 2020-07-13 at 11.08.25 AM.png


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.

Thank you!

8 comments

This is definitely a great addition to the next-gen projects! Thank you!

I would like to be able to add the "reporter" of the issue to the allowed roles. So that the reporter can view its own issues, but not the total board.

Arjoon Som Atlassian Team Jul 13, 2020

Hi @Martijn van Eijk , unfortunately, restricting the issue to the reporter is not supported in next-gen projects. We only support project roles for the time being but we hope to expand this capability in the future. 

Taranjeet Singh Community Leader Jul 24, 2020

@Arjoon Som Thanks for sharing this useful new feature added for next-gen projects.

This is a great feature. I would love to see that issues get restricted individually based on what role creates an issue. 

Trying to setup an automation where if a team member creates an issue - it's only for "team member role". If a Project viewer creates an issue then there is no restrictions. 

Hi, @Arjoon Som thanks for this!

Is there a known issue re: Set default restriction for issues of an issue type

Here's what I did:

  1. Created a new access role called "Confidential File"
  2. Only granted myself the user role "Confidential File"
  3. I created a new issue type called "Customer PII" and set restriction to "Confidential File" role only
  4. When I create new "Customer PII" issues, everyone in the project can see them.

Did I miss a step? Is there a bug here? It seems it only hides the issue if I manually click it after I create the new issue.

Also... how do restricted issues with story points affect burndown charts?

I noticed that when I manually restricted the issue, I can see 12 story points in the sprint, but everyone else can now see 11.

Does that affect how people see the reports too?

 

Thank you!

Chris

I'm seeing this issue as well when setting the default restriction for an issue type.

Arjoon Som Atlassian Team Jan 07, 2021

Hi Christopher & Jason,

 

Thank you for your comments. The issue restriction default-ing happens only via the issue create modal. If you were to use another method to create an issue, for example, through inline create on your respective board or backlog screen, the default-ing will not happen and you will have to manually assign the restriction post creation of the issue.

Can you please check whether an issue of the type for which a default restriction has been set, when created via the issue create modal, is restricted by default post the creation of the issue?

 

Thank you,

Arjoon Som
PM, Jira Cloud

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you