Issue Summary

When moving a ticket to an issue type that has no security level configured in its issue security scheme and no Security Level field on its screen, the existing security level from the source ticket is silently retained on the moved ticket.

Steps to Reproduce

1. Create or have an existing ticket on Issue Type A with a security level set (e.g. "Internal Only")
2. Ensure Issue Type B has no security scheme attached and no Security Level field on its screen
3. Open the ticket → More → Move
4. Select Issue Type B as the target and complete the move

Expected Results

Jira should either:

• Warn the user that the existing security level cannot be applied to the target issue type and will be removed, or

• Automatically clear the security level during the move, since the target issue type has no applicable configuration

Actual Results

The security level from the source ticket is silently carried over to the moved ticket, resulting in two problems:

1. Broken permissions: The ticket retains a security level that does not match the target issue type's configuration, causing incorrect visibility and access restrictions
2. Uneditable field: Because the Security Level field is not on the target screen, it renders as read-only when it contains a value. The user has no way to edit or clear it through the UI

Workaround

The security level can be cleared via the REST API:
{{PUT /rest/api/3/issue/{issueKey}

{ "fields":

}}}
Alternatively, temporarily adding the Security Level field to the target screen allows the field to be manually cleared through the UI.