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
- Maria Kazakou (Unlicensed)
- Deborah Scott (Unlicensed)
This page describes the required steps when migrating from a Jira Cloud instance to a Jira Server instance when you are using some of the default/JSU Workflow Condition/Validator/Post Functions in your workflows
Migration from Jira Cloud to Jira Server is not directly possible. You have to be careful as there are many validators and conditions which are built into Jira Cloud, but not in Jira Server. For that, you will need JSU.
JSU Cloud's additional post functions make it more powerful with its Related Issues, Perform as a different user, and many other post functions that you can use to automate your workflows without any coding.
Looking for documentation on a Server to Cloud migration? See our Migrating from Jira Server to Jira Cloud page.
Background
Years ago, Beecom donated some of JSU's modules to Jira Cloud. Atlassian integrated most of these JSU Workflow Condition/Validator/Post-Functions (based on JSU Server 1.4) into their native Jira Cloud environment which were still very basic modules. Since then, JSU Server has added many other functionalities to make it more powerful. When JSU on Cloud was released, it also had additional advanced form of the Post-functions as of JSU Server. If you perform a migration from Jira Cloud to Jira Server, those default/JSU Workflow Condition/Validator/Post-Functions do not exist in the default Jira Server Version but can be simply replaced with the JSU app.
How to fix the workflows
You can do one of the following to fix your migrated workflows:
Reconfigure the affected workflow modules with the ones from JSU. Afterward, remove the broken ones.
This is by far the safest way to do it but can be tedious.Export XML workflows, modify, import again.
Modify the workflows directly in the database - if you have the knowledge
It’s efficient but dangerous.
Workflow Condition/Post-Functions(JSU)
JSU Cloud post-functions are more powerful with its Related Issues, Perform as a different user, and many other functionalities.
Workflow Name | JSU Cloud Module-Key | JSU Server Module-Key |
|---|---|---|
Conditions | ||
User Is In Any Users (JSU) | com.atlassian.plugins.atlassian-connect-plugin:com.googlecode. jira-suite-utilities__userisinanyusers-condition | com.googlecode.jsu.workflow.condition.userisinanyusers-condition |
Post-Functions | ||
Clear Field Value (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__clearFieldValue-function | com.googlecode.jira-suite-utilitiesclearFieldValue-function |
Copy Value From Other Field (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__copyValueFromOtherField-function | com.googlecode.jira-suite-utilitiescopyValueFromOtherField-function |
Copy or Move Attachments (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__copymoveattachments-function | com.googlecode.jira-suite-utilitiescopymoveattachments-function |
Create a Linked Issue (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__createlinkedissue-function | com.googlecode.jira-suite-utilitiescreatelinkedissue-function |
Follow Up Transition (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__followuptransition-function | com.googlecode.jira-suite-utilitiesfollowuptransition-function |
Linked Transition (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__linkedtransition-function | com.googlecode.jira-suite-utilitieslinkedtransition-function |
Update any Issue Field (JSU) | com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__updateanyissuefield-function | com.googlecode.jira-suite-utilitiesupdateIssueCustomField-function |
Mapping between JSU Cloud TO JSU Server
The following description describes all the attributes which need to be mapped between the JSU Cloud and JSU Server Workflow functionality.
Post-Function Mapping: Clear Field Value (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example <function type="class">
<arg name="class.name">com.atlassian.plugin.connect.jira.workflow.RemoteWorkflowPostFunctionProvider</arg>
<arg name="full.module.key">com.atlassian.plugins.atlassian-connect-plugincom.googlecode.jira-suite-utilities__clearFieldValue-function</arg>
<arg name="remoteWorkflowPostFunctionConfiguration">
{"preconditions":[],
"preconditionAwareFunctionMode-textValue":"TRUE",
"field":"assignee",
"jsuCloudWorkflowParamsVersion-textValue":"2.8.0",
"scopeType":"SAME",
"source-scopeTarget":"ISSUE_IN_TRANSITION",
"destination-scopeTarget":"ISSUE_IN_TRANSITION",
"runAsUser-user":"qm:c14a3779-f1ba-496f-a5ef-dbb4ab1928f4:e5e9400a-0c77-440a-aa18-fbb585fbd6e8"}</arg>
<arg name="remoteWorkflowPostFunctionUUID">9dfcbdb2-7738-429c-9af4-e0a4b9490f9a</arg>
</function>
| Example <function type="class">
<arg name="scopeSource-linkEnd"></arg>
<arg name="maxAllowed-integerValue"></arg>
<arg name="runAsUser-user">admin</arg>
<arg name="field">assignee</arg>
<arg name="scopeType">SAME</arg>
<arg name="destination-scopeTarget">ISSUE_IN_TRANSITION</arg>
<arg name="full.module.key">com.googlecode.jira-suite-utilitiesclearFieldValue-function</arg>
<arg name="scopeDestination-linkEnd"></arg>
<arg name="preconditionAwareFunctionMode-textValue">ALWAYS</arg>
<arg name="jsuWorkflowParamsVersion-textValue">2.23.3-SNAPSHOT</arg>
<arg name="source-scopeTarget">ISSUE_IN_TRANSITION</arg>
<arg name="scopeDestination-jql"></arg>
<arg name="class.name">com.googlecode.jsu.workflow.function.ClearFieldValuePostFunction</arg>
<arg name="scopeSource-jql"></arg>
</function> |
Post-Function Mapping: Copy Value From Other Field (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example <function type="class">
<arg
name="class.name">com.atlassian.plugin.connect.jira.workflow.RemoteWorkflowPostFunctionProvider</arg>
<arg name="full.module.key">com.atlassian.plugins.atlassian-connect-
plugincom.googlecode.jira-suite-utilities__copyValueFromOtherField-function</arg>
<arg name="remoteWorkflowPostFunctionConfiguration">
{"preconditions": [],
"preconditionAwareFunctionMode-textValue":"TRUE",
"field.copyFieldSource1":"assignee",
"field.copyFieldDestination1":"customfield_10003",
"field.copyFieldMode1":"OVERWRITE",
"field.copyFieldSeparator1":"",
"field.createTargetValue1":false,
"jsuCloudWorkflowParamsVersion-textValue":"2.8.0",
"scopeType":"SAME",
"source-scopeTarget":"ISSUE_IN_TRANSITION",
"destination-scopeTarget":"ISSUE_IN_TRANSITION",
"runAsUser-user":""}
</arg>
<arg name="remoteWorkflowPostFunctionUUID">0e286a2f-b587-4432-8806-be35175e92a1</arg>
</function> | Example |
Post-Function Mapping: Create a Linked Issue (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example | Example |
Post-Function Mapping: Linked Transition (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example | Example
|
Post-Function Mapping: Update any Issue Field (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example
| Example |
Workflow Preconditions(JSU)
Preconditions in JSU Cloud are built-in as a part of the post-function. You can add as many preconditions inside a post-function. But in JSU Server preconditions are implemented as a separate post-function which acts as preconditions. All the preconditions from JSU Cloud are available in JSU Server as well, but they need different configurations.
Preconditions in JSU Server/Cloud |
Date Compare (JSU) |
Date Expression Compare (JSU) |
Date Window (JSU) |
Fields Required (JSU) |
JQL (JSU) |
Linked Status (JSU) |
Regular Expression Check (JSU) |
User Is In Any Groups (JSU) |
User Is In Any Roles (JSU) |
User Is In Custom Field (JSU) |
Value Field (JSU) |
Precondition Mapping: Value Field (JSU)
Arg Name: JSU Cloud | Arg Name: JSU Server |
|---|---|
Example | Example |
All other preconditions follow a similar pattern as above. As preconditions in JSU Cloud are built-in, you have to reconfigure all the preconditions manually in JSU Server.
Workflow Condition/Validator/Post Functions(Jira)
The following list of Workflow Condition/Validator/Post Functions which are built into the Jira Cloud environment can be replaced with JSU extensions. See below all attribute mappings between Jira Cloud and Jira Server.
Workflow Name | Jira Cloud Class-Name | JSU Class-Name (Jira Server) |
|---|---|---|
Conditions | ||
User Is In Any Group | com.atlassian.jira.workflow.condition.UserInAnyGroupCondition | com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition |
User Is In Any Project Role | com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition | com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition |
User Is In Custom Field | com.atlassian.jira.workflow.condition.UserIsInCustomFieldCondition | com.googlecode.jsu.workflow.condition.UserIsInCustomFieldCondition |
Value Field | com.atlassian.jira.workflow.condition.ValueFieldCondition | com.googlecode.jsu.workflow.condition.ValueFieldCondition |
Validators | ||
Date Compare Validator | com.atlassian.jira.workflow.validator.DateFieldValidator | com.googlecode.jsu.workflow.validator.DateCompareValidator & com.googlecode.jsu.workflow.validator.DateExpressionCompareValidator |
Date Window Validator | com.atlassian.jira.workflow.validator.WindowsDateValidator | com.googlecode.jsu.workflow.validator.WindowsDateValidator |
Field Required Validator | com.atlassian.jira.workflow.validator.FieldRequiredValidator | com.googlecode.jsu.workflow.validator.FieldsRequiredValidator |
Regular Expression Check | com.atlassian.jira.workflow.validator.RegexpFieldValidator | com.googlecode.jsu.workflow.validator.RegexpFieldValidator |
Post-Functions | ||
Clear Field Value | com.atlassian.jira.workflow.function.issue.ClearFieldValuePostFunction | com.googlecode.jsu.workflow.function.ClearFieldValuePostFunction |
Copy Value From Other Field | com.atlassian.jira.workflow.function.issue.CopyValueFromOtherFieldPostFunction | com.googlecode.jsu.workflow.function.CopyValueFromOtherFieldPostFunction |
Update Issue Custom Field | com.atlassian.jira.workflow.function.issue.UpdateIssueCustomFieldPostFunction | com.googlecode.jsu.workflow.function.UpdateIssueCustomFieldPostFunction |
Mapping between Jira Cloud Modules TO JSU Server
The following description describes all the attributes which need to be mapped between the Jira Cloud and Jira Server Workflow functionality.
Condition Mapping: User Is In Any Group
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
group | hidGroupsList (each group is separated by @@ and requires a @@ at the end) |
Example | Example |
Condition Mapping: User Is In Any Project Role
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
projectRoleIds | hidRolesList (each group is separated by @@ and requires a @@ at the end and groups required to be mapped between id to group name) |
Example | Example |
Condition Mapping: User Is In Custom Field
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Condition Mapping: Value Field
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Validator Mapping: Date Compare Validator
The Jira Cloud 'Date Compare Validator' combines 2 JSU Date Compare Validators which are:
Date Compare Validator (compareTypeField = true)
Date Expression Compare Validator (compareTypeField = false)
which of the 2 Validators to use is defined by the Jira Cloud argument name 'compareTypeField'
Date Compare Validator
All argument names are the same between Jira Cloud and Jira Server. Argument
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Date Expression Compare Validator
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
compareTypeField (must be false to map to the 'Date Expression Compare Validator') | not required for Jira Server. |
conditionSelected | conditionSelected |
includeTimeSelected | includeTimeSelected |
date1Selected | date1Selected |
expression | expressionSelected |
Example | Example
|
Validator Mapping: Date Window Validator
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Validator Mapping: Field Required Validator
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
hidFieldsList | hidFieldsList |
contextHandling | contextHandling |
errorMessage | customErrorMessage-textValue |
Example | Example |
Validator Mapping: Regular Expression Check
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Post-Function Mapping: Clear Field Value
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |
Post-Function Mapping: Copy Value From Other Field
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example
|
Post-Function Mapping: Update Issue Custom Field
All argument names are the same between Jira Cloud and Jira Server.
Arg Name: Jira Cloud | Arg Name: Jira Server |
|---|---|
Example | Example |