Server/DC to Cloud Migration with JCMA
Timepiece is fully compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA). This means your Timepiece configuration and data can be migrated from Data Center to Cloud automatically using JCMA.
Timepiece enables advanced historical reporting by analyzing Jira issue histories in detail. To ensure accurate and consistent results, it is critical that issue data and history are migrated reliably.
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.
What is Migrated?
The following components are included in the automated Timepiece migration via JCMA:
Access Settings
Format Settings
Calendars
Saved Parameter Sets
Access Settings
Group-based access settings of Timepiece defined in the Data Center environment are migrated to the Cloud.
⚠️If a group from the original access settings does not exist in the Cloud environment, the data will still be migrated, but a warning will be logged in the Timepiece migration log indicating the missing group.
Format Settings
Date format and date-time format configured in Timepiece are included in the migration.
Calendars
All custom calendars configured in Timepiece are fully migrated to the Cloud environment. During migration, all calendar definitions (working days, hours, breaks, holidays) and their associated time zone settings are preserved to ensure continuity in report results.
Saved Parameter Sets
Saved report configurations (report type, filters, groupings, columns, calendar settings, etc.) are migrated in bulk.
⚠️ If a saved parameter set includes projects that are not migrated to the Cloud, those parameter sets will be migrated but reports using those sets may not load successfully.
⚠️ If the user who owns a parameter set does not exist in the Cloud environment, the owner field will be empty in Cloud.
🔍 These issues are logged in detail in the Timepiece migration log file. Please review this log after migration.You may see similar messages in your log file for unmapped status, project, user, or group values. These indicate that some field values from the Data Center environment could not be resolved in the Cloud instance, but the parameter set will still be migrated with the original values.
Repeated Migrations & Overriding Behavior
If you perform multiple migrations from the same Data Center instance to the same Jira Cloud site using JCMA, the following Timepiece configuration components will be overwritten during each migration:
What gets overridden?
Component | Override Behavior |
|---|---|
Access Settings | Always fully overwritten by the latest version from Data Center |
Format Settings | Always fully overwritten by the latest version from Data Center |
Calendars | Overwritten only if a calendar with the same name exists in Cloud |
Saved Parameter Sets | Overwritten only if a saved set with the same name exists in Cloud |
If a calendar or saved parameter set already exists in the Cloud with the same name as the one being migrated from Data Center, it will be overwritten, even if the item in Cloud was manually created and not migrated previously.
⚠️ Important Note: Timepiece treats items with matching names as equivalent — regardless of whether they were originally migrated or manually created in the Cloud.
As a result, manually created Cloud items may be unintentionally overridden if they share a name with an item from the Data Center source.
This mechanism ensures consistency, but we recommend reviewing Cloud configurations before repeating a migration to avoid overwriting manually created content.
Dashboard gadgets are not migrated
Currently, JCMA does not support the migration of app-specific dashboard gadgets. As a result, Timepiece dashboard gadgets and their configurations will not be migrated.