Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
Summary
Currently, if some entities already exist in the cloud, JCMA gets a request to recreate the entity and duplicates the entity as (migrated).
It's pretty common for admins to then evaluate and delete the duplicate entities. However, there are some references to these deleted/merged entities that may cause future JCMA migrations to fail.
Suggested Approach
We should have better handling of these scenarios:
1) How duplicate elements are created/managed by JCMA
2) Better manage future JCMA migrations for missing dependencies on these elements
Attachments
Issue Links
- relates to
-
MIG-268 It would be super helpful to easily re-run a (failed or successful) migration.
- Gathering Interest
-
MIG-1163 Better handling of duplicate fields for migrated sites (server to cloud)
- Gathering Interest
- is related to
-
MOVE-98475 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...