For readability reasons, we only refer to Data Center or DC on the following pages, but explicitly include Server here unless otherwise mentioned.
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.
The two main challenges in this area are
- the general availability of features on both sides and
- the (automated) mapping of these features.
As of today, we're still working on both areas.
Important notice: we have not and will not bring all features or single functions to the Cloud.
JWT DC has grown steadily being among the first apps on the Atlassian Marketplace, and some features became since then, obsolete or have been replaced by newer, more powerful functions. However, we provide all the information needed to adequately represent all functions and thus establish feature parity between Data Center and Cloud.
Since the technical conditions for automated migration have only recently become available from Atlassian, we are planning to publish this by the end of the current year.
So what is the current state?
All the JWT configurations are stored within the workflows themselves. They are not migrated during a data migration from Jira Server/DC to Jira Cloud. So you have to recreate each workflow function in Jira Cloud.
In this documentation, we describe which JWT workflow functions are available in Jira Cloud as well and how existing JWT DC workflow functions can be migrated. That means they can be created manually in JWT Cloud using migration rules which are described in the subsequent pages.
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 Server / 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.
In the further course of this page, you will find a list of all JWT DC functionalities and how they may or may not be migrated to JWT Cloud.
Cloud availability and migration instructions
JWT Cloud availability
|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 byJira 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.
Calculated fields are and will not be part of JWT Cloud. In order to address our target audiences even more precisely, we have decided to deliver our calculated fields functionality separately in the cloud in the form of Smart Fields for Jira .
|Extended with the comprehensive list for manual migration of all relevant elements|
|Updated due to the release of Smart Fields for Jira|
|Initial public draft|