Resolved -
We haven't seen any more attachment cloning errors since deploying the workaround and thus resolve this incident.
We will continue to work with Atlassian support to understand and fix the root cause of this issue.
Dec 8, 15:27 UTC
Monitoring -
We have implemented a temporary workaround for this issue. Cloning attachments should be possible again. We are monitoring this issue to verify that no further errors occur with this workaround in place.
We will also continue to work with Atlassian support to understand and fix the root cause of this issue.
Dec 8, 13:35 UTC
Update -
We identified a call to an Atlassian REST API that returns unexpected error responses for a subset of clients. Atlassian support is investigating.
Dec 5, 16:10 UTC
Update -
We identified a call to an Atlassian REST API that returns unexpected error responses for a subset of clients. We are still waiting for clarification from Atlassian support.
Dec 5, 15:16 UTC
Update -
We identified a call to an Atlassian REST API that returns unexpected error responses for a subset of clients. We are still waiting for a reaction from Atlassian support.
Dec 4, 15:44 UTC
Update -
We identified a call to an Atlassian REST API that returns unexpected error responses for a subset of clients. We are waiting for clarification from Atlassian support on this matter.
Dec 3, 16:04 UTC
Investigating -
We are currently seeing a small number of clients for which cloning attachments does not work. We are investigating this issue and will update this incident as soon as we have more information.
Dec 3, 15:31 UTC
Resolved -
This incident has been resolved.
Dec 8, 13:49 UTC
Monitoring -
There was an issue regarding app license check in multiple "Quick Filters for Jira" gadgets. As a result, the gadgets could not be used on some customer instances.
The issue started at 12:12 UTC and a fix was deployed at 12:53 UTC. We are currently monitoring the issue and confirming it has been fully resolved.
Dec 8, 13:19 UTC