Jira Service Management Status

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: We've rolled out a fix, and Organizations page is back to normal operations now.

Monitoring: Impact

Customers using Jira Service Management are currently experiencing issues when attempting to access the Organizations tab. They encounter an error message. This affects the usability of this feature within the product.

Current Status

We've rolled out the fix and are monitoring the impact. We are seeing a reduction in errors.

Next Steps

We'll provide an update once we've verified the fix.

Identified: Impact

Customers using Jira Service Management are currently experiencing issues when attempting to access the Organizations tab. They encounter an error message. This affects the usability of this feature within the product.

Current Status

Our teams have successfully reproduced the issue and have identified the fix.

Next Steps We will start rolling out the fix soon.

Investigating: We are investigating reports of intermittent errors on Jira Service Management Cloud customers' Organizations page. Once we identify the root cause, we will provide more details.

Resolved: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

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

Identified: The issue has been identified and a fix is being implemented.

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

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: 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: 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 work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.

Monitoring: We are continuing to monitor for any further 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.

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: A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

Monitoring: Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

Identified: Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

Identified: Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.