Issue security scheme challenges

[Linus Chui]

Hi Jira Community,

I need some help with the setting up a security scheme on my project.

The main goal is to restrict a set of users to only be able to see and comment on certain issue types on a given project. All other users (except the aforementioned set) can do anything on any issue type on the project.

I've done some research and pretty much gave up and decided to use a security scheme in combination with the security level field. Essentially forcing users to define the security level for each issue and using that to control access. 

For this solution, I am struggling to set this up properly... I've followed the steps defined in this guide (https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/) but I'm unable to see or set the security level.

1. I have confirmed that "Security Level" is on all relevant screen schemes but I can't add the "Security Level" field when I edit my issue layout. I can drag it in but when I hit save, it disappears from the issue layout (this seems to only apply for the edit/view layout - I am seeing a dropdown for the creation layout)
2. When I see the "Security Level" on the creation screen - it is showing as a dropdown for me but there are no options to select despite having a security scheme on the project

I've been struggling with this on and off for the last two weeks but I've given up on more tinkering in Jira.

Appreciate all the help that I can get with either a solution to my main goal or the problems I raised above. 

Thanks in advance for all the help!

[John Funk]

Hi Linus - Welcome to the Atlassian Community!

Issue security only applies to whether the user can see the issue or not. Then you would control what they can do within the issue based on the Permission Scheme. But you won't be able to control what they can do by issue type out of the box. There are some add-on apps like ScriptRunner Behaviours that can give you potentially more of the field level security. 

[Linus Chui]

Hi John,

I'm ok with the out of the box behavior as you have suggested (i.e. manually defining whether a user can see a given issue). Can you provide some guidance on what I may have done wrong given the behavior I described above?

Thanks,

Linus

[John Funk]

There is a entry in the Permission Scheme that needs to be granted the permission to set the issue security. You are probably missing that permission. 

[Linus Chui]

Yes that was a pain and I figured out my other silly mistake. I assumed that the user groups for the security levels had me within them but it seems like that wasn't the case. After adding myself in, I am now able to at least see the selection finally.