"Security Level is required." error for new tickets but security levels are not used on project

Rebecca C
Contributor
December 16, 2022

I am getting an error when creating a new issue about the security level but I don't have security level set on this project. In looking at our JSM instance we actually are not using security levels on any of our projects so I don't know why I'm getting this error.

I have a different issue type in the same project and it is not getting this error when I create a new ticket. I have checked my create issue screen and it does not have the security level field assigned to the screen.

I can't figure out where this error is coming from. I can move old issues through the workflow but I can't create new issues.

3 answers

1 vote
Vincent T_ August 1, 2024

I solved the Problem:

Field Configuration - New Field Configuration

Edit Field Field Configuration - Security Level 

Change Security Level from required to optional

Project Settings - Field - Actions - "Use different scheme" - select your field configuration

 

A better/more secure way should be to use security levels like intended.

0 votes
Nicolas Grossi
Banned
August 1, 2024

Check the filed configuration associated.

0 votes
Vincent T_ August 1, 2024

Hello,

 

ich have the same problem for a company-managed project. Sadly this problem is "solved" without an answer.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events