Version 1.5.3 adds support for the early access program (EAP) for app migrations. If you are interested in joining the app migrations EAP, check out the blog for more details.
Version 1.5.3 also improves how the Activated Date field in sprints is migrated from Jira versions older than 8.7.1.
This version also fixes the following bugs:
Version 1.5.3 adds support for the early access program (EAP) for app migrations. If you are interested in joining the app migrations EAP, check out the blog for more details.
Version 1.5.3 also improves how the Activated Date field in sprints is migrated from Jira versions older than 8.7.1.
This version also fixes the following bugs:
Version 1.5.2 includes improvements to error logging and a fix for the bug (MIG-558) that prevents table columns from sorting correctly.
Version 1.5.2 includes improvements to error logging and a fix for the bug (MIG-558) that prevents table columns from sorting correctly.
Version 1.5.1 adds support for the Users in Group condition in workflow migrations. You can find the complete list of supported workflow rules here.
Version 1.5.1 adds support for the Users in Group condition in workflow migrations. You can find the complete list of supported workflow rules here.
Version 1.5.0 includes a minor bug fix that improves performance and increases reliability. This release also fixes the bug (MIG-520) related to user migration failure.
Version 1.5.0 includes a minor bug fix that improves performance and increases reliability. This release also fixes the bug (MIG-520) related to user migration failure.
Version 1.4.9 fixes the bug (MIG-177) related to migrating boards and projects with the following:
This release also includes a minor bug fix that improves performance and increases reliability.
Version 1.4.9 fixes the bug (MIG-512) related to Jira core only server support.
Version 1.4.9 fixes the bug (MIG-177) related to migrating boards and projects with the following:
This release also includes a minor bug fix that improves performance and increases reliability.
Version 1.4.9 fixes the bug (MIG-512) related to Jira core only server support.
We’ve made it simpler to configure your migration options and track your progress with the new tasklist format. Through tasks, you can systematically make selections for Projects, Users and groups. The same screen also shows a summary of your selections before you proceed to check for errors.
Version 1.4.7 also fixes the bug (MIG-277) related to issues migrated with sprint history entries.Update (on 20 Jan 2021): There is a small UI bug that appears in this release where the wrong text is displayed when you first land on the "Choose your migration options" page. This is resolved once you select projects to migrate.
We’ve made it simpler to configure your migration options and track your progress with the new tasklist format. Through tasks, you can systematically make selections for Projects, Users and groups. The same screen also shows a summary of your selections before you proceed to check for errors.
Version 1.4.7 also fixes the bug (MIG-277) related to issues migrated with sprint history entries. Update (on 20 Jan 2021): There is a small UI bug that appears in this release where the wrong text is displayed when you first land on the "Choose your migration options" page. This is resolved once you select projects to migrate.
Version 1.4.6 increases the workflow rules migration capabilities from 8 types of workflow rules to a total of 32. This significant increase includes rules ranging from conditions, validators, and post-functions. You can get the complete list of supporting workflow rules and how to handle invalid rules here.This release also fixes bugs (MIG-281) related to custom field changes not getting recorded in the issue history after migration. The fixes are specific to sprint, single select, and epic link custom field.
Version 1.4.6 increases the workflow rules migration capabilities from 8 types of workflow rules to a total of 32. This significant increase includes rules ranging from conditions, validators, and post-functions. You can get the complete list of supporting workflow rules and how to handle invalid rules here.This release also fixes bugs (MIG-281) related to custom field changes not getting recorded in the issue history after migration. The fixes are specific to sprint, single select, and epic link custom field.
The ‘Review your migration’ screen allows you to view your migration data in a new structured format. It starts with highlighting whether the pre-migration checks were successful or not (includes errors and warnings). This is followed by a summary of the current migration configuration. You can then switch tabs to view details about what is included (users and groups / projects) in your migration or to download the pre-migration report, post migration report, and error logs.
This release also adds ‘Configuration items' to the pre-migration report. It lists all the custom fields and workflows that are part of the migration.
The ‘Review your migration’ screen allows you to view your migration data in a new structured format. It starts with highlighting whether the pre-migration checks were successful or not (includes errors and warnings). This is followed by a summary of the current migration configuration. You can then switch tabs to view details about what is included (users and groups / projects) in your migration or to download the pre-migration report, post migration report, and error logs.
This release also adds ‘Configuration items' to the pre-migration report. It lists all the custom fields and workflows that are part of the migration.
The new post migration report gives more details about the data migrated to your cloud site. The report includes the following:
Once you run the migration, you can download the post migration report (.zip file) from the ‘Review your migration’ screen.This release also adds summary data in the pre-migration report showing a list of entities that are expected to migrate and not migrate.Version 1.4.3 also fixes the following:
The new post migration report gives more details about the data migrated to your cloud site. The report includes the following:
Once you run the migration, you can download the post migration report (.zip file) from the ‘Review your migration’ screen.This release also adds summary data in the pre-migration report showing a list of entities that are expected to migrate and not migrate.Version 1.4.3 also fixes the following:
The new pre-migration report will help you analyze to-be-migrated data, including problems and list practical alternatives for a smooth migration process.The report includes the following:
You can download the pre-migration report (.zip file) from the ‘Review your migration’ screen.
Version 1.4.2 fixes the bug (MIG-271) related to failure of duplicate email check validation under the ‘Check for errors' screen.
The new pre-migration report will help you analyze to-be-migrated data, including problems and list practical alternatives for a smooth migration process.The report includes the following:
You can download the pre-migration report (.zip file) from the ‘Review your migration’ screen.
Version 1.4.2 fixes the bug (MIG-271) related to failure of duplicate email check validation under the ‘Check for errors' screen.
Version 1.4.1 incorporates the following changes:
Bug fix:
This version also fixes the bug related to migrating issues with fractional time estimates.
Version 1.4.1 incorporates the following changes:
Bug fix:
This version also fixes the bug related to migrating issues with fractional time estimates.
This new security check under ‘Projects’ in the ‘Check for errors’ screen will notify if projects, boards, or filters are prone to anonymous access post migration. Anonymous access means that the data will be available to the public and searchable online. You can choose whether or not to grant public access before the migration.
To review affected projects, boards, and filters, you can download the .csv file.
This new security check under ‘Projects’ in the ‘Check for errors’ screen will notify if projects, boards, or filters are prone to anonymous access post migration. Anonymous access means that the data will be available to the public and searchable online. You can choose whether or not to grant public access before the migration.
To review affected projects, boards, and filters, you can download the .csv file.
Version 1.3.6 (MIG-141) offers more control and flexibility for migrating users and groups. With previous versions only migrating all users and groups, this release enables you to migrate users and groups relevant to selected projects. Such as users and groups referenced in configuration, fields, and content of the project.
To get a consolidated list of users and groups that are ready for migration, you'll be able to download .csv file.
Version 1.3.6 (MIG-141) offers more control and flexibility for migrating users and groups. With previous versions only migrating all users and groups, this release enables you to migrate users and groups relevant to selected projects. Such as users and groups referenced in configuration, fields, and content of the project.
To get a consolidated list of users and groups that are ready for migration, you'll be able to download .csv file.Learn more about migrating users and groups with the Migration Assistant.
Version 1.3.5 fixes the bug (MIG-231) related to attachment failures during migration. This release also fixes some minor issues.
Version 1.3.5 fixes the bug (MIG-231) related to attachment failures during migration. This release also fixes some minor issues.
Version 1.3.4 supports the migration of archived projects ('Choose projects you’d like to migrate' screen) from your on-premise instance to cloud.
Version 1.3.4 fixes the following:
Version 1.3.4 supports the migration of archived projects ('Choose projects you’d like to migrate' screen) from your on-premise instance to cloud.
Version 1.3.4 fixes the following:
Version 1.3.3 fixes a bug (MIG-216) where project roles were not being migrated.
Version 1.3.3 fixes a bug (MIG-216) where project roles were not being migrated.
Version 1.3.1 fixes the bug related to the error message: "Unable to resolve media file ID for attachment". During an ongoing migration, if attachments are added to the exporting projects real time, the migration will no longer fail.
Also, some HTTP conflicts (status code 409) are fixed in this release.
Version 1.3.1 fixes the bug related to the error message: "Unable to resolve media file ID for attachment". During an ongoing migration, if attachments are added to the exporting projects real time, the migration will no longer fail.
Also, some HTTP conflicts (status code 409) are fixed in this release.
App assessment steps you through the assessment process to streamline your decision-making process. Assessing your apps before testing and running your migration helps reduce the potential for delays when you are ready to migrate.
You can review the apps currently being used, see which apps are available in cloud, and decide which apps to migrate using one simple tool.
With the v1.3.0 release you can now:
App assessment helps you to identify what differences there are between server and cloud versions
Learn more about using app assessment from the user documentation here.
App assessment steps you through the assessment process to streamline your decision-making process. Assessing your apps before testing and running your migration helps reduce the potential for delays when you are ready to migrate.
You can review the apps currently being used, see which apps are available in cloud, and decide which apps to migrate using one simple tool.
With the v1.3.0 release you can now:
App assessment helps you to identify what differences there are between server and cloud versions
Learn more about using app assessment from the user documentation here.
Version 1.2.0 introduces compatibility with Jira Data Center. This app can be installed and used on Jira Server or Data Center version 7.6 or later. Before migrating, check what data can be migrated with the Jira Cloud Migration Assistant.
Version 1.2.0 introduces compatibility with Jira Data Center. This app can be installed and used on Jira Server or Data Center version 7.6 or later. Before migrating, check what data can be migrated with the Jira Cloud Migration Assistant.
Version 1.1.5 fixes the bug identified in MIG-195
Version 1.1.4 includes minor bug fixes and improvements to error logging.
Version 1.1.3 includes minor bug fixes and preparation work for future compatibility with Jira Data Center.
Version 1.1.1 includes bug fixes and minor UI enhancements. You can now view a list of the projects selected when reviewing your migration plan.
Version 1.1.0 includes bug fixes, UI enhancements and the addition of a beta version of the app assessment feature (currently available in the Confluence Cloud Migration Assistant).
The app assessment feature is still being actively developed, and some functionality may be missing.
This release fixes some known bugs including: https://jira.atlassian.com/browse/MIG-140
This release includes fixes for some bugs found after the initial release.
This is the initial public release of the Jira Cloud Migration Assistant, allowing you to migrate individual projects from Jira Server to Jira Cloud. This version is compatible with Jira Software and Core on server only and is not compatible with Jira Service Desk or Jira Data Center. You can install it on Jira Server version 7.6 or later. Learn more about how the migration assistant works.
