Issue Summary

Moving an issue to another issue type where an Assets Custom Field is marked as required does not prompt the user to input a value for that field.

Steps to Reproduce

1. Create Issue 1
2. Create Issue 2 and set an Assets Custom field to be required
3. During the Move operation, the assets custom field will not be prompted to be set

Expected Results

The move screen would prompt the user to provide a value for the Assets custom field as seen with marking the description as required.

Actual Results

The user can move the issue without setting a value for the Assets Custom field. 

Workaround

Although the field will not be set, any operation on that issue afterwards will prompt the user to input a value for this field. 

Notice: For Jira projects, after any operations, the user will not be prompted to input a value for this field.