JCMA set "updated" field to migration date

Issue Summary

For a server-to-cloud migration, it is seen that some issues have their updated field set to migration date.

This is reproducible on Data Center: (no)

Steps to Reproduce

1. Perform a server to cloud Jira migraiton
2. Some issues have their updated field set to the migration date
   This can affect AR plan exclusion rules

Expected Results

An issue should be created/updated with the updated field set to the original updated field value from server

Actual Results

The updated is reset with the date of migration.

Workaround

No workaround exists at this moment.