Jira Platform Incident - viewIssue and createIssue Service Disruption

Update timeline

1. investigating Oct 27, 2025, 04:33 PM UTC

   Impact Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management. Next Steps - The team is investigating and further communications will be provided in 60 minutes.

2. resolved Oct 27, 2025, 05:50 PM UTC

   Between 15:09 UTC to 17:16 UTC, some customers experienced partial outage for Jira Work Management, Jira Service Management, and Jira viewIssue, createIssue and editIssue caused by a faulty code rollout. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The root cause is still being investigated and will be provided in the post incident review. The conditions that cause the errors are being addressed and we're actively working on a permanent fix. The issue has been resolved and the services are operating normally.

3. postmortem Nov 12, 2025, 04:35 AM UTC

   ### Summary On Oct 27, 2025, between 2025-10-27 15:06 UTC and 2025-10-27 17:14 UTC, some Atlassian customers using work item view in Jira and JSM could not access the page and received a "Something went wrong" error message. The issue was caused by a code error in a product update utilising a fast rollout process. The incident was detected within 8 minutes of the update rollout via automated monitoring and was mitigated by reverting the code change, which put Atlassian systems into a known good state. The total time to resolution was 2 hours and 8 minutes. ### **IMPACT** The overall impact was between 2025-10-27 15:06 UTC and 2025-10-27 17:14 UTC on work item view for a subset of users. During this period, affected users experienced full degradation of the page, with a "Something went wrong" error message. ### **ROOT CAUSE** The issue was caused by a code error in a product update that was intended to introduce additional monitoring to track any partial failure to the page requests. The faulty code resulted in the page not rendering, instead of displaying empty data fields, due to partial failures; that, along with the fast rollout process, led to an increased impact. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified because the associated change was related to a very specific kind of legacy case that could not be detected by our automated continuous deployment suites and manual test scripts. We are prioritizing the following improvement actions to avoid this type of incident from occurring in the future: * Additional testing controls during the code development process. * Enhanced monitoring to detect regressions earlier during a release. * Improvements to deployment automations to reduce the risk of similar incidents in the future. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian Customer Support