Migration to Cloud
Last update: Nov 17th, 2023
If you are considering to migrate your Jira instance to Cloud we we would be happy to introduce our Release Gadgets Cloud App. This post is mainly about “How to migrate?” and “What is the difference?” so you can make an educated decision.
Let’s start with so quick Q&A.
FAQ about Cloud App
Question | Answer |
|---|---|
Is it secured? | Yes, we are Cloud security Participant in collaboration with Atlassian & Bugcrowd where 300+ researches are continuously trying to breach our security. As a result of this effort and meeting reliability and resilience requirements we are now Cloud Fortified by Atlassian. Also please check https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-B:-Technical-and-Organizational-Security-Measures |
Did they find any vulnerabilities? | Rarely, a number items were reported. All of them are fixed on timely manner. We have a practice in place to communicate within 48 hours any P1 and P2 items found and our action to eliminate. To date only P3 & P4 were found. |
Where the data is stored? | Distributed cluster in two location in Europe (Germany, Finland). Also backups in AWS (Germany). But since we are talking Gadgets only practically no client Jira data is stored. |
Is it GDPR/CCPA compliant? | Yes, please check https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441 |
The biggest client tier using the App? (Performance Concerns) | 1800 (as of Nov 17th, 2023) |
Is there any automation migration tool? | Nope, Dashboards and Third Party Gadgets are not included in Automated migration tool but there is some help with manual migration. See below. |
Functionality is the same or different? | Same same. See below. |
Do you plan to abandon Server Apps? | Nope, not at all. We have single code base for Server and DataCenter and we actually keep on investing in the Apps as the segment is keep on stable. So, while Atlassian allows upgrade of Server versions … clients will be receiving the same builds we are preparing for DataCenter edition. Read more here: https://releasemanagement.atlassian.net/wiki/spaces/GFJR/pages/2574024705 |
More details
Migration assistance
Automated migration is not supported
As of now (Nov 17th, 2023) Jira Server/Datacenter to Cloud Migration tool does not support Jira Dashboards and Third Party Gadgets (Partner Gadgets) migration described in this feature request https://jira.atlassian.com/browse/MIG-164. That’s why we have equipped you with the following tips to help you with the manual migration of gadget configurations.
Assistance with manual migration
Once you migrated your Jira data from Server/Datacenter to Cloud, you need to manually recreate gadgets and their configurations. First, however, you need to know what gadgets were added to which dashboards.
You can fetch that information using SQL queries run in your Jira database.
SQL snippets have been tested in Postgres and MySQL databases but should work in all other Jira-supported databases either as is or with minimal modifications.
List of Dashboards where Release Gadgets are used
Postgres
SELECT jira.baseurl || '/secure/Dashboard.jspa?selectPageId=' || pp.id as "dashboard_url",
pp.pagename as "dashboard_name",
pp.username as "dashboard_owner",
count(pc.id) as "gadget_count"
FROM portletconfiguration pc,
portalpage pp,
(select propertyvalue "baseurl"
from propertyentry PE join propertystring PS on PE.id=PS.id
where PE.property_key = 'jira.baseurl') "jira"
WHERE pc.portalpage = pp.id
AND pc.gadget_xml LIKE '%app.releasemanagement.releasegadgets.release-gadget%'
GROUP BY pp.id, jira.baseurl
ORDER BY "gadget_count" DESC;MySQL
SELECT concat(jira.baseurl, '/secure/Dashboard.jspa?selectPageId=', pp.id) as "dashboard_url",
pp.pagename as "dashboard_name",
pp.username as "dashboard_owner",
count(pc.id) as "gadget_count"
FROM portletconfiguration pc,
portalpage pp,
(select propertyvalue "baseurl"
from propertyentry PE join propertystring PS on PE.id=PS.id
where PE.property_key = 'jira.baseurl') as jira
WHERE pc.portalpage = pp.id
AND pc.gadget_xml LIKE '%app.releasemanagement.releasegadgets.release-gadget%'
GROUP BY pp.id, jira.baseurl
ORDER BY "gadget_count" DESC;Result column / value details
Column | Value |
|---|---|
dashboard_url | dashboard url that can be used for quick access to dashboard in the browser |
dashboard_name | dashboard name |
dashboard_owner | dashboard owner (Jira user name) |
gadget_count | number of gadgets on the dashboard |
List of Release Gadgets that are used across all Dashboards
Postgres
SELECT substring(pc.gadget_xml, 'gadget/gadgets/(.*).xml') as "gadget_type",
count(pc.gadget_xml) as "gadget_count"
FROM portletconfiguration pc,
portalpage pp
WHERE pc.portalpage = pp.id
AND pc.gadget_xml LIKE '%app.releasemanagement.releasegadgets.release-gadget%'
GROUP BY pc.gadget_xml;MySQL
Result column / value details
Column | Value |
|---|---|
gadget_type | Type of gadget:
|
gadget_count | number of gadgets |
Any assistance you might need on the way please contact our support team.
Functionality parity
Please navigate to section of the documentation. “Apps Supported“ column says that all the gadgets are supported for both Server/Datacenter and Cloud versions.
As of Nov 17th, 2023 there is no difference in functionality between the Apps. If we are going to introduce any difference in scope of our future roadmap this will be highlighted in “Apps Supported“ column with a link to specific difference per Gadget.
We suggest to kick off a trial with Cloud solution before you decide to migrate to check all the features you use in Server/Datacenter versions. Any assistance you might need on the way please contact our support team.