Resolved after 54 minutes, affecting Web App, on August 7, 2026.
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.
Affected components
Update timeline
- investigating Aug 07, 2026, 09:02 AM UTC
We are currently investigating this issue.
- investigating Aug 07, 2026, 09:03 AM UTC
We are continuing to investigate this issue.
- 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.
- 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.
Your product runs on more than eazyBI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services