Jira Status

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.

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.

Identified: 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.

Identified: 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.

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.

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.

Resolved: Duplicated message. Please refer to the updates from this incident: https://jira-software.status.atlassian.com/incidents/knx11cj542ks

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.

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.

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.

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.

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.

Identified: 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.

Identified: 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.

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.

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.

Monitoring: 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.

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.

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.

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.

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.

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.

Investigating: 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.

Investigating: 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.

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.