How do you set issue security level on issue/epic

[Clyde Tamburro]

I (very new to Jira) have been tasked with building out a Jira project that involves multiple teams. We want each team to have its own epic, and only be able to see/modify their respective epic.

I have created an issue security scheme, associated it with the project, and modified the project permissions to allow administrators (me) to set issue security levels. Furthermore, I added myself to a couple of the security levels to ensure I would be able to select them.

My issue now is that when I click on any of the epics or issues I created, I don't see "set security level" or the drop-down that is mentioned in several tutorials/answers.

Have I missed a step, or am I looking in the wrong place? Any help would be greatly appreciated.

[Mikael Sandberg · Accepted solution]

Hi @Clyde Tamburro,

Welcome to Atlassian Community!

The issue security is set if you click on the pad lock on the right hand side

If you do not see it, make sure that you have added the field Security Level to the screens that your issue types are using.

[Clyde Tamburro]

Thank you for your answer! I did ensure Security Level was a field in the screen that these issues are using. When editing the issue layout, there was no field for Security Level in the main layout or hidden fields section.

I've attached a screenshot of where I am in the application. Is the red circle where I should see what you linked in your screenshot?

[Mikael Sandberg]

Yes, if the security level field is set you should see the padlock to the left of the watch icon.

Since you don't see it I suspect that Security Level is not set on your issues. You can do a bulk change and set it that way. Also make sure that your security scheme has a default level set.

[Clyde Tamburro]

I cannot thank you enough good sir. I hope you have a great weekend.

[Mikael Sandberg]

You too!

[Mikhail Ponomarev]

I have noted that what you call "Issue security level" padlock is in my Jira (Jira software, next-gen) is called "Restrictions"

\

And I have a problem described here - when Issue is restricted Automation does not work. 

My question is: Why is it called differently? Are we using different Jiras???

[Mikael Sandberg]

@Mikhail Ponomarev since you are using a team-managed project the issue security works differently, and is based on the access roles in the project, not based on an issue security scheme.