Duplicate issues being created in Jira Service Management and Jira
Update - Affected customers who have Tempo installed; the script will be delayed as we await confirmation from Tempo on next steps.

For other affected customers, Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 17, 2025 - 13:36 UTC
Update - Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 15, 2025 - 09:11 UTC
Monitoring - Root cause of the issue was identified to a code change. To fix the issue, we have reverted the code change and we expect the behaviour to be back to normal.

Atlassian team is working on creating steps or a script to remove the duplicate issues created. We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 11, 2025 - 16:07 UTC
Identified - We continue to work on resolving the cause of the duplicate issue creation in Jira Service Management and Jira. We have identified the root cause and expect recovery shortly.
Sep 11, 2025 - 10:30 UTC
Investigating - We are investigating the issue of duplicate issues being created in Jira Service Management and Jira.

The team is working on identifying and taking actions to mitigate the issue and minimize the impact.
Sep 11, 2025 - 09:39 UTC

About This Site

Here we will post updates about Jira'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 ? Degraded Performance
Mobile ? Operational
Purchasing & Licensing Operational
Signup Operational
Automation for Jira Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Sep 17, 2025

Unresolved incident: Duplicate issues being created in Jira Service Management and Jira.

Sep 16, 2025
Xray Testing board fails to load
Resolved - Xray team after deep dive on their end have confirmed to Atlassian that the cause of the this issue is at their end and they are working on fixing the same.

With this update from Xray team, Atlassian is considering this issue closed since there is no issue at Atlassian end.
Sep 16, 15:17 UTC
Identified - Xray team after deep dive on their end have confirmed to Atlassian that the cause of the this issue is at their end and they are working on fixing the same.
Sep 16, 15:13 UTC
Update - We have not identified any changes on the Atlassian side that would have caused this issue as of now. We are working with The XRay team to identify the root cause of the issue.

Next Steps
We are in contact with the XRay team and continuing to investigate and monitor the situation. We will share updates here as more information becomes available.
Sep 16, 12:25 UTC
Update - We have not identified any changes on the Atlassian side that would have caused this issue as of now. We are working with The XRay team to identify the root cause of the issue.

Next Steps
We are in contact with the XRay team and continuing to investigate and monitor the situation. We will share updates here as more information becomes available.
Sep 16, 12:24 UTC
Investigating - Jira users are experiencing an issue where the Xray Testing board fails to load when accessed, resulting in an error. This disruption may cause temporary inconvenience in accessing certain functionalities associated with the Xray Testing board.

Atlassian team has reached out to the Xray team to align on the next steps towards investigation and resolution.
Sep 16, 09:51 UTC
Sep 15, 2025
Degraded performance in Confluence and Jira for Microsoft Edge users
Resolved - An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections List', ensuring that you are on version 1.0.0.31 or higher to ensure you are running the version that contains the fixed release.
All Edge browsers should otherwise receive this update within 10 hours without user intervention.
Sep 15, 06:40 UTC
Monitoring - We have identified the root cause of the Microsoft Edge 140 tracking prevention issue and have mitigated the problem and we continue monitoring closely. The issue has been mitigated however it will not be considered resolved until Microsoft issues an updated version of the Edge browser scheduled for September 18th. This will be the last update until the issue is resolved.
Sep 10, 20:34 UTC
Update - We continue to work on resolving the Microsoft Edge 140 tracking prevention issue for Confluence, Jira Work Management, Jira Service Management, Jira, Jira Align, and Jira Product Discovery. We have identified the root cause and are working on solutions for each product. We will provide the next update within three hours.
Sep 10, 18:35 UTC
Update - Our team is aware that the incorrect classification of Atlassian sites as advertising has been resolved, however these changes will take some time to propagate out to users since we are waiting for Edge from Microsoft to incorporate the changes.

We are continuing to monitor the situation and will provide further update when we are able to confirm that the issue is resolved.
Sep 10, 00:55 UTC
Identified - Important Update on Attachment Issues with Edge 140 and Atlassian Products

We've identified an issue affecting images, media, and Whiteboards in Confluence and Jira for users who have upgraded to Microsoft Edge version 140.0.3485.54 with Strict tracking prevention enabled. These settings can block media (images and videos) content from loading, uploading, or opening.

The issue is triggered by Edge's Strict tracking prevention incorrectly classifying Atlassian as advertising, impacting functionality.

Recommended Workarounds:
- Switch your tracking prevention settings from 'Strict' to the 'Balanced (Recommended)' mode in Edge.
- Alternatively, add an 'Exception' for the URL you use to access Atlassian products.
- Use a different browser, such as Chrome, Firefox, or Safari.

This issue only affects Microsoft Edge. Other browsers are not affected by this issue.
Thank you for your patience as we work through this issue. We'll provide updates as they become available.
Sep 9, 11:40 UTC
Investigating - We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.
Sep 9, 10:23 UTC
Sep 14, 2025

No incidents reported.

Sep 13, 2025

No incidents reported.

Sep 12, 2025

No incidents reported.

Sep 11, 2025
Duplicate issues being created in Jira Service Management and Jira
Resolved - Duplicated message. Please refer to the updates from this incident: https://jira-software.status.atlassian.com/incidents/knx11cj542ks
Sep 11, 09:45 UTC
Investigating - We are investigating the issue of duplicate issues being created in Jira Service Management and Jira.
The team is working on identifying and taking actions to mitigate the issue and minimize the impact.
Sep 11, 09:41 UTC
Sep 10, 2025
Sep 9, 2025
Disappearing 'account' field for Tempo users
Resolved - Our team is now satisfied that the issues relating to these missing fields are now resolved.
Sep 9, 00:40 UTC
Monitoring - Our team has identified the root cause of this issue and has now put a fix in place to resolve this issue. We are continuing to monitor the situation and will provide further updates as available.
Sep 8, 23:59 UTC
Update - We are continuing to investigate this issue
Sep 8, 17:22 UTC
Update - All affected fields originate from Tempo(Vendor), we are consulting it now with them.
Sep 8, 12:45 UTC
Investigating - We are investigating cases of disappearing 'account' while trying to edit it. Account field is Tempo(Vendor) field. We are investigating the case and provide further informations
Sep 8, 10:50 UTC
Sep 8, 2025
Users receiving 'something went wrong' or 'Hash MHHY91' Error messages when using Apps
Resolved - Our team has continued to monitor the errors relating to accessing Apps and we are now satisfied that this issue is fully resolved.
Sep 8, 05:49 UTC
Monitoring - We have implemented a mitigation for the issue affecting access to 3rd party Apps. At this time, services are operating as expected and we are closely monitoring the situation to ensure continued stability. We will provide further updates if there are any changes.
Sep 4, 15:11 UTC
Identified - We have identified the issue that might happen after multiple page refreshes. A temporary workaround for users is to avoid performing a full page refresh; instead, try switching between different tabs within the interface to reload third-party applications. Our team is actively working on fixing this issue and will provide updates as soon as more information becomes available.
Sep 4, 07:45 UTC
Update - Our team is continuing to investigate this issue. We will provide further updates when available.
Sep 4, 05:02 UTC
Investigating - We are aware of some users currently receiving error messages such as 'something went wrong' or 'Hash MHHY91' when attempting to access 3rd party Apps. Our team is investigating with urgency and we will provide an update as soon as possible.
Sep 4, 00:53 UTC
Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

Sep 4, 2025
Sep 3, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage