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
Error:-"customfield_10007": "Specify a valid value for 'Change reason'. The allowed values are 10011[Repair], 10012[Upgrade], 10013[Maintenance], 10014[New functionality], 10015[Other], -1"
JSON:-
{
"fields":{
"summary":"None",
"issuetype":{
"id":"10000"
},
"project":{
"key":"CI"
},
"customfield_10007": {
"id":"10007",
"Change reason":"Maintenance"
},
"customfield_10008":"2015-11-10",
"customfield_10009":"2019-11-10",
"customfield_10011":"CI-1",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "description"
}
]
}
]
}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Koxaras _Relational_ , one doubt here,
For custom fields we need to put "value," but for resolution (or default fields), we need to put "name" in key, any reason? what is the differentiator here?
examples :
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.