Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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.

(warning) All Conditions/Validators/Post-Functions will need to be recreated (warning)

  • 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 in Jira Cloud is essentially as powerful as JSU in Jira Server/Data Center. 

There are, however, some unavoidable API limitations in Jira Cloud, which restrict full capabilities for some minute features that are in JSU for Jira Server/Data Center. 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 overview of JSU features below. 






Copy Value from Other Field post-function

FeatureServer/ Data CenterCloud
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)

Create a Linked Issue post-function

FeatureServer/ Data CenterCloud
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)(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)

Copy within the Origin Issue:

Simple copy field A to field B
(core functionality)

(tick)(tick)

Copy within the Origin Issue:

Configure multiple fields in 1 post function

(tick)(tick)

Copy within the Origin Issue:

Overwrite, Append, Prepend

(tick)(tick)

Copy within the Origin Issue:

Separator

(tick)(tick)

Copy within the Origin Issue:

Create version if necessary

(tick)(tick)

Copy within the Origin Issue:

*** default value ***

(tick)(error) Jira Cloud API limitations

Copy within the Origin Issue:

*** empty ***

(tick)(tick)

Copy within the Origin Issue:

*** transition comment ***

(tick)

(tick)

Copy within the Origin Issue:

*** last comment ***

(tick)(tick)

Copy within the Origin Issue:

*** new comment ***

(tick)(tick)

Linked Transition post-function

FeatureServer/ Data CenterCloud
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)(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)



Custom fields

FieldServer/ Data CenterCloud
Location Text Custom Field(tick)(error)
Location Select Custom Field(tick)(error)
Directions Custom Field(tick)(error)

Additional features

FeatureServer/ Data CenterCloud

Issue Transitions Tab

(tick)

(error)

Bulk Copy(tick)(error)
Transition Trigger Service(tick)(error)

Calculated Field

(error)(tick)




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


The Beecom Products team has decided not to include the features marked with (error) in JSU for Jira Cloud in the near future due to low popularity. We have maintained the features that truly matter.

However, we are always interested to know if any of those are critical for you. Contact us and share your use cases with our team. Help us make JSU even better for you!



  • No labels