Check out chapters Get Field Id, Get field configuration context Id, and Create/Update field configuration (options) in order to find out how to use endpoint properly. All endpoints used in the article Singe/Multiple select pickers with create are also used for this custom field, only provided data in the body of Create/Update API is different.
In order to make this request successful, body should follow this scheme and it’s property names:
`{
configurations: [
{
configuration: {
tshirt: [
{
label: "XS",
value: "XS",
description: "...",
active: true/false,
id: "<Unique Id>",
},
{
label: "S",
value: "S",
description: "...",
active: true/false,
id: "<Unique Id>",
},
{
label: "M",
value: "M",
description: "...",
active: true/false,
id: "<Unique Id>",
},
{
label: "L",
value: "L",
description: "...",
active: true/false,
id: "<Unique Id>",
},
{
label: "XL",
value: "XL",
description: "...",
active: true/false,
id: "<Unique Id>",
},
{
label: "XXL",
value: "XXL",
description: "...",
active: true/false,
id: "<Unique Id>",
},
]
},
contextId: "<Unique Id>"
}
]
}`
Properties value and label are fixed and can’t be changed, otherwise it can lead to unexpected behavior of custom field.
Property id must be unique in order for JQL to use it.
Property active is Boolean type, it accepts true or false only.
To make this request properly 6 objects must be passed in tshirt array.