You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
So basically, when a customfield 11500, which is Source in our case, is added to the API Post request, we get a 400 error back. When that field is taken out, the ticket is made just fine.
I checked to make sure the value works(as in an available option), the syntax appears fine(it is exactly the same as the other fields, the custom field number is also correct, and the field is available for this issue type in the project.
customfield11500: {value: confirmedoption}
I also successfully made a Jira ticket with Source as a field manually.
Does anyone have any idea of what could be causing a 400 error?
"POST /rest/api/latest/issue/ HTTP/1.1" 400 145 457 "https://localhost:3200/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36 Edg/111.0.1661.44" "hqntl0"