This changelog is the source of truth for all changes to the Migration API.
Note that some functionality in the Migration API remains in beta.
You can now use the SCOPED
mode in Advanced Roadmap migrations to migrate AR plans related to selected projects. The minimum supported versions for this feature is JCMA 1.12.8.
You can now add a payload of up to 390 KB for the create migration job endpoint.
You can now use special characters when naming a migration.
You can now connect to your cloud site through APIs instead of going to the CMA UI. The minimum supported versions for this feature are JCMA 1.12.5 (released) and CCMA 3.10.8 (will be released in October 2024). See more details here.
You can now override some failed pre-migration checks in migrate
tasks. The minimum supported versions for this feature are JCMA 1.12.5 and CCMA 3.10.6. See more details here.
You can now download pre- and post-migration reports for check
and migrate
tasks. The minimum supported version for this feature is JCMA 1.12.5; it’s not supported for CCMA. See more details here.
You can now download the error logs for your failed or incomplete migrate
tasks. The minimum supported versions for this feature are JCMA 1.12.2 and CCMA 3.10.5. See more details here.
For the jira-onpremises-to-cloud
flow, we’ve introduced scoped dashboard migrations, which migrate only dashboards linked to selected projects specified in gadgets or dashboard permissions. The minimum supported version for this feature is JCMA 1.11.16. See more details.
In relation to this change, the default migration mode for dashboards is now SCOPED
instead of ALL
.
Progress details are now supported for the confluence-onpremises-to-cloud
flow in the status API (link). The minimum supported version for this feature is CCMA 3.10.6.
We’ve completed the beta phase for the migration API and are now moving it to general availability (GA).
As a part of the GA release, we’re also adding the following features for jira-onpremises-to-cloud
jobs (JCMA >= 1.11.4):
Support for archived issues. They will now be migrated by default. If you wish to skip migrating archived issues, you can use the includeArchivedIssues=false
flag in projects
.
Support for dashboards. Jobs will now migrate all dashboards by default. If you don’t wish to migrate dashboards, you can set the dashboards mode to NONE
.
Support for migrating boards and filters with the following options (read more here link):
ALL
- This includes all filters (both single and cross-project) and cross-project boards, irrespective of their shared access.
SCOPED
- (Default) Only migrate boards and filters shared with selected projects. This includes both single and cross-project boards and filters that have been shared with the projects selected for migration.
NONE
- Doesn’t migrate boards and filters.
Support for progress details in the status API (link).
For more details about the API’s functionality, go to https://developer.atlassian.com/platform/migration-api/.
We’ve completed the Early Access Program (EAP) for the migration API and are now moving it to beta. For more details about the API’s functionality, go to https://developer.atlassian.com/platform/migration-api/.
Rate this page: