Date: Fri, 29 Mar 2024 16:30:06 +0100 (CET) Message-ID: <1925959681.612.1711726206784@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_611_520481304.1711726206784" ------=_Part_611_520481304.1711726206784 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Considering your move to the Cloud? Make sure to check out our <= a href=3D"/display/JWTCLOUD/Automated+migration+path">automated app migrati= on path.
For readability reasons, we only refer to Data Center&n= bsp;or DC on the following pages, but explicitly include <= strong>Server here unless otherwise mentioned.
Migrating from Data Center to Clou= d is not a trivial task - and JWT's configuration is no exception. Basicall= y, workflow extensions provided by 3rd party apps are incompatible between = Data Center and Cloud due to fundamental technical differences between thos= e two platforms.
One of the main challenges in this= area is the general availability of features on both sides. JWT DC has grown steadily bein= g among the first apps on the Atlassian Marketplace, and some features beca= me since then, obsolete or have been replaced by newer, more powerful funct= ions. However, we provide all the information needed to adequately represen= t all functions and thus establish feature parity between Data Center and C= loud. In adition, it's important to understand we have not and will not bring all f= eatures or single functions to the Cloud.
So what is the current state?
With our latest release of JWTC, paired with the release of JWT DC 3.3.0= , we're more than happy to announce that JWT now comes with an automated app migration path= .
In this documentation, we describe which JWT workflow func= tions are available in Jira Cloud as well and how existing JWT DC workflow = functions can be migrated.
Not all workflow function=
s known in JWT DC are available in JWT Cloud. The main reason bein=
g the different architecture of Jira Cloud as described in A general note about JWT for Jira Cloud
In the further course of this page= , you will find a list of all JWT DC functionalities and how they may or ma= y not be migrated to JWT Cloud.
Date | Notes |
---|---|
&nbs= p; |
Webinar section added |
&nbs= p; |
Extended due to introducing an automated app migration pat= h |
&nbs= p; |
Extended with the comprehensive list for manual = migration of all relevant elements |
&nbs= p; |
Updated due to the release of Smart Fields for Jira |
&nbs= p; |
Initial public draft |
If you still have questions, feel = free to refer to our support team.