Custom fields
The Jira Service Management connector supports custom fields for the following cards:
For a list of common supported custom fields, see List of supported custom fields for request types on Jira's support site.
Supported fields and schemas
If a custom field isn't supported, use a CAPIA card instead. See Build a custom API action card
To determine if a specific field is supported, you can use a Custom API Action (CAPIA) card and call GET /rest/api/3/field to retrieve the list of system and custom fields. Search for the specific custom field by its name or ID.
It's important to verify both the schema.type and schema.item are supported when reviewing results. See Supported schema examples.
The following schema.type are supported:
- array
- string
- sd-asset
- attachment
- version
- user
- component
- option
- number
- datetime
- date
- option-with-child
- priority
If the schema.type is array, the following schema.item are supported:
- string
- sd-asset
- attachment
- version
- user
- component
- option
- number
- datetime
- date
Supported schema examples
Example with supported schema.type
{
"id": "customfield_10989",
"key": "customfield_10989",
"name": "Operational categorization",
...
"schema": {
"type": "option-with-child",
"custom": "com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect",
"customId": 10989
}
}
Example with supported schema.type and schema.item
{
"id": "customfield_107",
"key": "customfield_107",
"name": "Approvers",
...
"schema": {
"type": "array",
"items": "user",
"custom": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker",
"customId": 107
}
}