-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
None
-
22
-
Minor
-
17
Issue Summary
When migrating using Jira Cloud Migration Assistant, if there are existing projects using the Default Field Configuration Scheme, custom fields such as Story Points which link to issue type Story will appear to be lost if the incoming projects being migrated also has an issue type Story.
This appears to be because while the incoming issue type will have the (migrated) value appended to the name, the Default Field Configuration Scheme will replace the existing one in Jira Cloud.
Existing projects that used the Story issue type will fail to show data post-migration (such as linked custom fields) because the new Default Field Configuration Scheme that was imported is linked only with the Story (migrated) issue type.
Steps to Reproduce
- Create a Jira Cloud project that utilizes the Default Field Configuration Scheme for an issue type like Story
- Link the issue type to a custom field like Story Points where the value can be visible in the screen
- Create a project on Jira Server that also uses the Default Field Configuration Scheme for an issue type like Story that also links to a custom field Story Points
- Verify both projects have issues that are of type Story and have Story Points values associated with them
- Migrate the Jira Server project using JCMA
Expected Results
Existing projects should show data as it appeared pre-migration before the incoming Jira Server project is migrated
Actual Results
- A new Default Field Configuration Scheme is created with the description:
(Migrated on "Date of Migration") - The new scheme contains a duplicate issue type Story (migrated)
- Existing projects associated with the Default Field Configuration Scheme will inherit this new issue type as the Global Context will be set for all projects
- Existing projects will appear to have missing data
Workaround
In this particular scenario, the user can edit the Default Field Configuration Scheme and add the original issue type Story to the list in addition to the Story (migrated). This will ensure existing projects and imported projects both have references to their exact issue type.
[MIG-581] JCMA will migrate Default Field Configuration Scheme and replace existing one in Jira Cloud
| Workflow | Original: JAC Bug Workflow v3 [ 4095487 ] | New: Mig Bug Workflow v3 [ 4527355 ] |
| Resolution | New: Obsolete [ 11 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Labels | Original: atlas-45432_01 jcma mtun | New: atlas-45432_01 jcma legacy-jcma-bulk-close mtun |
| UIS | Original: 8 | New: 17 |
| Support reference count | Original: 21 | New: 22 |
| UIS | Original: 16 | New: 8 |
| Labels | New: atlas-45432_01 jcma mtun |
| UIS | Original: 8 | New: 16 |
| Support reference count | Original: 20 | New: 21 |
Hi Everyone,
Thank you for previously raising this bug and bringing it to our attention.
With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base.
With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time.
If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue.
We appreciate your understanding and look forward to providing you with an enhanced migration experience.
Thank you again for providing valuable feedback!
The Migrations team