Some Jira dimensions and calculated members removed during Jira Cloud incident

The data of most affected accounts has been re-imported, and custom hierarchies have been restored. All members rename and calculated members that were removed during the incident have been restored. A few accounts with large data volumes are still finishing their re-import; we will restore them as soon as it completes. If a report still shows missing data or a missing calculated member, please contact eazyBI support.

We are re-importing the data of the affected accounts. About two-thirds of the accounts have finished the data re-import; the larger accounts take longer. The custom hierarchies, renamed All members and calculated members, that were removed during the incident have not yet been restored. We will post an update about restoring them.
Until the recovery is complete, reports that use the affected dimensions may show incomplete data or errors. No action is needed from you.

Our investigation shows that between 22:35 and 00:45 UTC, eazyBI imports removed some Jira dimensions that were not returned to eazyBI because of the Jira Cloud incident, including custom fields, Sprint, Epic Link, Parent Link, Team, Story Points, and Service Management SLA fields. The next import recreated the dimensions, but their historical data is incomplete, and custom hierarchies and calculated members defined on them need to be restored.

We are running full re-imports for the affected accounts and will restore the custom hierarchies and calculated members once each account's re-import completes. No action is needed from you. Reports that use these dimensions may show incomplete data until then. We will post an update when the recovery is complete.

Following an earlier Jira Cloud incident about missing fields on work items, we have identified that some custom field values were not imported into eazyBI for some accounts.
More details about the Jira incident here: https://jira-software.status.atlassian.com/incidents/1blzrf38268l