MoSCoW Configuration
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, the body should follow this scheme and its property names:
`{
configurations: [
{
configuration: {
moscow: [
{ label: "...", value: "<default, inprogress, moved, new, removed, success>", id: "<Unique Id>" },
{ label: "...", value: "<default, inprogress, moved, new, removed, success>", id: "<Unique Id>" },
{ label: "...", value: "<default, inprogress, moved, new, removed, success>", id: "<Unique Id>" },
{ label: "...", value: "<default, inprogress, moved, new, removed, success>", id: "<Unique Id>" },
]
},
contextId: "<Unique Id>"
}
]
}`
The property value
must contain one of the following strings: default
, inprogress
, moved
, new
, removed
, success
.
Property id
must be unique in order for JQL to use it.
To make this request properly 4 objects must be passed in moscow
arrays.
, multiple selections available,
Related content
App Limitations
App Limitations
Read with this
Default values and Bulk changes
Default values and Bulk changes
Read with this
How to use custom fields in Automation rules
How to use custom fields in Automation rules
Read with this
T-Shirt Configuration
T-Shirt Configuration
Read with this
Decimal Number Configuration
Decimal Number Configuration
Read with this
MoSCoW Prioritization
MoSCoW Prioritization
Read with this