Issue Summary

When performing a migration with the JCMA from server to cloud, the context of the custom field Story Points on the cloud instance gets modified by the JCMA.

Steps to Reproduce

1. On the cloud instance set the Story Points field to have Global context
2. On the server instance, set the Story Points context to be applicable to only some issue types
3. Create some issues on a test project and migrate them to cloud

Current Results

The JCMA creates a separate context for the migrated issue types that belong to the server custom field context without warning that this will hide field data on issues that previously had this field viewable on Cloud.

Desired Results

As part of the migration process, a warning or confirmation appears notifying the user that the contexts between server and cloud do not match, and that this may result in data being hidden or fields being unusable until the contexts are adjusted.

Migrated context can be renamed as "migrated_<context_name>"