On this page:
|
Transform configuration elements inline during a migration
Cloud TCloud Migration Tool allows you to change how configuration elements from your Jira Server or Data Center instance will be migrated to a Jira Cloud site. We call these changes transformations. There are two ways to apply such actions to the configuration being migrated - : inline transformations and custom configuration mapping.
...
| Info |
|---|
Inline transformations don’t modify Jira Server/Data Center configuration (in any way) The Your Jira Server or Data Center instance's projects and configuration elements remain unchanged in your Jira Server or Data Center instance. You’re only transforming how the configuration you’re migrating will be uploaded to the Jira Cloud site. |
You may also use the transformations to optimize the configuration for your teams' needs when migrating to the cloud.
How
...
inline transformations are applied
...
Once the analysis of the configuration being migrated is complete, you'll receive a detailed report. It’ll include a list of all the planned changes , as well as and any problems or conflicts that were detected. For more information, you can check our article describing everything about the analysis phase of the migration.
...
After making all the necessary changes and applying them, you can continue the migration.
| Info |
|---|
New A new analysis is run when applying changes Keep in mind that once you confirm the draft changes, a new analysis will be performed automatically while the configuration is updated. The purpose of running Running a new analysis is intended to detect problems and conflicts that may have emerged from the newly updated configurations. |
...
Change project name and key
In the Analyze changes phase of a migration, you have the tools to change the name and key of a conflicting project before uploading it to the cloud. This way, you can clear conflicts between server and cloud projects and accomplish successful migrations.
...
Start a migration.
On the Analyze changes page of the migration wizard, hover over the name or key of a project.
Click the project name or key and edit them inline.
You can also use the Resolve button within the error message shown in the Problems area that notifies you about a project conflict.
After you click the Resolve button, a dialog will appear where you will be able to edit the project details. Make your changes to the project details and click Confirm.
Once you edit the project details, the project is marked with a Draft change label on the Analyze changes page.
Also, a new Apply changes button appears at the bottom when there are draft changes in the migration scope.
Click the Apply changes button to confirm your modifications and continue the migration.
Rename workflows, workflow schemes, and issue type schemes
You can rename workflows and workflow schemes during a migration. This way, you can resolve conflicts between server and cloud workflows/workflow schemes.
...
Start a migration.
In the Analyze changes page of the migration wizard, hover over the name of a workflow or workflow scheme.
Click the name of a workflow/workflow scheme/issue type scheme and change it inline.
You can also use the Resolve button within the error message shown in the Problems area that notifies you about a workflow/workflow scheme/issue type conflict.
After you click the Resolve button, a dialog will appear where you will be able to rename the workflow/workflow scheme/issue type scheme.
Once you edit the workflow/workflow scheme/issue type details, the configuration element is marked with a Draft change label on the Analyze changes page.
Also, a new Apply changes button appears at the bottom when there are draft changes in the migration scope.Click the Apply changes button to confirm your modifications and continue the migration.
Rename project filters
You can also rename filters during a migration to resolve conflicts or optimize your project configurations that will be uploaded to the cloud.
...