Change History Migration fails if some dependencies fails via JCMA

Issue Summary

JCMA will try to migrate change history items from Server to Cloud via groups of items. If one of the items in the group is not supported via JCMA (e.g. multi version picker), the rest of the change history items in that group will not make it to cloud.

Steps to Reproduce

These steps are hard to replicate and depend on the order in which change group items are attempted to be migrated to Cloud:

1. Create an unsupported change history item in Server (e.g. unsupported custom field change)
2. Migrate to Cloud
3. If the supported change history items is in a group with an unsupported item, all items will not make it through

In this example, there's 6 items in the import group, if one of them is not supported (e.g. custom field), none of the change history items will make it over for that issue.

Expected Results

Only the unsupported items in the change history are not migrated to cloud

Actual Results

Any other change history items in that batch will not make it through to Cloud

Workaround

None Available so far