Our new Appfire Documentation Space is now live!
Take a look here! If you have any questions please email support@appfire.com
Migrating from Jira Cloud to Jira Server/Data Center
This article explains the steps required when migrating a Jira Cloud instance to Jira Server/Data Center when you were using JMWE workflow extensions on your JIRA Cloud instance.
Background:
Because of the way Atlassian's Connect framework is implemented, workflows extensions (validators, conditions, and post-functions) provided by add-ons are incompatible between Jira Server/Data Center and Jira Cloud. The entire JMWE configuration is contained within the workflows themselves. So you need to take a backup of your entire Jira Cloud instance, identify the workflows and transitions that use JMWE workflow extensions, and fix them.
See here for the Cloud to Server migration challenges/limitations.
Migrating workflows
Before you begin fixing your workflows, publish all your workflows to avoid duplicate work (between the draft and corresponding published workflow)
- 1 Migrating workflows
- 1.1 Step 1 - Backup the Cloud instance and open the XML file
- 1.2 Step 2 - Identify workflows and transitions using JMWE post-functions
- 1.3 Step 3 - Identify workflows and transitions using JMWE conditions
- 1.4 Step 4 - Identify workflows and transitions using JMWE validators
- 1.5 Step 5 - Manually edit the XML file
- 1.6 Step 6 - Import the backup into your JIRA Server/Data Center instance
- 1.7 Step 7 - Manually edit the workflows
- 1.7.1 Before you start
Step 1 - Backup the Cloud instance and open the XML file
Using JIRA's XML backup utility backup your entire Jira Cloud instance for server.
Unzip the backup.
Find the
entities.xml
file.Open it in an editor that supports very large files.
Step 2 - Identify workflows and transitions using JMWE post-functions
At the end of this step, you will create a table with the workflow name and the transition names of all the workflows that contain JMWE post-functions.
Post-function Name | Transition Name | Workflow Name |
---|---|---|
|
|
|
Find the text
"DelegatingPostFunction"
Right above the search under the
“full.module.key”
find the post-function nameWrite down the post-function name in the table
Work your way up on the file from the line that contains "DelegatingPostFunction" to find the name of the transition on which the post-function is configured. You can identify it under the <actions> tag.
Write down the transition name in the table.
Work your way up further on the file from the line you have found the transition, to find the name of the workflow. You can identify it under the <Workflow> tag. Refer to the above image.
Write down the workflow name.
Find the next instance of
DelegatingPostFunction
Repeat steps 2 to 6 until you reach the end of the file.
Repeat steps 1 to 7 but searching for RemoteWorkflowPostFunctionProvider instead of DelegatingPostFunction
Now you will have a list of transitions and their corresponding workflow name.
Post-function Name | Transition Name | Workflow Name |
---|---|---|
Set field Value | Create, Done | SFVFUP |
Comment issue | Start Progress, Reject | TPI |
Step 3 - Identify workflows and transitions using JMWE conditions
Condition Name | Transition Name | Workflow Name |
---|---|---|
|
|
|
At the end of this step, you will create a table with the workflow name and the transition names of all the workflows that contain JMWE conditions.
Find the text
com.atlassian.jira.workflow.condition.JiraExpressionWorkflowCondition
Below the search under the argument
“full.module.key”
find the condition nameWrite the condition name in the table
Work your way up on the file from the line that contains
com.atlassian.jira.workflow.condition.JiraExpressionWorkflowCondition
to find the name of the transition on which the condition is configured. You can identify it under the<actions>
tag.Write down the transition name in the table.
Work your way up further on the file from the line you have found the transition, to find the name of the workflow. You can identify it under the
<Workflow>
tag. Refer to the above image.Write down the workflow name.
Find the next instance of
com.atlassian.jira.workflow.condition.JiraExpressionWorkflowCondition
Repeat steps 2 to 6 until you reach the end of the file.
Condition Name | Transition Name | Workflow Name |
---|---|---|
Linked issues condition | Create, Done | SFVFUP |
Current Status Condition | Start Progress, Reject | TPI |
Step 4 - Identify workflows and transitions using JMWE validators
Validator Name | Transition Name | Workflow Name |
---|---|---|
|
|
|
At the end of this step, you will create a table with the workflow name and the transition names of all the workflows that contain JMWE validators.
Find the text
com.atlassian.jira.workflow.validator.JiraExpressionWorkflowValidator
Below the search under the argument
“full.module.key”
find the validator nameWrite the validator name in the table
Work your way up on the file from the line that contains
com.atlassian.jira.workflow.validator.JiraExpressionWorkflowValidator
to find the name of the transition on which the condition is configured. You can identify it under the<actions>
tag.Write down the transition name in the table.
Work your way up further on the file from the line you have found the transition, to find the name of the workflow. You can identify it under the
<Workflow>
tag. Refer to the above image.Write down the workflow name.
Find the next instance of
com.atlassian.jira.workflow.validator.JiraExpressionWorkflowValidator
Repeat steps 2 to 6 until you reach the end of the file.
Validator Name | Transition Name | Workflow Name |
---|---|---|
Linked issues validator | Create, Done | SFVFUP |
Field Required Validator | Start Progress, Reject | TPI |
Step 5 - Manually edit the XML file
class.name
changes for validators and conditions native to Jira Cloud.Most issues with JMWE Validators and Conditions can be resolved by a simple search and replace. For each entry in the table below replace the text in the first column (Current
class.name
) with the text in the second column (Newclass.name
) throughout the file using ReplaceAll.
Current class.name | New class.name |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Step 6 - Import the backup into your JIRA Server/Data Center instance
Zip back the XML file.
Log in to Jira as an administrator.
Restore the data from the xml file into your Jira Server/Data Center instance.
Step 7 - Manually edit the workflows
By now, you will have completed the XML fixes for workflow conditions, validators and unavailable workflow post-functions. The remaining fixes must be done by recreating the post-function and deleting the existing ones.
Before you start
Open the table prepared in Step 2.
On Jira Server/Data Center and Jira Cloud:
Go to the Administration section
Click on the cogwheel
Go to Issues → Workflows
Recreate the post-functions in Jira Server/Data Center
→ For each affected workflow listed in the table open the workflow in an edit mode in the Cloud and the Server/Data Center.
→ For each affected transition listed for the workflow, go to that transition in the editor and then to the Post Functions
tab.
Locate the first strange looking post-function in Jira Server/Data Center. You can easily identify JMWE post-functions imported from Cloud because they appear strange, with either Class:
com.atlassian.jira.workflow.function.DelegatingPostFunction
or Class:com.atlassian.plugin.connect.jira.workflow.RemoteWorkflowPostFunctionProvider
similar to this:Locate the same post-function in Jira Cloud by its position in the list and edit it to see its full configuration.
Recreate the post-function:
Click on
Add post-function
in Jira Server/Data Center.Recreate the post-function looking at its equivalent configuration in Jira Cloud. While recreating the post-function you might notice some known incompatibilities in JMWE Server/Data Center.
Move the post-function right before the existing post-function
Delete the existing post-function in Jira Server/Data Center.
Once all the transitions in a workflow are fixed, publish the workflow.