Issue Summary

This bug is confirmed to at least affect "Fix Version" but may impact other fields too. There appears to be a difference in behaviour between Jira Server and Jira Cloud with respect to "WAS <x> ON <date>" and issue history. JCMA migrations do not account for "missing" changeitem entries that are expected by Jira cloud.

On Jira Cloud, when an issue has a fix version added during creation, there are additional entries created in changeitem table. These same records are not created for Jira issues in the same circumstance on Jira Data Center.

This does not impact issues where the fix version is added as an edit after issue creation.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a project with a fix version
2. Create some issues and add the fix version on create
3. Create some issues with out fix version
4. Add the fix version to the issues from step 3
5. Migrate the project
6. Create a new issue in the cloud in the same project and add the fix version on create.
7. Review the following JQL query in cloud

Fix Version WAS <version_from_step_1> ON <issue_creation_date_or_later>

Expected Results

All issues created by following the steps above are returned.

Actual Results

Only issues created from steps 3 and 6 are returned.

Workaround

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