Date: Fri, 29 Mar 2024 07:29:39 +0000 (UTC) Message-ID: <62583061.1.1711697379227@591f5d7b35f4> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_136019117.1711697379213" ------=_Part_0_136019117.1711697379213 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you and your team are moving from Jira Server or= Jira Data Center to Jira Cloud (or from Jira Cloud to Jira Server o= r Data Center for that matter), you=E2=80=99re more than likely wondering i= f your marketplace apps are compatible and how the move will impact them. I= f you=E2=80=99re reading this - you=E2=80=99re wondering about ActionableAg= ile for Jira specifically.
When you migrate your Jira issue data - make sure to migrate the data in= such a way that the historical data is migrated as well. The CSV importer = in Jira does not migrate historical data for example. The Jira Cloud Migrat= ion Assistant does migrate Issue History as documented at h= ttps://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-clou= d-migration-assistant-993925216.html . Without the historical data - Ac= tionableAgile for Jira will not be able to identify the status history.
Since ActionableAgile for Jira only reads data from an instance= and uses localStorage/sessionStorage for the settings on a per browser bas= is. There is no data to migrate.
There is no impact. Your end-users will continue to select the data that= they want to analyze just like they would on Jira Server.
For the core part of ActionableAgile for Jira, the user-facing f= eatures are the same between the different hosting versions. The o= nly thing to keep in mind is that changes, either for bug fixes or enhancin= g functionality, often release to different hosting versions at different s= chedules. We usually release to Jira Cloud initially, followed by releases = to Jira Server and Data Center.
For non-user-facing aspects, there may be some differences between the p= latform. For example, in Jira Cloud, the number of search threads is hardco= ded though it is configurable in Jira Server and Jira Data Center. All of t= he differences are documented in the https://55degrees.atlassian.net/wiki/spaces/ActionableAgile/overview= documentation.
You will need a new license if you=E2=80=99re moving to Jira Cloud since= the Atlassian Marketplace treats the licenses differently. For more detail= s, please visit https://www.atlassia= n.com/licensing/marketplace#general-faqs.