JWT DC to JWT Cloud migration hub | Decadis App Help Center

Considering your move to the Cloud? Make sure to check out our automated app migration path.

Introduction

Migrating from Data Center to Cloud is not a trivial task - and JWT's configuration is no exception. Basically, workflow extensions provided by 3rd party apps are incompatible between Data Center and Cloud due to fundamental technical differences between those two platforms.

We offer a JWT Advanced Edition that includes migration assistance. Make sure to check out all the available extras included before planning your migration.

A key challenge when migrating to Jira Cloud is feature availability. JWT DC has evolved over many years as one of the first apps on the Atlassian Marketplace. During this time, some features have become obsolete or have been replaced by newer, more powerful alternatives. This documentation provides the information you need to understand the available options and achieve feature parity where possible. However, not every JWT DC feature or individual function is available in JWT Cloud, and some are not planned for migration.

This guide explains which JWT workflow functions are available in Jira Cloud and how to migrate existing JWT DC workflow functions where a Cloud equivalent is available.

Automated migration path

Manual migration instructions

Not all workflow functions known in JWT DC are available in JWT Cloud. The main reason being the different architecture of Jira Cloud as described in A general note about JWT for Jira Cloud , e.g. you can't rely on an execution order of post functions when transitioning an issue or you only can use Jira expressions in conditions and validators. Besides that, the Cloud platform itself is not as mature as the DC platform which means that JWT Cloud app does not yet have the maturity its DC variant has. The entire team is working hard on continuously closing or at least narrowing the gap with JWT DC.

This page lists all JWT DC functionalities and their potential migration to JWT Cloud.

Cloud availability and migration instructions

• Conditions

JWT DC	JWT Cloud availability	Notes
Compare two values condition	✅	See Migrate 'Compare two values condition'.
Condition on a list of issue keys	-	This function is deprecated in JWT DC and is thus not covered in this manual.
Condition based on cascading select list value	⚠️	Mappable by Jira expression condition : see Migrate 'Condition based on cascading select list value'.
Condition based on JQL query	-
Condition based on regular expression	⚠️	Mappable by Jira expression condition: see in Migrate 'Condition based on regular expression'.
Condition on JWT project property	-
Condition on linked issues	⚠️	Mappable by Jira expression condition: see Migrate 'Condition on linked issues'.
Condition on sub-tasks	⚠️	Mappable by Jira expression condition: see Migrate 'Condition on sub-tasks'
Except assignee	⚠️	Mappable by Jira expression condition: see Migrate 'Except assignee'.
Except reporter	⚠️	Mappable by Jira expression condition: see Migrate 'Except reporter'.
Except users in a field	⚠️	Mappable by Jira expression condition: see Migrate 'Except users in a field'.
Fields required	✅	See Migrate 'Fields required'.
Hide transition from user (bulk operation only)	-
Hide transition from user (JWT function only)	-
Logical condition	⚠️	Mappable by Jira expression condition: see Migrate 'Logical condition'.
Only users in a field	⚠️	Mappable by Jira expression condition: see Migrate 'Only users in a field'.
User is not in project role	⚠️	Mappable by Jira expression condition: see Migrate 'User is not in project role'.
Users are/aren't in project role (condition)	-

• Validators

JWT DC	JWT Cloud availability	Notes
Compare two values validator	✅	See Migrate 'Compare two values validator'.
Fields required or changed	✅	See Migrate 'Fields required or changed'.
Logical validator	⚠️	Mappable by Jira expression validator: see Migrate 'Logical validator'.
Users are/aren't in project role (validator)	-
Validation based on JQL query	-
Validation based on regular expression	⚠️	Mappable by Jira expression validator: see Migrate 'Validation based on regular expression'
Validation of JWT project property	-
Validation of linked issues	⚠️	Mappable by Jira expression validator: see Migrate 'Validation of linked issues'.
Validation of sub-tasks	⚠️	Mappable by Jira expression validator: see Migrate 'Validation of sub-tasks'.
Validation on a list of issue keys	-	This validator is deprecated in JWT DC and is thus not covered in this manual.

• Post functions

JWT DC	JWT Cloud availability	Notes
Add comment	✅	See Migrate 'Add comment'.
Add or disable option in (multi-) select list, radio button, or checkbox field	-
Add or disable option in cascading select list field	-
Add or remove watchers	✅	See Migrate 'Add or remove watchers'.
Assign to project role	-
Clone issue link	-	This function is deprecated in JWT DC and is thus not covered in this manual.
Copy a parsed text to a field	⚠️	Mappable by Update fields: see Migrate 'Copy a parsed text to a field'.
Copy cascading select list value	-
Copy excerpted value	-
Copy JWT project property	-
Copy JWT user property	-
Copy or add custom field value to issue description	⚠️	Mappable by Update fields: see Migrate 'Copy or add custom field value to issue description'.
Create issue	✅	See Migrate 'Create issue'.
Copy field values from multiple issues	-
Copy field values from linked issues or sub-tasks	-
Create issue link	-
Delete issue link	-
Format field value	-
Inhibit temporary fields' auto-clearance	-	This function is deprecated in JWT DC and is thus not covered in this manual.
Log work	-
Mathematical or date-time expression calculator	⚠️	Mappable by Update fields: see Migrate 'Mathematical or date-time expression calculator'.
Move issue	-
Regular expression renderer	-
Send email	✅	See Migrate 'Send email'.
Set issue reporter to current user	⚠️	Mappable by Update fields: see Migrate 'Set issue reporter to current user'.
Set or create JWT project property	-
Set or create JWT user property	-
Transition issue	✅	See Migrate 'Transition issue'.
Update field based on rules	-
Update linked issue or sub-task	✅	See Migrate 'Update linked issue or sub-task'.
Update or copy field values	✅	See Migrate 'Update or copy field values'.

• Calculated fields

Calculated fields are not part of JWT Cloud and cannot be migrated automatically from JWT Data Center. However, the functionality is still available in Jira Cloud through our dedicated app Advanced Formula Fields.

Advanced Formula Fields is designed specifically for calculated and formula-based field use cases in Cloud and goes beyond the calculated fields functionality known from JWT DC, offering a broader and more powerful feature set for creating dynamic values, performing calculations, and displaying formula results directly in Jira work items.

When planning your migration, treat calculated fields as a separate migration topic: they will not be recreated as JWT Cloud workflow functions, but comparable functionality — plus many additional capabilities — can be implemented with Advanced Formula Fields for Jira. Reach out to our support team to get help and discounts as an existing JWT customer.

• Parser expressions

The JWT Cloud expressions differ from those used by JWT DC. So they need to be migrated like described in Migrate JWT parser expressions. with detailed instructions related to parsing modes, field codes, and parser functions.

• Temporary fields

Temporary fields differ from the those used by JWT DC. While you cannot migrate them JWT Cloud offers to store values in Temporary text or Temporary number fields in a dedicated Execute sequence of actions post function.

• Automation rules

Automation rules are not part of JWT Cloud. The main reason is the availability of Atlassian's own automation engine.

• JWT calendars

JWT calendars are not part of JWT Cloud. This might change related to customer demand.

• JWT JQL functions

JWT JQL functions are not part of JWT Cloud. This might change related to customer demand.