Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Security level field

Евсин Михаил July 29, 2019

Hi. I have Security level field in Edit/View Issue Screen but I can't see it in Issue layout. I have all right on site and project. Help me please.

1 answer

1 accepted

0 votes
Answer accepted
Pavel Junek
Community Champion
July 29, 2019

Hi,

you have to first edit an existing issue where Issue Security Level is not yet filled. Furthermore, it is necessary to make adjustments in the Permission scheme.

Pavel

Евсин Михаил July 30, 2019

I can't see it on Issue layout screen.Issue layout - Jira.jpgConfigure Screen - Jira.jpg

Pavel Junek
Community Champion
July 30, 2019

Hi @Евсин Михаил

This is caused "New Issue View" in Jira Cloud. This new look has too little "features".

Please look to this Atlassian issues: 

Pavel

Евсин Михаил July 30, 2019

Oh, thank you. I'm confused (:

Pavel Junek
Community Champion
July 31, 2019

Your welcome :). The only one solution is to turn on the "Old Issue View" look.

Chris Shaffer
Contributor
April 29, 2020

This answer no longer applies - you can't turn on the "Old Issue View" anymore and Security Level no longer appears as an option for a field in Issues.

Yet, Issue Security still exists as a project menu item and issue levels can be created, even assigned through the walk-through process when creating a new Security Level, however, you can't see this value on the issue, you can't change the value and you can only remove it by deleting the level entirely.

This is clearly a bug.

Like Marie F. Kent likes this
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2020

That's not how it's working for me.  It sounds like you've not got the right permission to change the security level.

Chris Shaffer
Contributor
May 4, 2020

Considering I can go directly into an issue and modify it's Security Level, I don't think that's correct. I was mistaken that I couldn't see it - I didn't realize it was the lock icon.

The real problem is that when an automation runs to change the security level it fails saying the field doesn't exist, which isn't the same as a permissions error. It's also not a field that can be added via the Request Types area where you edit the field layout. I believe this might be why the automation thinks it doesn't exist.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events