Hello,
I'm trying to change the type of over 38,000 tickets. Is there a way to do this using this REST API:
/rest/api/3/bulk/issues/move I've tried many payloads, without success.
Chatgpt offered me this after two hours of chatting, but it doesn't work either.
{ "sendBulkNotification": false,
"targetToSourcesMapping": { "VIRPRIN,10102,723102": {
"inferClassificationDefaults": true,
"inferFieldDefaults": true,
"inferStatusDefaults": true,
"inferSubtaskTypeDefault": true,
"issueIdsOrKeys": [ "701484" ]
} } }
And the answer:
Bad request.
We can't connect to the server for this app or website at this time.
There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
The documentation is a bit too brief on this topic.
Does anyone know how to use this API?
Thanks for your help
Have you considered using the issue search and Bulk Change in the UI to move/change their issue type? Is the 1.000 issues at a time the reason why you preferred to do them using REST API?
Anyway, I was able to run it successfully with the json payload below.
But, bear in mind that it has to be POST not GET, otherwise you will get the exact same error that you mentioned
{
"sendBulkNotification": false,
"targetToSourcesMapping": {
"<YOU-PROJ-KEY>,<YOUR-TARGET-ISSUETYPE-ID>": {
"issueIdsOrKeys": ["TMP-21"],
"inferClassificationDefaults": true,
"inferFieldDefaults": true,
"inferStatusDefaults": true,
"inferSubtaskTypeDefault": true
}
}
}
this is the version with id values that I tried
POST: /rest/api/3/bulk/issues/move
{
"sendBulkNotification": false,
"targetToSourcesMapping": {
"TMP,10050": {
"issueIdsOrKeys": ["TMP-21"],
"inferClassificationDefaults": true,
"inferFieldDefaults": true,
"inferStatusDefaults": true,
"inferSubtaskTypeDefault": true
}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know why, but when I run the request, the POST becomes a GET. I need to find out where the bug is in my code.
Thank you for helping me figure out the reason for this strange response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Today only! Share what you’re the most excited about for Team ‘25 or just dance out the beginning of a new quarter with us.
Comment the postOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.