Issue Summary

As per the issue-level security configuration documentation, when setting the default security level for an issue security scheme, if the issue reporter does not have the 'Set Issue Security' permission, the issue will be set to the default security level. 

This does not seem to be working on Jira version 10.3.12, as it results in the exception below while creating the Jira issue.
Security Level: The selected security level is not available for this issue. Please choose a different security level.

Note:  The issue has been observed since 10.3.12, and the change made between 10.3.11 and 10.3.12 is a fix for JRASERVER-74605.

Steps to Reproduce

1. Create a new project (project A)
2. Create an issue security scheme
3. Add two security levels to it and map it to the project by navigating to Project settings > Issue security  
   1. Security Level 1
   2. Security Level 2
4. Set Level 1 as the Default level.
5. Add a user (User A) to this project, having Browse project and Create issue permissions.
6. Add this user (User A) to Security Level 2, but not to Security Level 1
7. Make sure the “Security level”-System field is mapped to the Create issue screen mapped to the project.
8. Create an issue using User A from project A

Expected Results

The user (User A) should be able to create a new issue from Project A successfully.

Actual Results

Jiar issue creation fails with the following exception:

Security Level: The selected security level is not available for this issue. Please choose a different security level.

Workaround

• Mark the “Security level” system field as a required field to ensure the correct security level is selected during issue creation.
  Navigate to "Project permission" >"Set Issue Security" > Add the required groups/users.  

• If the issue was created using the REST API, include the “Security level” field in the create section of the REST API script.