Duplicate issues being created in Jira Service Management and Jira
Incident
Report for Jira Service Management
Subscribe to Updates
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.
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.
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.
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.
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.
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.
Update
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.
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.
Update
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.
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.
Update
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.
The team is working on identifying and taking actions to mitigate the issue and minimize the impact.
This incident affects: Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow, Opsgenie Incident Flow, Opsgenie Alert Flow, Jira Service Management Email Requests, Authentication and User Management, Purchasing & Licensing, Signup, Automation for Jira, and Assist.