Issue Summary

Currently, JCMA silently drops issue history entries (change items) authored by third-party apps when those entries do not have a corresponding record in the customfield table.

In the source Data Center database, these rows exist in the changeitem table with fieldtype = 'custom' and a string label in the field column. However, because the app wrote these entries without registering a standard Jira custom field, JCMA’s CloudChangeItemConverter cannot resolve the string in the field column to a valid Jira object. As a result, these history rows are excluded from the migration payload.

Steps to Reproduce

1. In a Jira Data Center source database, identify or insert a changeitem row where fieldtype = 'custom' and field = 'Add Test Cases'.

1. Ensure there is no record in the customfield table where cfname = 'Add Test Cases'.

1. Perform a migration of the affected project using JCMA.

1. Check the issue history in Jira Cloud.

Expected Results

JCMA should provide a mechanism to migrate these history entries (perhaps via a name-based fallback to a placeholder field) even if the metadata is missing from the source customfield table.

Actual Results

The history entries are silently discarded during the export phase because they cannot be mapped to a registered field. The migration completes with SUCCESS, but the data is missing in Cloud.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.