Page History
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
On this page
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
IntroductionFor readability reasons, we only refer to Data Center or DC on the following pages, but explicitly include Server here unless otherwise mentioned. |
JWT has an automated migration path that assists with migrating from JWT DC to JWT Cloud. The automated migration uses the Jira Cloud Migration Assistant (JCMA) which is still in beta for app migrations.
Pre-migration
- Please ensure that the correct version of JWT DC (version 3.3.0 or later) is installed on your Jira on-prem instance.
Please ensure that the correct version of JWT Cloud is installed on your Jira Cloud instance.
- Make sure that you have Jira Cloud Migration Assistant in the list of user-installed apps on your Jira DC instance if you are running Jira < 8.1.4 (for higher Jira versions it is already pre-installed). If you don't, then go to "Find new apps" and download it. If it's already installed, please be sure to have it updated to the most recent version.
- None of the projects you want to migrate must already exist in Jira Cloud (not even in the trash). This also includes the corresponding inactive workflows/workflow schemes!
Migration
- From your Jira DC instance, navigate to the System tab within the Jira administration and select Migrate to cloud from the Import and Export section of the left navigation.
- Follow the steps from the JCMA to define what you will migrate.
- In the Assess your apps step, make sure that you have marked Jira Workflow Toolbox status as Needed in cloud. If no green check is present, you have to upgrade to version JWT 3.3.0. Choose Not needed in cloud for xApps Library by Decadis.
UI Expand | ||
---|---|---|
| ||
The JCMA migration runs project-based, i.e. only those JWT functions are migrated which are defined in one of the workflows belonging to the migrated projects. The Atlassian documentation describes in What gets migrated with the Jira Cloud Migration Assistant the details of a migration, How the Jira Cloud Migration Assistant links your data from Atlassian gives a detailed description of how JCMA handles certain data. Nevertheless, we highlight specific scenarios, which you have to be aware of when migrating JWT:
|
UI Expand | ||||
---|---|---|---|---|
| ||||
The automated migration follows the rules described for the manual migration (besides "Execute remote action" and "Add or remove watchers", which does do not have an automated migration path so far). Specifically, this means that we cannot map all elements of a workflow rule or JWT parser expression exactly from JWT DC to JWT Cloud. The information which can be found in the column "Notes" of the description of the respective rules of the manual migration, e.g. Migrate 'Transition issue' is reflected as a feedback message in the Migration log. The same applies if a parameter/option is not present in JWT Cloud (marked with "-" in the documentation). Due to the different feature set of JWT DC and JWT Cloud, some parameters/options/values available in JWT DC are not available in JWT Cloud. If possible, they are replaced by default values, e.g. if a non-user field is specified for the "Run as" parameter. In this case, it will be replaced by the "Current user". Others will result in an error. These situations are reflected in the Migration log and include the following scenarios:
Certain parameters and values are handled differently in JWT Cloud. This is reflected in the Migration log and include
The latter applies to a number of conditions and validators. They have to be migrated to ones based on Jira expressions due to requirements from Jira Cloud. Especially JWT parser expressions are then not translated into Jira expressions (due to the very different paradigms used in both approaches). We strongly recommend checking the results in such cases (it may even happen that the migration results in an empty Jira expression): |
UI Expand | ||
---|---|---|
| ||
JWT supports to cancel and, if necessary, to re-run a migration. Note: Atlassian does not allow to cancel a migration before a certain amount of time has elapsed. When a JWT app migration was canceled, the migration process might several minutes to finish the currently processed workflow rule. The JCMA status reflects this as CANCELING. Workflow rules that were already migrated before canceling will not be reverted in any way. As soon as JWT successfully canceled the current migration, the JCMA status moves to INCOMPLETE. If you choose to re-run the migration from the Actions drop-down menu, you will find additional migration entries in the Migration log, one for every migration run. |
Note: If you have already migrated to the Cloud and need information regarding how to fix errors, see the Migration log.
Post-migration
After the migration has finished, JCMA displays a completion message.
We strongly recommend to check the Migration log in your target Cloud site, because it supports you with all the details on necessary post-migration tasks to be completed on your Cloud site.
Should you wish to consult the consult the JCMA migration logs, use the Actions drop-down menu.
Newer versions of the JCMA do not display the above completion message anymore. Instead, you can choose to view the JCMA migration logs from the Actions drop-down menu.
Note: The JCMA migration logs are provided as a CSV file. The way the file is opened and displayed is dependent of your local computing environment, which may not be able to present you with a clickable link to our Migration log.
Info | ||||||||
---|---|---|---|---|---|---|---|---|
In case if any warnings or errors were found during the migration, this post-migration report shows a status of
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|