rewindex

CompaniesJiraIncidents

Jira: Automation for Jira rules are not being triggered

MinorStatus: resolvedStarted Resolved (13 h)1 updatejira-software.status.atlassian.com (opens in new tab)

Timeline of updates

  1. resolved

    Between September 30th 12:55 UTC to October 1st 02:00 UTC, we experienced delays processing triggers for Automation for Jira. 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: minor) posted by Jira, started 2020-09-30 14:49 UTC, resolved after 13 h, 1 update(s).

Title
Automation for Jira rules are not being triggered
Vendor
Jira
Date
URL
https://rewindex.com/company/jira/incidents/7tsqjvkldmpr

Jira profileRecent Jira incidentsAll outages on September 30, 2020Jira in September 2020MarkdownJSON