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,461,809
Community Members
 
Community Events
176
Community Groups

Security level field not showing in issues or bugs

Edited

We're following this setup process for implementing new security levels for 1 project in Jira Cloud - https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

We can't seem to get the security level field to actually show on the issue or the bug. Here's what we've done so far:

  • We have the field telling us it should show on the screen (not hidden) after checking the "Find your field" method through the issue and the bug and checking the screen setup/issue layout section of the project
  • We've added users to the security levels so we know those users should be able to view those issues and change the security levels

Are we missing something else to check?

Our goal: Have a certain subset of users be able to change security levels on certain stories so only they would be able to view it. We have some stories that would need to be confidential for 1 team, but we still want visibility across teams and other users on issues they're working on that AREN'T confidential. 

2 answers

1 accepted

1 vote
Answer accepted
Mikael Sandberg Community Leader Dec 05, 2022

Have you also updated your permission scheme so that you can set the issue security? If you do not see the pad lock up in the right-hand corner and the field is on the screen then that is what I would check.

I got it! We did the entire checklist mentioned above and the last step was making sure our default software scheme was also updated to reflect the right role. We had the scheme for the project tied to this default and needed to update that. 

I got to permissions scheme by going to Issues --> (scroll the left-hand menu all the way down) Permission schemes --> Edit permissions

Note: We have permissions set to admins right now just so we could test it out, but we will change this to the right group of users now that we know how to get it to show up on the issue and bugs :) 

Screenshot 2022-12-07 143841.png

Screenshot 2022-12-07 144226.png

Thank you, Mikael!

Like Mikael Sandberg likes this
2 votes

Welcome to the Atlassian Community!

Security level is a bit of an odd one.  To get it on a screen, you have to jump through more hoops than other fields.  Some of this is going to be blindingly obvious, and you've already covered it, but I prefer to put the complete list into an answer so that other readers don't miss things!

  • Is it on the create/edit screen you want it on in the screen setup?
  • is it hidden in the field configuration?
  • Have you defined and associated a security scheme with the project?
  • Does the user have the permission to set a security level in the project?
  • Is the current user set up so that they belong to at least one security level in the scheme?  (Note one real oddity here - if you make the field mandatory and the user does not belong to any level other than "none", they won't see the field!)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events