...
Known issues | ||||||
|---|---|---|---|---|---|---|
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 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. | ||||||
Projects sometimes fail to migrate due to missing apps on destination site (MIG-606)
This bug occurs when 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)
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 migrate. |
| Status | ||||
|---|---|---|---|---|
|
On the project selection screen, sorting projects by name in the table doesn’t work correctly.