-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
None
-
16
-
Minor
-
7
Issue Summary
When trying to progress with the migration after having selected the destination cloud and source server site on the "Choose your destination cloud site" screen, if the groups are not reviewed in the destination cloud site, the "Confirm" button will not move forward with the request.
Steps to Reproduce
- Perform a site import on the destination cloud site;
- Do not approve the default groups for "Product access";
- Use the JCMA to perform an import to the same cloud site;
Expected Results
The JCMA will display an error message/warning that the groups should be reviewed on the cloud site.
Actual Results
Nothing will happen.
Workaround
Review the groups on the "Product access" page in the UM.
Notes
It's possible to see the following response for a 400 status code:
{
"code": 3013,
"message": "The default group is missing or unapproved. Please check your cloud site and try again."
}
[MIG-450] JCMA - Clicking on the button "Confirm" on the "Choose your destination cloud site" screen when the groups are not reviewed in the destination cloud site will not proceed with the migration
I've encountered this issue today on a migration. However, it is not dependent on reviewing groups via the Complete Your Migration banner but only dependent on a default group being set.
For context, after the initial data migration portion and before finishing approving those groups, I swapped over to a different org admin and removed the user that initiated the migration. I then tried to Reject all of the items on the group review in the banner but the Reject button just wouldn't do anything (although red and not grayed out) so I hit the Approve button which worked. All items from the banner were resolved and it went away and the migration was "completed" after the group review. I then tried to initiate the migration and ran into this.
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