Versions Compared

Old Version 14

changes.mady.by.user Maria Kazakou

Saved on

compared with

New Version Current

changes.mady.by.user Deborah Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

We have achieved feature value parity

!

; JSU

in

for Jira Cloud is essentially as powerful as

the

our best-selling JSU

in

for Jira Server

. There are, however,

!

While some unavoidable API limitations in Jira Cloud

, which

restrict the full capabilities

for

of some minute features

that are in

of JSU for Jira Server

. We

, 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

parity tables of JSU features below for complete details.

 

Conditions

Feature

Condition

JSU Server/ Data Center

JSU Cloud

*Atlassian managed integration with Jira Cloud

User Is In Any Groups

Condition

(tick)

(tick) *

User Is In Any Roles

Condition

(tick)

(tick) *

User Is In Custom Field

Condition

(tick)

(tick) *

Value Field

Condition

(tick)

(tick) *

JQL

Condition

(tick)

(error) Jira Cloud architecture limitation

User Is In Any Users

Condition

(tick)

(tick)

Status Changed

Condition

(tick)

(error) Currently not supported

(info) N/A - Jira Cloud natively prevents ANY → ANY transitions to/from the same status.


Validators

Feature

Validator

JSU Server/ Data Center

JSU Cloud

*Atlassian managed integration with Jira Cloud

Date Compare

Validator

(tick)

(tick) *

Date Expression Compare

Validator

(tick)

(tick) *

Fields Required

Validator

(tick)

(tick) *

Regular Expression Check

Validator

(tick)

(tick) *

Date Window

Validator

(tick)

(tick) *

Linked Status

ValidatorFeatureServer/ Data CenterCloudDate Compare Precondition(tick)(tick)Date Expression Compare Precondition(tick)(tick)Date Window Precondition(tick)(tick)

Fields Required Precondition

(tick)(tick)Linked Status Precondition(tick)(tick)Regular Expression Check Precondition(tick)(tick)User Is In Any Groups Precondition(tick)(tick)User Is In Any Roles Precondition(tick)(tick)User Is In Custom Field Precondition(tick)(tick)Value Field Precondition(tick)(tick)JQL Precondition(tick)(tick)

Post-functions

Feature

(tick)

(error)

(tick) *

Preconditions

* 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

Post-FunctionUpdate any Issue Field Post-Function(tick)(tick)Clear Field Value Post-Function(tick)

(tick)

Create a Linked Issue(tick)(tick) (99%)Linked Transition(tick)(tick) (99%)Follow Up Transition(tick)(tick)Copy or Move Attachments Post-Function(tick)

(tick)

Calculated Field Post-Function

(error) (tick)

(tick)(tick) (99%)
Expand
titleCopy Value from Other Field post
-
function parameters
Feature

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

post-functionFeature

Expand
titleCreate 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)
(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

Feature

(tick)

(tick) (99%)

Linked Transition

Expand
titleLinked 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)
(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

Custom Field

(tick)

(error)

Location Select

Custom Field

(tick)

(error)

Directions

Custom Field

(tick)

(error)

Additional features

Feature

JSU Server/ Data Center

JSU Cloud

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


Info

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 have maintained the features that truly matter.However, we are always interested to know

 

We are, however, always interested in hearing if any of

those

these are critical for you. Contact us and share your use cases with our team. Help us make JSU even better for you!