← Back to Jira History
minor✓ Resolved
Degraded performance of Jira Automation rules
Status
resolved
Duration
1h 21m
Updates
2
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedMon, Jul 20, 2026, 05:25 PM
This incident has been resolved.
identifiedMon, Jul 20, 2026, 04:58 PM
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are currently seeing signs of improvements, however, affected users may experience delays in Jira and Jira Service management Automation rule executions.
We'll continue to share additional updates here as more information is available.
investigatingMon, Jul 20, 2026, 04:03 PM
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
📊 TECHNICAL DETAILS
Internal ID
7f097816-75f3-47d0-956d-855dc2552ae4
External ID
4wxvsr6lwth5
🕐 Started
Mon, Jul 20, 2026, 04:03 PM
🔄 Last Updated
Mon, Jul 20, 2026, 05:25 PM
✓ Resolved
Mon, Jul 20, 2026, 05:25 PM
MINOR
Impact Level
1h 21m
Total Duration
2
Status Updates
Affected Components
Automation for Jira
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed