"Security level not valid for the current issue" error when creating issues in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When attempting to create an issue in Jira, users encounter the error We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields.
When further investigation is performed to identify the root cause as described in Unable to create issues due to unsupported content in Jira Server and Data Center, the Jira application log contains the error Security level with name ... not valid for the current issue.
Environment
Jira Data Center using issue-level security.
Diagnosis
An error similar to the following appears in the Jira application log:
1
2
3
4
2024-01-01 00:00:00,000+0000 http-nio-8080-exec-1 ERROR username 123x456789x0 123abcd 1.2.3.4 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:
com.atlassian.jira.exception.CreateException: Security level with name "My Security Level" not valid for the current issue
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:585)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:486)Cause
This error occurs when attempting to assign a security level to an issue which is not part of the issue security scheme associated with the issue's parent project.
Solution
Check your workflow post-functions to determine where the security level is being assigned, and change it to a security level which is present in the project's issue security scheme.
Was this helpful?