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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,857
Community Members
 
Community Events
176
Community Groups

Jira Cloud limit view of certain issue types to certain groups

Is there a way to limit certain issue types in a Jira project to certain user groups?

I have 20+ issue types in a Jira project and wish to separate viewing between user groups. For example, 5 issue types to be seen only by 1 user group, 12 issue types to be seen by three user groups.

Is this possible? If yes, how do I set this up?

2 answers

1 accepted

0 votes
Answer accepted
Mikael Sandberg Community Leader Mar 17, 2022

Yes, it is possible. You would need multiple security schemes and then you can use automation to set the issue security based on the issue type when an issue is created.

@Mikael Sandberg Hello, thanks for your time and reply. I already have several security schemes, but they limit only seeing issues per project. I wish to limit viewing the issues by certain issue types inside one Jira project, is this possible? And how do I achieve this if yes? 

Mikael Sandberg Community Leader Mar 17, 2022

You have to set the issue security on each issue you want to limit. Having multiple security schemes only defines who should be able to do something when an issue is assigned to that scheme. So for example if you want to limit who can see Bugs, the security level also has to be set. You can either do that by manually setting it when the issue is created, or use Automation to do it. 

For example in our HR project the default security level is general, but if there is a question for HR that only our People team should see, I have an automation that will change the security level to People which limits who can view that issue.

0 votes
Dirk Ronsmans Community Leader Mar 17, 2022

Like @Mikael Sandberg mentions you can use issue level security to limit what someone sees after the issue is created.

blocking who can see an issue type to create however is not possible.
if you have permissions in the project to create, you can view all issuetypes at creation.

At best you could add conditions/validators at the creation transition to block the creation itself.

Hi @Dirk Ronsmans thanks, but my question is not to limit the users from seeing the list of available issue types during creation.

After the issue is created I wish to limit its viewability to certain groups.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events