This page explains the migration support details for the Power BI Jira Connector app data from the Data Center to the cloud.
...
Install (and configure) the Power BI Jira Connector app.
Use the supported integrations on the cloud after migration: If you are using any of the supported integrations in the Data Center and plan to use them on the cloud, then install the required applications on the cloud.
Assets (formerly known as Insight):
Assets is Jira Service Management’s native asset and configuration management tool. To use Assets for the Jira Cloud, install the Jira Service Management Cloud Premium or Enterprise. For more information, refer toAssets in Jira Service Management.
Create a new custom field with the name Assets. For more information, refer to Insight (now Assets) Integration.
Make sure the user who will use the Assets configuration on the Power BI Jira Connector has access to the Jira Service Management.
Projectrak Integration: To use project fields, install Projectrak ( project tracking solution for Jira) on your cloud instance. For more information, refer to Projectrak Integration.
Tempo Timesheets: To use Tempo Timesheets, install Tempo Timesheets on your cloud instance. For more information, refer to Tempo Timesheets.
...
Entity | Field configurations not checked for Connectors after migration |
|---|---|
Dates |
|
Epic |
|
Portfolio | Parent Link |
Custom |
|
Tempo | Account |
Service Desk |
|
...
Under Sprint Metrics, the Data Center Board configuration is not updated for Connectors in the cloud.
To update the Board relevant to the cloud, edit the migrated Connector in the cloud, select the Board, and Save the Connector.
AQL for Insight (Asset) Objects: The AQL defined for the Insight object in the Data Center is not migrated to the cloud.
To update the query, edit the Connector in the cloud, input the AQL for Insight (Asset) Objects, and Save the Connector.
Jira Importers custom field - ${field_Story_Points}: If any of the Data Center Connectors are configured with the custom field ${field_Story_Points}, then after migration, you will encounter an error for those specific Connectors data extraction.
Resolution (before migration): Before migrating to the cloud, edit the Connector that includes the custom field ${field_Story_Points} configuration in the Data Center, uncheck the custom field ${field_Story_Points}, and Save the Connector.
| Info |
|---|
The field ${field_Story_Points} is added by JIM when a project is created in the Data Center. JIRA Importers (JIM) add-on enables administrators to import issues from external issue trackers into JIRA. |
We are currently addressing the known issues to ensure migration support in upcoming releases.
...