| Tip |
|---|
Cloud-to-cloud migration is now available on all Jira Cloud sites For the latest guidance on performing a cloud-to-cloud migration, visit the new support documentation. This EAP documentation will be archived on May 31, 2022. |
| Info |
|---|
Thank you for being a part of the early access program. This community site allows you to provide feedback through page or inline commenting. We will use your comments to improve our product and documentation. Anybody on the internet can view your comments. To know your rights and responsibilities as a customer of our cloud products, read our Atlassian Cloud Terms of Service. |
...
This page lists bugs that are known and are being investigated by the team. We will update this page as bugs are addressed, resolved, or when new bugs are reported.
Projects sometimes fail to migrate due to missing apps on destination site Continue with public access doesn’t resolve errors (MIG- |
606colourYellowFIX in progress performing a migration to a destination site that doesn’t have the same apps installed as the source site. While we work to fix this problem, we recommend installing the same apps on your source and destination sites to reduce the chances of the migration failing.Filter created by a deleted user doesn’t migrate (MIG-612)
| Status |
|---|
| colour | Yellow |
|---|
| title | FIX in progress |
|---|
|
This bug occurs when migrating a project with a filter created by a deleted user. The project will migrate successfully, but the filter fails to migrateproceeding to Continue with public access for a project from the Check for conflicts screen. After confirming, unresolved errors and warnings remain on the Review migration screen. Clicking View errors and warnings will return the user to the public access warning. On the migration dashboard, the progress of this migration will show Some checks failed. |
Incorrect number of issues is shown during project selection (MIG-650) This bug occurs when an issue is added to a project after a migration has been saved. The number of issues in that project doesn't update correctly in the table on |
the project selection screen.Sort projects by name doesn't work correctly (MIG-649)On screen, sorting projects by name in the table doesn’t work correctly.Continue with public access doesn’t resolve errors (MIG-648)This bug occurs when proceeding to Continue with public access for a project from the Check for conflicts . After confirming, unresolved errors and warnings remain on the Review migration screen. Clicking View errors and warnings will return the user to the public access warning. On the migration dashboard, the progress of this migration will show Some checks failed