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.