Skip to content
OutageDeck

Incident detail

Duplicate issues being created in Jira Service Management and Jira

Duplicate issues being created in Jira Service Management and Jira

Resolved incidentMajor1 affected service

Timeline window

to

Sponsored placement

Google AdSense placeholder

This slot is reserved for future AdSense placement. It stays as a non-invasive placeholder until a client ID and slot ID are configured.

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.