I used this Json for creating bulk issues
{
"issues": [
{
"id": "10174",
"key": "SJI-175",
"self": "https://soundsmart.atlassian.net/rest/api/2/issue/10174"
}
],
"errors": [
{
"status": 400,
"elementErrors": {
"errorMessages": [],
"errors": {
"customfield_10038": "Field 'customfield_10038' cannot be set. It is not on the appropriate screen, or unknown."
}
},
"failedElementNumber": 1
},
{
"status": 400,
"elementErrors": {
"errorMessages": [],
"errors": {
"customfield_10038": "Field 'customfield_10038' cannot be set. It is not on the appropriate screen, or unknown."
}
},
"failedElementNumber": 2
}
]
}
and I got this response
{
"issues": [
{
"id": "10177",
"key": "SJI-178",
"self": "https://soundsmart.atlassian.net/rest/api/2/issue/10177"
}
],
"errors": [
{
"status": 400,
"elementErrors": {
"errorMessages": [],
"errors": {
"customfield_10038": "Field 'customfield_10038' cannot be set. It is not on the appropriate screen, or unknown."
}
},
"failedElementNumber": 1
},
{
"status": 400,
"elementErrors": {
"errorMessages": [],
"errors": {
"customfield_10038": "Field 'customfield_10038' cannot be set. It is not on the appropriate screen, or unknown."
}
},
"failedElementNumber": 2
}
]
}
First issue is getting created but the remaining issues are creating problem..
Could anyone help to resolve this ?!
The url I hit is: https://soundsmart.atlassian.net/rest/api/2/issue/bulk
Hi @sowmi smart -- Welcome to the Atlassian Community!
I believe you posted the response twice rather than the request and response. Please consider editing your question so the community can help.
Next, please consider editing your post to remove your specific company URL information.
Finally, when you are using JSON to create/edit issues, it can sometimes be difficult to know what the field/smart value names are. You can use the method at the link below with the REST API to look up an example issue and confirm that you have the correct names:
https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.