Bulk Move within the same project doesn't allow update of Component/s, Affects Version/s and Fix Version/s

Issue Summary

A project is created with multiple issue types. For one issue type, the Component/s, Affects Version/s and Fix Version/s fields are not required. For another issue type, these System Fields are required. If you create an issue of the first type where the System Fields values are not required, and then use the bulk operation to move it to the second issue type (staying within the same project), the following behavior is seen:

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a Project with SCRUM sample data, this will contain multiple Issue types
2. Let's pick the following Issue types with the following rules:
   • Story, System fields Component/s, Affects Version/s and Fix Version/s are not be required
   • Bug, System fields Component/s, Affects Version/s and Fix Version/s are required

For this:

1. Create a Field Configuration (FC) and Field Configuration Scheme(FCS) to make the System fields Component/s, Affects Version/s and Fix Version/s required for the Issue Type Bug.
2. Let the Default FC for the rest of Issue Types (i.e.: Story, Task, Subtask) where the System fields Component/s, Affects Version/s and Fix Version/s are not required.
3. Edit the new FCS and Associate the Issue Type Bug with the new FC where the system fields are required and let the default FC for all the unmapped Issue Types (i.e.: Story, Task, Subtask)
4. Go to the Project settings, on the Fields section go to Actions > use a different scheme and select the new CFS. Here you will see again the new CF and the Default CF as follows:
   
5. Create Two Issues of type Story without Component/s, Affects Version/s and Fix Version/s.
   • Make sure these System Custom Fields are present in your project screens.
6. Try to move the previous two Issues you created from Story to Bug. You won’t be able to move it, as you can not select a new Component, Fix Version nor Affects Version:
   

Expected Results

You should be able to select a new Component, Fix Version nor Affects Version and move the Issues.

Actual Results

The Retain checkbox is ticked and grayed out, so it means the bulk actions will retain current values. Since the System fields Component/s, Affects Version/s and Fix Version/s are required for Issue Type Bug, it won't be possible to move:

Findings:

• If you create a Story Issue Type without subtasks and you move it to Bug, it will use the method secure/MoveIssue.jspa and will let you choose values for the System Fields.
• If you create a Story Issue Type with subtasks, it will use the method secure/views/bulkedit/BulkMigrateSetFields!default.jspa and it will not let you choose the value for the system fields because the Retain is checked and greyed out.
• If you create two different stories without subtask, but you select both Issues and move them in bulk to Bug, it will also use the method secure/views/bulkedit/BulkMigrateSetFields!default.jspa and it will not let you choose the value for the system fields because the Retain is checked and greyed out.

Workaround

Set a value for the System fields Component/s, Affects Version/s and Fix Version/s before moving the Issues.