-
Suggestion
-
Resolution: Unresolved
-
None
-
65
-
-
Jira Software, Jira Service Management
Issue Summary
During the C2C migration process, certain entities are duplicated and labelled with "(migrated)" appended to their names. This behaviour is intentional and aligns with the logic outlined in the document provided below.
Post-migration site administrators have to manually clean up these duplicate entities after the migration, which can be quite time-consuming and tedious.
Suggested Solution
- Enhance the entity mapping process to minimize the occurrence of duplicate entities during the migration.
- An option should be provided to the admin, allowing them to assess the entity mapping and decide whether they want to create new fields or link them with existing ones. This feature will significantly benefit admins after migration, enabling them to make informed decisions based on a risk assessment, ultimately saving time and effort.
- is related to
-
CLOUD-11436 Cloud-to-cloud migration - don't create a new custom field with the suffix migrated when a custom field already exists
- In Progress
-
JRACLOUD-82762 C2C migration of a single project creates duplicated custom fields with (migrated) in their name
- In Progress
- relates to
-
JRACLOUD-93358 Duplication of Teams upon C2C migration of Advanced Roadmap Plans
- Closed
-
CLOUD-12225 Custom fields and other entities should not be duplicated when I selectively copy projects into a sandbox
- Gathering Interest