Provider
JiraIncident detail
Duplicate issues being created in Jira Service Management and Jira
Timeline window
to
Get alerted the next time Jira breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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.
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.
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
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.
Resolved
Our team has completed restoration of customer environments for the vast majority of those impacted by this issue. We will continue working with the final impacted customers to ensure we reach a full resolution.
If you are still experiencing any issues relating to these duplicate issues being created we encourage you to reach out to our support team who will assist with completing any additional tasks that are remaining.
Keep exploring
More from Jira
Neighboring incidents on Jira's timeline and the rest of their record on OutageDeck.