This page describes:
- Migration support details for the app content from server to cloud
- Differences between the server and cloud version of the app
| Info |
|---|
If you are looking for documentation on Cloud to Server migration, please follow this link. |
Background
| Info | ||
|---|---|---|
| ||
The JSU Development team has been working closely with Atlassian to develop an automated solution for workflow migrations from Server to Cloud instances of Jira. While it is not yet available, Atlassian is working on implementing specific APIs compatible with the Cloud Migration Assistants as part of an Early Access Program, that is expected to be available in Spring 2021. Here, we guide you through a manual migration process that can be used until Atlassian's workflow API is live. |
To migrate Jira Server to Jira Cloud, you will need to consider the following things, depending on the functionality you are using in relation to the JSU App:
Workflow Condition/Validator/Post-Function
Workflows are automatically migrated to Jira Cloud, but the Workflow Configuration will be broken. This is due to how Workflow Conditions/Validators/Post-Functions work on Jira Cloud.
All Conditions/Validators/Post-Functions will need to be recreated
...
If you use JSU Server/Data Center and are planning a migration to Jira Cloud, you can use Atlassian’s Jira Cloud Migration Assistant (JCMA) to migrate most of your JSU workflow automations.
To learn more about migrating your JSU app and its workflow rules from Jira Server to Jira Cloud, see our Jira Cloud Migration Assistant page. Before proceeding with a migration, review our feature comparison tables below to understand the subtle differences between our Cloud and Server/Data Center apps.
| Info |
|---|
If you are looking for documentation on Cloud to Server migration, please see Migrating from Jira Cloud to Jira Server. |
Feature comparison summary:
- Post functions: All the post functions we offer for Jira Server, are also available on Jira Cloud.
- Preconditions for post - functions
: All the preconditions from we offer for Jira Server are also available on Cloud. However, Note that preconditions are no longer separate post - functions, ; they are now part of the post - function. See details here: See Workflow Preconditions for more information. - Conditions/Validators
: Due to technical limitations, JSU does not offer workflow conditions and validators in for Jira Cloud . Only provides only the User Is In Any Users Condition is offered by JSU. All other conditions and validators offered condition. Most conditions provided in JSU for Jira Server , are supported now integrated and maintained by Atlassian since 2016 and are integrated in for Jira Cloud. However, the " The Status Changed " and " JQL " conditions are still not supported in Jira Cloud. - Validators: All validators offered in JSU for Jira Server are supported by Atlassian and are integrated with Jira Cloud.
- Custom Fields
We provide 3 Custom Fields : Due to technical limitations, the three custom fields we provide in JSU for Jira Server (Location, Location Select & , and Directions) on the JSU Server App (Custom Fields ) . Due to technical limitations, Custom Fields are not available on JSU for Jira Cloud. - Project Variables
We offer : JSU for Jira Server provides functionality to store variable variables per project which then can be used in Workflow Post-Functions (Project Variables)workflow post functions. This feature is a feature we currently do not offer not currently supported on Jira Cloud, but we have it in our backlog.
...
- ; it's in our roadmap, and we will let you know as soon as it's available.
JSU for Jira Server vs Cloud feature comparison
Include Page JSU On-premise Server/Data Center vs Cloud feature comparison JSU On-premise Server/Data Center vs Cloud feature comparison
...