Jira: Association to OpsGenie in Jira
Timeline of updates
- resolved
Between 2020-11-03 11:04 AM UTC to 2020-11-06 05:05 AM UTC, some customers experienced an issue related to Code and OpsGenie schedule features in Jira. The root cause was an error in a code path that caused configuration data to be deleted. We immediately deployed a fix to mitigate the issue and have verified that this will not happen again. The conditions that caused the bug have been addressed and we have restored all data that was erroneously deleted. The issue has been resolved and the service is operating normally.
From Jira’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Jira, started 2020-11-04 07:18 UTC, resolved after 46 h, 1 update(s).
- Title
- Association to OpsGenie in Jira
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/5wtbhhjkvc7d
Jira profileRecent Jira incidentsAll outages on November 4, 2020Jira in November 2020MarkdownJSON