-
Suggestion
-
Resolution: Fixed
-
19
-
Boards and Filters
Currently at https://confluence.atlassian.com/cloudkb/how-to-migrate-all-boards-and-filters-with-the-jira-cloud-migration-assistant-jcma-1095774091.html it is mentioned
-->Once all data is migrated, only then enable the two Dark Features -->Create a dummy project in Jira Server with a single Issue -->Run a JCMA migration plan only with that dummy project
But for a customer migrating in multi-phases over many months , it's not feasible to
- Wait for the end of the migration to migrate boards/filters.
- Migrate all boards and filters at the start will bring over so many incomplete or invalid boards/filters which isn't acceptable either.
Similarly for dashboards
Currently at https://confluence.atlassian.com/cloudkb/how-to-migrate-all-dashboards-with-the-jira-cloud-migration-assistant-jcma-1103430546.html it is mentioned
-->DO NOT ENABLE THIS FEATURE FOR EVERY MIGRATION PLAN -->The recommendation is to migrate dashboards as the last part of the migration, using a dummy project to initiate migration
which again doesn't apply to multi-phase migrations. Especially ones panning over months.
Goal:
There should be an option to migrate the associated boards, filters and dashboards per plan and for the scope of projects rather than the whole instance.
- is blocked by
-
MIG-164 Support Migration of Dashboards
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
MOVE-113777 Loading...
-
MOVE-1756762 Loading...
-
ENT-1236 Loading...