We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.
We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.
We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.
Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.
We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with