Hello,
We were trying to create JIRA issues using the REST API. So far we've successfully created a 'barebone' ticket, by supplying the minimum fields, which proved that the route was good.
We had trouble creating the target ticket, which had mandatory custom fields. And these fields look like so from HTTP GET:
"customfield_10000": "xxx",
"customfield_20000":{
"self": "https://company.atlassian.net/rest/api/2/customFieldOption/20000",
"value": "yyy",
"id": "22222"
},
so in our HTTP POST, we specified:
"fields": {
"project": {"id": "12345"},
"summary": "foo",
"issuetype": {"id": "12345"},
"customfield_10000": "xxx",
"customfield_20000": {"id": "22222"},
}
which returned with:
error: {"errorMessages":["There was an error parsing JSON. Check that your request body is valid."]}
the 'barebone' ticket creation which succeded had:
"fields": {
"project": {"id": "54321"}
"summary": "foo",
"issuetype": {"id": "10003"},
}
so it would seem the trouble-maker here were the two new customfields. What were we missing here?
found the problem!
turned out that if the last JSON clause had a comma then the entire block would be treated as illegal JSON. once removed that comma, we started receiving meaningful error messages for the individual customfiels, then, by following the hints, we ended up with a correct JSON block, and the issue creation was then successful!!
hooray!!!
Online 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.