Summary

Unable to move issue to another issue type when the source issue type has a subtask (with no Affects Version value) and the target issue type has "Affects Versions" as "Required".

Steps to reproduce:

1. Create Field Configuration with "Affects Versions" hidden.
2. Create another Field Configuration with "Affects Versions" required.
3. Go to Field Configuration Scheme and create a new Field Configuration Scheme.
4. Associate the first field configuration with an issue type and associate another issue type with the next field configuration.
5. Associate the new Field Configuration Scheme with a project.
6. Create an issue with an issue type which has "Affects Versions" hidden.
7. Create sub-tasks for the newly created issue.
8. Move the issue to the another issue type which has the "Affects Versions" required.

Environment

JIRA 6.4.14, JIRA 7.1.9, JIRA 7.2.1

Expected Results

User is able to map specific Versions under "Affects Versions" while moving issue to target issue type which has "Affects Versions" as "Required".

Actual Results

User is not able to move the issue because they are not able to map the "Affects Version".

Workaround

None.