eazyBI incident

Errors when opening Jira import settings

Minor Resolved View vendor source →

eazyBI experienced a minor incident on August 7, 2026 affecting Web App, lasting 54m. The incident has been resolved; the full update timeline is below.

Started
Aug 07, 2026, 09:02 AM UTC
Resolved
Aug 07, 2026, 09:57 AM UTC
Duration
54m
Detected by Pingoru
Aug 07, 2026, 09:02 AM UTC

Affected components

Web App

Update timeline

  1. investigating Aug 07, 2026, 09:02 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 07, 2026, 09:03 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 07, 2026, 09:57 AM UTC

    This issue has been resolved. The Jira import settings screen loads normally again. No data was lost, and imports were not interrupted.

  4. postmortem Aug 07, 2026, 10:05 AM UTC

    Opening the Jira source data import settings page returned a 500 error. A DWH table existence check, added as part of performance improvements, was performed during schema definition without a checked-out DWH connection. Cloud accounts opening Jira source data settings were affected while imports, reports, and dashboard viewing were not. No data loss or data corruption.