Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Our team has identified the issue causing problems with Assets loading within JSM and Jira and applied a fix. Assets are now functioning as expected across our products.

We have confirmed that this issue is now resolved.

Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

Between 00:13 UTC to 10:00 UTC, on 21st March, we experienced provisioning failures for Jira Service Management. During this time, customers were unable to add/update their Assets in JSM. The issue has been resolved and the service is operating normally.

On February 26, 2025 14:45 UTC a temporary Slack outage began which affected JSM automations within Slack. On February 27, 2025 08:05 UTC we observed new Slack events being processed within JSM successfully. We have confirmed with the Slack team that this outage is resolved. Slack has advised on their Status page that they do not plan to replay events that were buffered from this incident. For more information on Slack’s update please refer to Slack's status page: https://slack-status.com/2025-02/1b757d1d0f444c34 If you have any further questions please contact our support team.

This incident has been resolved.

The issue with Jira Service Management Assets has been resolved, and the service is now functioning normally.