This page describes:
- Migration support details for the app content from server to cloud
- Differences between the server and cloud version of the app
If you are looking for documentation on Cloud to Server migration, please follow this link.
Background
IMPORTANT
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
- Post-functions
All the post-functions we offer on Jira Server, are also available on Jira Cloud. - Preconditions for post-functions
All the preconditions from Server are also available on Cloud. However, preconditions are no longer separate post-functions, they are now part of the post-function. See details here: Workflow Preconditions - Conditions/Validators
Due to technical limitations, JSU does not offer workflow conditions and validators in Jira Cloud. Only the User Is In Any Users Condition is offered by JSU. All other conditions and validators offered in JSU for Jira Server, are supported by Atlassian since 2016 and are integrated in Jira Cloud. However, the "Status Changed" and "JQL" conditions are still not supported. - Custom Fields
We provide 3 Custom Fields (Location, Location Select & 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 functionality to store variable per project which then can be used in Workflow Post-Functions (Project Variables). This is a feature we currently do not offer on Jira Cloud, but we have it in our backlog.
JSU On-premise vs Cloud feature comparison
We have achieved feature value parity; JSU for Jira Cloud is essentially as powerful as our best-selling JSU for Jira Server!
While some unavoidable API limitations in Jira Cloud restrict the full capabilities of some minute features of JSU for Jira Server, we've pushed the parity as far as Jira Cloud allows. Rest assured, this does not affect the value JSU brings into customizing your Jira workflows regardless of platform.
See the parity tables of JSU features below for complete details.
Conditions
Condition | JSU Server/ Data Center | JSU Cloud *Atlassian managed integration with Jira Cloud |
|---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
N/A - Jira Cloud natively prevents ANY → ANY transitions to/from the same status.
Validators
Validator | JSU Server/ Data Center | JSU Cloud *Atlassian managed integration with Jira Cloud |
|---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
All features marked were originally supported by JSU for Jira Server but are currently maintained by Atlassian on Jira Cloud.
Preconditions
Precondition | JSU Server/ Data Center | JSU Cloud |
|---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Post functions
Post Function | JSU Server/Data Center | JSU Cloud |
|---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Custom fields
Field | JSU Server/ Data Center | JSU Cloud |
|---|---|---|
|
| |
|
| |
|
|
Additional features
Feature | JSU Server/ Data Center | JSU Cloud |
|---|---|---|
|
| |
|
| |
|
| |
|
|
The Product team has prioritized the features that matter most to you. The features marked with 
in JSU for Jira Cloud are not being implemented in the near future due to low popularity. We are, however, always interested in hearing if any of these are critical for you. Contact us and share your use cases with our team. Help us make JSU even better for you!