The Work Item view experience of Jira is restored

SUMMARY

Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work item fields was degraded for both products. Navigating to and interacting with boards were degraded for Jira specifically. On Jira mobile, users were unable to view work items and work item search was degraded. This was caused by a deployment of a schema configuration change that had only been validated against some production environments.

The issue also affected Atlassian's customer support operations and temporarily impacted Atlassian’s ability to respond to incoming support requests. Customers were able to raise tickets as usual.

Atlassian’s automated monitoring systems detected the issue on May 1, 2026 at 23:41 UTC, and engineering teams promptly began investigating.

The issue was reported on Statuspage on May 2, 2026 at 00:55 UTC.

The issue was resolved after 3 hours and 19 minutes on May 2, 2026 at 02:53 UTC when the previous version of the schema configuration was successfully redeployed to all regions.

IMPACT

• Duration: 3 hours 19 minutes (May 1, 2026 at 23:34 UTC – May 2, 2026 at 02:53 UTC)
• Affected regions: All regions.
• Affected products: Jira, JSM, Jira Mobile
• Customer experience:
• Users were unable to view work items using the work item view; consequently updating and creating work items from the work item view was affected.
• Editing work items was degraded.
• Boards did not show under Spaces in the Jira navigation.
• Certain board interactions were affected.
• Other areas of Jira not dependent on the broken schema configuration continued to operate normally.

ROOT CAUSE

The root cause was a deployment sequencing issue. A schema configuration change was deployed to the API gateway layer before the corresponding application-level change had been deployed across all production environments. This created a mismatch between the schema expected by the gateway and the schema served by the application servers.

MITIGATIONS

The engineering team identified the problematic schema change and initiated a rollback of the deployment. A deployment blocker was put in place to prevent further changes while the rollback was executed. The previous version of the schema configuration was redeployed, and service was restored across all regions.

REMEDIAL ACTION PLAN & NEXT STEPS

We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur:

• We are adding automated pre-deployment checks to verify that schema configurations are compatible across all production environments before changes are deployed.
• We will streamline our incident communication processes, incident response training and tooling to reduce the time between incident detection and customer notification.
• We are working to improve resilience of critical customer-facing support services to ensure SLA continuity during outages.

We apologize to customers whose services were impacted during this incident. We are taking immediate steps to reduce the risk and impact of similar issues in future.

Thanks,

Atlassian