Some Jira dimensions and calculated members removed during Jira Cloud incident

Incident Report for eazyBI

Postmortem

On November 2, 2026, between 00:35 and 02:45 EET, a Jira Cloud incident caused Jira to leave some existing fields out of its responses, including custom fields and Jira Software and Service Management fields such as Sprint, Epic Link, Team, and the SLA fields. eazyBI imports that ran during this time treated these fields as deleted in Jira and removed their dimensions, custom hierarchies, renamed All members, and calculated members across about 900 accounts. The next imports recreated the dimensions but without the data for issues that had not changed since the previous import.

We re-imported the data of the affected accounts, and on November 3 we restored the custom hierarchies, renamed All members, and calculated members from the audit log. The largest accounts, including some with Xray data, took longer, and the last of these accounts finished on November 10.

To prevent this in the future, we are changing the import so it stops with an error instead of removing a field that Jira or an app manages when Jira temporarily does not return it. We will also monitor unusual mass removals across accounts.

Posted Nov 10, 2026 - 15:49 EET

Resolved

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.
Posted Nov 03, 2026 - 17:31 EET

Update

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.
Posted Nov 02, 2026 - 20:01 EET

Update

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.
Posted Nov 02, 2026 - 11:32 EET

Monitoring

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
Posted Nov 02, 2026 - 09:36 EET
This incident affected: Web App.