All eazyBI for Jira eazyBI for Confluence Private eazyBI

Troubleshooting eazyBI migration

This page provides guidance on addressing the most common problem situations that may arise during the migration process. Migration steps are described in the database migrator.

The main root cause of these issues is inconsistency between the source and target environments. In some cases, this is inevitable; data and configuration cleanup is performed, or fields, objects, and user permissions are refined or renamed.

Always read error and warning messages carefully, as they usually indicate the cause and suggest how to resolve it.

Missing or No Data in Reports

Reports show no data after migration despite having the same configuration.

This occurs because only the configuration and report definitions are migrated, not the actual source data. Data must be manually imported from all source applications.

Solution

Go to Source Data and press Import to import data for the first time. After the first successful import, the following imports will be automatically scheduled according to the import schedule for this account.

If data import failed, read the error messages. The message will indicate the cause of the failure, so you can act upon it and restore data import.

Data from additional data sources is missing after migration

Data from source files and source applications is not migrated with the eazyBI migration tool. The database migration transfers configuration only, not the data. First time after migration, data must be manually imported from all source applications

Solution

  1. Source file - Uploaded source files (CSV, Excel, etc.) are not migrated. These files need to be re-uploaded in the Source Data tab and data re-imported from all source files.
  2. Source application - update authorisation details and press import. For REST API and SQL data sources, additionally check if IP addresses of the source system are available from eazybi.com

User not found or no permissions

During the migration process, eazyBI displays a warning if some authorized users are not found or lack sufficient permissions in Jira. For example:

  • Cannot find user "be899a36-aaa5-3e4f-b8da-5456b8d1cd10@atlassian_cloud".

  • The Jira user 'Anna Linda' does not have the 'Browse Projects' permission for the project 'Demo Alpha (DA)'.

Those errors and warnings are repeated during data imports in the new environment until they are resolved.

Solution

First, review the user and their permissions in Jira (new environment). If applicable, update the user permission in Jira to access the needed data. 

Or assign a new user to the account with Owner, User Admin, or Data Admin account user roles in eazyBI. The user should log in to eazyBI, open the Source Data tab, click Reset authorization, and then run the import.

Report failing because the measure or dimension is not present in the cube

Opening the report or dashboard, you may get an error indication that some measure or dimension is missing in the cube.

It means that the mentioned field is not imported into eazyBI for one of the following reasons, and the solution varies for each of them.

Solution

First, try to restore and import the missing data that is required by your reports.

Custom field not found or is duplicated 

During data import, you may see a warning indicating that the custom field is not available on the target instance. For example, "Cannot find custom field "Business domain (customfield_10196)".

You may also get an error indication that some measure or dimension is missing when opening a report or a dashboard. For example, "Report definition contains row dimension "Business domain" which is not present in the cube."

Those errors indicate that during data migration, eazyBI could not find the custom field and import it into the cube. During migration, the custom field may change ID; therefore, eazyBI maps custom fields based on their name and data type. The reason for not finding the custom field:

  • The custom field name has been changed. Note that custom field names are case sensitive in eazyBI.
  • The custom field is no longer present in the target environment. This may be the case with Jira calculated and scripted custom fields. 
  • The data type of the custom field has changed and is different in the target instance.

Solution

If a custom field can’t be found, update references manually in your target environment

Check the site settings for custom fields and JavaScript-calculated fields.

Check custom fields in the import options.

Next, update each of the failing reports.

  1. Open a report.
  2. Check if you can replace the missing field with another or a user report that does not require it.
  3. Save the changes to the report to overwrite the report.
  4. If fixing the report is not possible, consider deleting it or converting it to a private report so that other users cannot publish it.

Data from 3rd-party or Jira apps not imported

Opening the report or dashboard, you may get an error indication that some measure or dimension is missing. For example, "Report definition contains row dimension "QMetry Test Case Type" which is not present in the cube.

This indicates that data from 3rd-party or Jira apps are not imported into the target instance.

Solution

First, try to get the data. Edit the import option to import data from a 3rd-partyor Jira apps (Assets, Plans, and JSM). 

  • Go through all tabs (General, Add-ons, and Custom fields) and select the custom fields required for reports.
  • The 3rd party app requires authorization to import data. Depending on the integration, you should either press 'Authorize' or provide a new secure API token from the app; details and informative links are provided in the import options. 

If importing required data fields are not possible, then you should review and remake each of the failing reports.

  1. Open a report.
  2. Check if you can replace the missing field with another or a user report that does not require it.
  3. Save the changes to the report to overwrite the report.
  4. If fixing the report is not possible, consider deleting it or converting it to a private report so that other users cannot publish it.

Report definition errors

Reports show an error about missing dimensions and measures, for example:

  • "Report definition contains a measure which is not defined."
  • "Report definition contains a dimension which is not present in the cube"

This occurs when a measure or dimension used in a report is not imported into the data cube.

Solution

Check custom fields in the import options and consider importing missing fields or updating the report by removing failing measures. See also the Custom field not found or is duplicated chapter.

The calculated member formula is not valid

eazyBI shows a warning "Calculated member formula is not valid" at the top of the report or dashboard about missing dimensions and measures. Warning lists all failing member names, and they are marked with a red frame in the Measures.

This occurs when a dimension member or measure used in a report calculation is not imported.

Solution

Check the custom fields in the import options, and consider either importing missing fields or updating the calculations. See also the Custom field not found or is duplicated chapter. 

Jira gadgets and Confluence macros don't show eazyBI reports after migration

eazyBI gadgets in Confluence pages and Jira dashboards are not migrated automatically due to Atlassian platform limitations. 

Dashboard gadgets and Confluence macros won't have the same parameters after the migration, hence previously added eazyBI gadgets won't work.

Solution

You’ll need to re-add gadgets and macros manually after migration. 

You can query the Jira or Confluence database to find Jira dashboards and Confluence pages that use eazyBI reports or dashboards. 

See also