Job processing and scheduling is degraded affecting multiple Atlassian products
Incident
Report for Jira Service Management
Subscribe to Updates
Update
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.
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.
Update
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.
Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.
This incident affects: Jira Service Management Email Requests and Automation for Jira.