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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is caused "New Issue View" in Jira Cloud. This new look has too little "features".
Please look to this Atlassian issues:
Pavel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your welcome :). The only one solution is to turn on the "Old Issue View" look.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's not how it's working for me. It sounds like you've not got the right permission to change the security level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.