Bulk Move - New security level field values are shown from originating project, not the target project

When moving issues from a project to other, the Update Fields view that allows setting values for issues uses the values from the originating project in the Security Level field. AFAIK the field should show values in the target project.

To reproduce:

1. Create projects SOURCE and TARGET
2. Create an Issue Security Scheme with at least one level
3. Associate the scheme with TARGET
4. Create issue in SOURCE
5. Bulk Move the issue to TARGET
6. In the Update Fields view, notice the pulldown selection for the Security Level only lists "None" even though TARGET has other valid field values

Workaround:

Before moving the issues, associate the security level scheme with the SOURCE project.

Possible fix would be that in the first screen for bulk moving issues, if the TARGET and SOURCE projects do not have same Issue Level Security scheme associated, warn users that they should first associate the same scheme to the projects or they will lose the field settings. Ideally of course the field should allow selecting the Security Level without this additional step.