Update - We have successfully restored the majority of automation rules that were affected, but we are currently in the process of manually fixing the remaining ones. Our support team will be contacting the customers impacted by this issue to proceed with resolving their cases.
Mar 01, 2024 - 14:52 UTC
Update - This issue has been mitigated, and we have restored the majority of automation rules that were affected. Those rules are working as normal, including the rules that had not been modified in the last 48 hours and the rules created after the incident. The remaining rules that haven't yet been restored are cases where customers have manually updated the rules after the incident happened.
We are proceeding with caution to avoid overwriting these changes.

Mar 01, 2024 - 03:18 UTC
Update - We are continuing to work on a fix for this issue.
Feb 29, 2024 - 17:45 UTC
Update - We are continuously working on restoring the affected automation rules configuration data. At the moment the majority of the impact has already been mitigated and the team is currently focusing on a few specific outstanding scenarios. We will continue to update you as we progress.
Feb 29, 2024 - 17:30 UTC
Update - We are currently working on restoring the lost automation rules configuration data. The email notifications related to the automation will be addressed upon restoring the lost data. Customers can update the configurations with the Automation rules themselves, and our fix will not override those changes. We will share further updates as we progress.
Feb 29, 2024 - 15:20 UTC
Identified - We have identified the root cause and we are currently working on deploying fix to restore any lost configuration/rules. Next update will be provided in an hour.
Feb 29, 2024 - 10:54 UTC
Update - We continue to investigate the issue with the Automation rules losing configuration data that is impacting certain cloud products. We are actively working to resolve this issue as quickly as possible.
Feb 29, 2024 - 09:23 UTC
Investigating - We are investigating an issue with the Automation rules losing configuration data that is impacting some of the Cloud products. We are actively working to resolve this issue as quickly as possible.
Feb 29, 2024 - 08:23 UTC

About This Site

Here we will post updates about Jira Work Management's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

Viewing content ? Operational
Create and edit ? Operational
Authentication and User Management Operational
Search ? Operational
Notifications ? Operational
Administration ? Operational
Marketplace ? Operational
Mobile ? Operational
Purchasing & Licensing Operational
Signup Operational
Automation for Jira Partial Outage
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Mar 1, 2024

Unresolved incident: Configuration data discrepancies in automation rules.

Feb 29, 2024
Resolved - Between 28th Feb 2024 23:15 UTC to 29th Feb 2024 00:05 UTC, we experienced issue with new product purchasing for all products. All new sign up products have been successfully provision and confirmed issue has been resolved and the service is operating normally.
Feb 29, 02:53 UTC
Investigating - We are investigating an issue with new product purchasing that is impacting for all products. Customers adding new cloud products may have experienced a long waiting page or an error page after attempting to add a product. We have mitigated the root cause and are working to resolve impact for customers who attempted to add a product during the impact period. We will provide more details within the next hour.
Feb 29, 01:27 UTC
Feb 28, 2024
Resolved - On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user-impersonation operations and failed to execute. This had a widespread impact on all product extensions based on the Connect platform resulting in failure when performing actions on behalf of a user.

Jira Cloud Automation rules that triggered during the outage may have failed to run. Those rules will not be able to be replayed by customers or Atlassian. Our support engineers have details regarding which customers and automation rules that were impacted. However, support engineers will not be able to replay the failed automation rules.

We have identified the root cause of the fault and have resolved it by scaling up the infrastructure. The incident is now resolved.

If you have questions or require support - please reach out at https://support.atlassian.com/contact/.

We apologise to all of our developers, customers and users who were impacted during this time.

We will release a public incident review (PIR) here in the upcoming weeks. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.

Feb 28, 17:17 UTC
Identified - Starting from 13:15 UTC, Automation and Connect Apps affecting certain cloud products

We have scaled up the underlying services and we're seeing an improvement in response times and success rates. We continue to investigate the root cause and will provide the next update by 18:00 UTC.

Feb 28, 16:25 UTC
Update - We continue to investigate the issue with the Automation and Connect Apps affecting certain cloud products. We are actively working to resolve this issue as quickly as possible.
Feb 28, 15:13 UTC
Investigating - We are investigating an issue with Automation and Connect Apps that is impacting some Cloud products. We will provide more details within the next hour.
Feb 28, 13:45 UTC
Feb 27, 2024

No incidents reported.

Feb 26, 2024

No incidents reported.

Feb 25, 2024

No incidents reported.

Feb 24, 2024

No incidents reported.

Feb 23, 2024

No incidents reported.

Feb 22, 2024

No incidents reported.

Feb 21, 2024
Postmortem - Read details
Mar 1, 08:25 UTC
Resolved - Between 2:30 UTC to 4:26 UTC, we experienced increased authentication errors for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.
Feb 21, 04:57 UTC
Monitoring - We have identified the root cause of the authentication errors and have mitigated the problem. We are now monitoring this closely and will provide further updates within the hour.
Feb 21, 04:22 UTC
Update - We are continuing to investigate this issue.
Feb 21, 04:05 UTC
Investigating - We are investigating authentication issues impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.
Feb 21, 03:41 UTC
Feb 20, 2024
Resolved - Between 04:33 UTC to 13:10 UTC, we experienced intermittent 503 errors for Jira Software, Jira service management and Jira work management. The issue has been resolved and the service is operating normally.
Feb 20, 13:15 UTC
Investigating - We are investigating reports of intermittent 503 errors for Jira Work Management, Jira Software and Jira Service Management Cloud customers. We will provide more details once we identify the root cause
Feb 20, 12:51 UTC
Feb 19, 2024

No incidents reported.

Feb 18, 2024

No incidents reported.

Feb 17, 2024

No incidents reported.

Feb 16, 2024

No incidents reported.