Migrating from Jira Server to Jira Cloud

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.


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 we offer for Jira Server are also available on Cloud. Note that preconditions are no longer separate post functions; they are now part of the post function. See Workflow Preconditions for more information.
  • Conditions: Due to technical limitations, JSU for Jira Cloud provides only the User Is In Any Users condition. Most conditions provided in JSU for Jira Server are now integrated and maintained by Atlassian for Jira Cloud. The Status Changed and JQL conditions are 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: Due to technical limitations, the three custom fields we provide in JSU for Jira Server (Location, Location Select, and Directions) ) are not available on JSU for Jira Cloud.
  • Project Variables: JSU for Jira Server provides functionality to store variables per project which then can be used in workflow post functions. This feature is not currently supported on Jira Cloud; 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

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

User Is In Any Groups

(tick)

(tick) *

User Is In Any Roles

(tick)

(tick) *

User Is In Custom Field

(tick)

(tick) *

Value Field

(tick)

(tick) *

JQL

(tick)

(error) Jira Cloud architecture limitation

User Is In Any Users

(tick)

(tick)

Status Changed

(tick)

(info) 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

Date Compare

(tick)

(tick) *

Date Expression Compare

(tick)

(tick) *

Fields Required

(tick)

(tick) *

Regular Expression Check

(tick)

(tick) *

Date Window

(tick)

(tick) *

Linked Status

(tick)

(error)

* All features marked were originally supported by JSU for Jira Server but are currently maintained by Atlassian on Jira Cloud.


Post functions

Post Function

JSU Server/ Data Center

JSU Cloud

Copy Value From Other Field

 Copy Value from Other Field post function parameters


ParameterJSU Server/ Data CenterJSU Cloud
Precondition(tick)(tick)
Issue Relation(tick)(tick)
Perform as user(tick)(tick)
Simple copy field A to field B
(core functionality)
(tick)(tick)
Configure multiple fields in 1 post function(tick)(tick)
Overwrite, Append, Prepend(tick)(tick)
Separator(tick)(tick)
Create version if necessary(tick)(tick)
*** default value ***(tick)(error) Jira Cloud API limitations
*** empty ***(tick)(tick)
*** transition comment ***(tick)(tick)
*** last comment ***(tick)(tick)
*** new comment ***(tick)(tick)

(tick)

(tick) (99%)

Update any Issue Field

(tick)

(tick)

Clear Field Value

(tick)

(tick)

Create a Linked Issue

 Create a Linked Issue post function parameters

ParameterJSU Server/ Data CenterJSU Cloud
Precondition(tick)(tick)
Custom Field that enables linked issue creation(tick)(tick) Available with preconditions
Copy or Move Attachments(tick)(tick)
Copy Existing Attachments(tick)(tick)
Init target project as Inside same project(tick)(tick)
Init target project as Project variables(tick)(error)
Init target project as Selected Project(tick)(tick)
Init target project Defined by custom field selection(tick)(tick)
Create New Issue As User(tick)
New issue will be related via no relation(tick)(tick)
New issue will be related via issue link(tick)(tick)
New issue will be related via Sub-Task(tick)(tick)
New issue will be related via Epic/ Issue in Epic(tick)(tick)
Init selected issue type(tick)(tick)
Init issue type defined by custom field selection(tick)(tick)
Init issue priority(tick)(tick)
Init issue assignee(tick)(tick)

Copy from the Origin Issue to the New Issue:

Simple copy field A to field B
(core functionality)

(tick)(tick)

Copy from the Origin Issue to the New Issue:

Configure multiple fields in 1 post function

(tick)(tick)

Copy from the Origin Issue to the New Issue:

Overwrite, Append, Prepend

(tick)(tick)

Copy from the Origin Issue to the New Issue:

Separator

(tick)(tick)

Copy from the Origin Issue to the New Issue:

Create version if necessary

(tick)(tick)

Copy from the Origin Issue to the New Issue:

*** default value ***

(tick)(error) Jira Cloud API limitations

Copy from the Origin Issue to the New Issue:

*** empty ***

(tick)(tick)

Copy from the Origin Issue to the New Issue:

*** transition comment ***

(tick)(tick)

Copy from the Origin Issue to the New Issue:

*** last comment ***

(tick)(tick)

Copy from the Origin Issue to the New Issue:

*** new comment ***

(tick)(tick)


(tick)

(tick) (99%)

Linked Transition

 Linked Transition post function parameters

ParameterJSU Server/ Data CenterJSU Cloud
Precondition(tick)(tick)
Issue Relation(tick)(tick)
Transition(tick)(tick)
List Transitions of all workflows(tick)(tick)
Perform as user(tick)(tick)
Set Resolution(tick)(tick)
Set Resolution None(tick)(error) Jira Cloud API limitations
Copy Workflow Transition Comment(tick)(tick)
Check other siblings status(tick)
Simple copy field A to field B
(core functionality)
(tick)(tick)
Overwrite, Append, Prepend(tick)(tick)
Configure multiple fields in 1 post function(tick)(tick)
Separator(tick)(tick)
Create version if necessary(tick)(tick)
*** default value ***(tick)(error) Jira Cloud API limitations
*** empty ***(tick)(tick)
*** transition comment ***(tick)(tick)

*** last comment ***

(tick)(tick)

*** new comment ***

(tick)(tick)


(tick)

(tick) (99%)

Follow Up Transition

(tick)

(tick)

Copy or Move Attachments

(tick)

(tick)

Calculated Field

(error) 

(tick)

Custom fields

Field

JSU Server/ Data Center

JSU Cloud

Location Text

(tick)

(error)

Location Select

(tick)

(error)

Directions

(tick)

(error)

Additional features


The Product team has prioritized the features that matter most to you. The features marked with (error) 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!