Server/DC to Cloud Manual Migration

If you are a Timepiece by OBSS user and planning to migrate from Jira Server/DC to Jira Cloud, you should know the following:

Migrating Data

Timepiece prepares its reports based on Jira issue histories. Jira issues and their histories will be migrated as part of your base Jira migration. You won't need to take additional steps about issue migration regarding Timepiece.

Timepiece itself does not store your data but it has a few app-specific settings. Settings like param sets, permissions, calendar definitions, and gadget definitions.

An automated migration path is available via Jira Cloud Migration Assistant (JCMA). This process allows for the automatic migration of Timepiece configuration data such as calendars, format settings, access settings, and saved parameter sets.

For detailed instructions, please refer to the migration documentation: Server/DC to Cloud Migration with JCMA

Note on JCMA Migration and Issue Histories

There was a known bug in JCMA (described in MIG-1032) that caused outdated object IDs in issue histories during Cloud migrations. This issue could lead to inconsistencies in status-based Timepiece reports for issues created before the migration.

Atlassian resolved this bug starting with Jira Cloud Migration Assistant (JCMA) version 1.7.3, released on September 12th, 2022. However, if your Jira Cloud site was migrated before this date, your instance may still be affected. Unfortunately, this data corruption is introduced during the migration process and is outside Timepiece’s control.

We recommend checking your migration timeline. If your migration occurred before the fix, please contact Atlassian Support for further assistance.

Manual Migration Checklist

Timepiece has its own Calendar, Format, Access Permission settings.
- Admin pages for these settings can be found in Timepiece Admin pages (under Jira admin section).
- You can manually copy these configurations to a Jira Cloud instance through Jira Admin UI.
Timepiece users might have saved some Parameter Sets.
- From Timepiece UI, each user can see his/her own param sets and the ones that are saved as public.
- There is no way to automatically or manually move this to the cloud environment since there is no admin UI for them.
- They are kept in AO_956E29_REPORT_SETTINGS table in Jira DB. In the DB table, you can at least see which users have saved param sets.
- CODE
```
select s.username, s.* 
from AO_956E29_REPORT_SETTINGS s;

-- The username column contains the name of the user who created this param set.

-- This is a query built for MySQL. If you are using a different DBMS, you will need to change this query accordingly.
```
- Cloud users will need to re-create them.

Timepiece users might have used Gadgets on their dashboards.

The gadgets and their configuration are saved by Jira.
Timepiece doesn't keep any data about them in its DB tables. You can use the following query to see which users have dashboards with Timepiece gadgets.

Query

SQL

select 
dashboard.id                        as dashboard_Id,       
dashboard.pagename                  as Dashboard_Name,       
users.id                            as user_id,       
users.lower_user_name               as user_name,       
gadget.id                           as Gadget_Id
from portalpage as dashboard
         join portletconfiguration as gadget on gadget.portalpage = dashboard.id
         join app_user as users on users.user_key = dashboard.username
where gadget.gadget_xml = 'rest/gadgets/1.0/g/com.obss.plugin.time-in-status:tis-gadget/tis-gadget.xml';

-- This is a query built for MySQL. If you are using a different DBMS, you will need to change this query accordingly.

The gadgets will also need to be manually re-created on the cloud instance.

There might be an integration built via Timepiece REST API to get Timepiece data from Jira (for custom reporting, BI integration, etc).
- Timepiece Cloud also has a similar REST API but the nuts and bolts are slightly different so if there is an integration, it will need to be re-visited for Jira Cloud.

Feature Compatibility

Please see Server/DC and Cloud Feature Comparison document about feature comparison between Timepiece Server/DC and Cloud.

Licenses

All sales and licensing operations for apps are handled by Atlassian directly. You can browse Atlassian website or contact Atlassian support directly to get information about app licensing when migrating to Cloud.

https://www.atlassian.com/

https://support.atlassian.com/contact/

Repeated Migrations

If you import your data to your Jira Cloud instance multiple times and install Timepiece multiple times, there is a slight chance that you might get errors after the second import/install. That is because your second import overwrites all instance data (including apps) and during the second install of Timepiece, the instance tries to register itself to our service as a clean install. That sometimes causes an error.

If you get errors during repeated imports to the cloud, you can reach us through our support channels below. We will remove your registration manually and you will be able to install the app without a problem.

Support

For any more questions or support requests, please reach us through https://appsupport.obss.tech/ or send an e-mail to appsupport@obss.tech.