-
Suggestion
-
Resolution: Unresolved
-
None
-
388
-
Problem Definition
When sites are migrated over from Server to Cloud, some fields are copied over as duplicate entities with (migrated) attached to the field name.
This is expected behavior when projects are migrated in separate plans or migrated from two server instances and the entities already exist in the cloud.
- field names are changed, with '(migrated)' appended
- field descriptions are changed, with '(Migrated on <datetime>)' appended
Suggested Approach
We should have better handling of these scenarios:
1) How duplicate elements are created/managed by JCMA
2) Better management of entities for migrated sites by JCMA
- is related to
-
MIG-163 Better handling of deleted objects with Jira Cloud Migration Assistant
- Closed
- relates to
-
MIG-1084 JCMA should provide report on entities that will be duplicated with migration
- Gathering Interest
-
MIG-2124 Tool to handle duplicated entities post migration
- Gathering Interest
-
MOVE-136820 You do not have permission to view this issue
-
ENT-677 Failed to load
- resolves
-
JRACLOUD-83395 Performing PbP Migration to Cloud results in duplicate Custom Fields
- Closed
- is addressed by
-
ENT-2311 Loading...
- is blocked by
-
MOVE-1745274 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...
Better handling of duplicate fields for migrated sites (server to cloud)
-
Suggestion
-
Resolution: Unresolved
-
None
-
388
-
Problem Definition
When sites are migrated over from Server to Cloud, some fields are copied over as duplicate entities with (migrated) attached to the field name.
This is expected behavior when projects are migrated in separate plans or migrated from two server instances and the entities already exist in the cloud.
- field names are changed, with '(migrated)' appended
- field descriptions are changed, with '(Migrated on <datetime>)' appended
Suggested Approach
We should have better handling of these scenarios:
1) How duplicate elements are created/managed by JCMA
2) Better management of entities for migrated sites by JCMA
- is related to
-
MIG-163 Better handling of deleted objects with Jira Cloud Migration Assistant
- Closed
- relates to
-
MIG-1084 JCMA should provide report on entities that will be duplicated with migration
- Gathering Interest
-
MIG-2124 Tool to handle duplicated entities post migration
- Gathering Interest
-
MOVE-136820 Loading...
-
ENT-677 Loading...
- resolves
-
JRACLOUD-83395 Performing PbP Migration to Cloud results in duplicate Custom Fields
- Closed
- is addressed by
-
ENT-2311 Loading...
- is blocked by
-
MOVE-1745274 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...