-
Suggestion
-
Resolution: Unresolved
-
None
-
152
-
Issue Summary
JCMA creates duplicate entities with migration, if an entity with same name already exists. But it does not provide a report with all such entities, it will be helpful for customers and partners post migration.
Steps to reproduce
- Create a migration plan from Server to cloud using JCMA and run migration into a site with already existing data.
- Post migration, you will notice that entities like groups, roles, custom fields etc have duplicates with word (migrated) added to them.
Expected Results
JCMA should provide a report of all entities that will be duplicated post migration so that customers know what they have to fix in cloud site.
Actual Results
Most of the already existing entities gets a duplicate entity after migration, like administrator(migrated) etc and customers have to look for all such entities post-migration.
Workaround
Contact Atlassian cloud migration support
- is related to
-
MIG-1163 Better handling of duplicate fields for migrated sites (server to cloud)
- Gathering Interest
- relates to
-
MIG-208 Map with existing entities even if the record is not found while migrating using Jira Cloud Migration Assistant
- In Progress
- causes
-
MOVE-137901 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
The important part of such report is the reason why a configuration element appears on it, so end users will know what actually needs to be fixed (name, description, type, class, etc.)