← Back to Jira History
major✓ Resolved
Job processing and scheduling is degraded affecting multiple Atlassian products
Status
resolved
Duration
4h 59m
Updates
5
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share.
There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.
identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share.
Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.
identified
Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.
identified
Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.
investigating
Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud.
Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.
📊 TECHNICAL DETAILS
Internal ID
27af6860-e2ab-4cf8-9b0f-86834636f933
External ID
vwrp378v0zmk
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
4h 59m
Total Duration
5
Status Updates
Affected Components
NotificationsAutomation for Jira
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed