Inline configuration transformations

Transform configuration elements inline during a migration

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.

The inline transformations are quick actions you can apply to a set of configuration elements with just a few clicks in the UI. This feature set allows you to edit your configuration elements during the Analyze Changes phase of migrations.

You have the following distinct inline transformations available when using the Cloud Migration Tool:

• renaming projects, workflows, workflow schemes, issue type schemes and project filters, and

• changing project keys

Open

With these transformations, you can resolve conflicts between server and cloud configurations detected during the migration analysis. You can also fix problems like duplicate Jira Server/Data Center configuration elements in the migration scope, like filters with the same name and owner.

For example, you can apply transformations when the Cloud Migration Tool alerts you that there’s already a workflow with the same name on the cloud. In this case, you can select a different name for the workflow during the migration. This will add a new copy of the workflow with the updated name to the cloud.

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 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.

The transformations applied in the analysis phase are not final until confirmed with the Apply changes button on the Analyze changes page. Before confirmation, each change to a project, workflow, workflow scheme, or filter is marked as a Draft change in the UI.

After making all the necessary changes and applying them, you can continue the migration.

Open

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.

To change a project name or key:

1. Start a migration.

2. On the Analyze changes page of the migration wizard, hover over the name or key of a project.

3. Click the project name or key and edit them inline.

4. You can also use the Resolve button within the error message shown in the Problems area that notifies you about a project conflict.

5. 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.

6. 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.

7. 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.

To rename a workflow/workflow scheme/issue type scheme:

1. Start a migration.

2. In the Analyze changes page of the migration wizard, hover over the name of a workflow or workflow scheme.

3. Click the name of a workflow/workflow scheme/issue type scheme and change it inline.

4. 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.

5. After you click the Resolve button, a dialog will appear where you will be able to rename the workflow/workflow scheme/issue type scheme.

6. 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.

7. 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.

The Cloud Migration Tool detects filter conflicts when:

• Jira Server/DC filters with the same names and owners were added to the migration.

• A Jira Server/DC filter matches a filter on Jira Cloud by name and owner.

In these cases, you can resolve the filter conflicts without even leaving the migration wizard.

To rename a project filter:

1. Start a migration.

2. In the Analyze changes page of the migration wizard, hover over the name of a filter.

3. Click the filter name and change it inline.

4. You can also use the Resolve button within the error message shown in the Problems area that notifies you about a filter conflict. A window to rename the filter will appear when you click the button.

5. Once you edit the name, the filter 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.

6. Click the Apply changes button to confirm your modifications and continue the migration.