...
The values have to be defined in a JSON fashioned style.
Any fields
How to find out the field-id / key of a field
See here: How to get customfield-id (key) of a Jira field
Syntax examples for field type labels
| Code Block |
|---|
|
{"<label-field-id>": ["label-one", "label-two"]} |
...
| Code Block |
|---|
{"fixVersions": [{"name":"1.4"}]} |
Syntax example for components
| Code Block |
|---|
{"components": [{"name":"Update"}]} |
Syntax examples for field type Text-Field single-line
| Code Block |
|---|
{"customfield_10305":"My text"} |
Syntax example for field type Select List (single choice)
| Code Block |
|---|
{"customfield_10306": {"value": "TeamA"}} |
Syntax example for field type Select List (multiple choice)
| Code Block |
|---|
{"customfield_11803":[{"value":"TeamA"}]}
or
{"customfield_11803":[{"value":"TeamA"}, {"value":"TeamB"}]} |
Syntax examples for combining multiple fiels
| Code Block |
|---|
{"customfield_10304": ["PiedPiper"], "fixVersions": [{"name":"1.4"}]} |
...
Epic-link
If your Jira is setup in a way that it requires for any team-level issue (Story, Bug...) to be linked to an epic, you need to specify this by a specific syntax:
...