-
Suggestion
-
Resolution: Unresolved
-
None
-
15
-
Post-migration there isn't an easy way to get the new custom fields' IDs and sprint ids in bulk to compare with the IDs in source cloud instance, in case we need to fix any JQL or Workflows.
The C2C migration tool could provide a post-migration report with the mapping of the new IDs of the custom fields and sprint ids and what was the previous value in source instant .
- is cloned from
-
MIG-1323 JCMA to provide a post-migration report with the new/old IDs for custom fields
- Gathering Interest
- is related to
-
CLOUD-11855 JQL filter using project id doesn't update ids after migrating from another Cloud instance
- Closed
- relates to
-
JRACLOUD-83096 Migrating from server to cloud doesn't update the sprint ID in filter JQL
- In Progress
- mentioned in
-
Page Failed to load
Form Name |
---|
[CLOUD-11805] Jira Cloud to cloud tooling to provide a post-migration report with the new/old IDs for custom fields and Sprint ID
Support reference count | Original: 14 | New: 15 |
Remote Link | New: This issue links to "Page (Confluence)" [ 1018591 ] |
Support reference count | Original: 13 | New: 14 |
Support reference count | Original: 12 | New: 13 |
Support reference count | Original: 11 | New: 12 |
Support reference count | Original: 10 | New: 11 |
Support reference count | Original: 9 | New: 10 |
Description |
Original:
Post-migration there isn't an easy way to get the new custom fields' IDs, sprint ids and Team ID in bulk to compare with the IDs in source cloud instance, in case we need to fix any JQL or Workflows.
The C2C migration tool could provide a post-migration report with the mapping of the new IDs of the custom fields sprint ids and Team Ids and what was the previous value in source instant . |
New:
Post-migration there isn't an easy way to get the new custom fields' IDs and sprint ids in bulk to compare with the IDs in source cloud instance, in case we need to fix any JQL or Workflows.
The C2C migration tool could provide a post-migration report with the mapping of the new IDs of the custom fields and sprint ids and what was the previous value in source instant . |
Summary | Original: Jira Cloud to cloud tooling to provide a post-migration report with the new/old IDs for custom fields and Sprint ID/Team ID | New: Jira Cloud to cloud tooling to provide a post-migration report with the new/old IDs for custom fields and Sprint ID |
Description |
Original:
Post-migration there isn't an easy way to get the new custom fields' IDs and sprint ids in bulk to compare with the IDs in source cloud instance, in case we need to fix any JQL or Workflows.
The C2C migration tool could provide a post-migration report with the mapping of the new IDs of the custom fields and sprint ids and what was the previous value in source instant . |
New:
Post-migration there isn't an easy way to get the new custom fields' IDs, sprint ids and Team ID in bulk to compare with the IDs in source cloud instance, in case we need to fix any JQL or Workflows.
The C2C migration tool could provide a post-migration report with the mapping of the new IDs of the custom fields sprint ids and Team Ids and what was the previous value in source instant . |