This document lists the expected text/raw input value that should be provided to set Jira Standard and Custom fields. The easiest is to use the "Expected Value" tab of the Groovy editor help system. It lists the possible expected values for the selected Field
and Value Type
. This is applicable in contexts where you set a field value or comment an issue or write a conditional Groovy script. Select the Field
and Value Type as
Click onSet field value to constant or Groovy template.
Expected Value.
The help editor displays the expected text/Groovy templates values for the selected field.
You might also want to look at Standard fields, Predefined custom fields, and User-created custom fields to know how to access the fields of an issue object.
...
Field Name | Expected input value | Examples |
---|---|---|
Epic Color | Any simple single/multi-line text should be provided |
|
Epic Link | Issue KEY of an Epic should be provided |
|
Epic Name | Any simple single/multi-line text should be provided |
|
Epic Status | Status value should be provided |
|
Sprint | String representing the ID of the sprint should be provided. |
|
Story points | String representing the number of story points should be provided |
|
Jira Service Desk fields
Field Name | Expected input value | Examples | ||
---|---|---|---|---|
Approvers |
|
| ||
Customer Request Type |
|
| ||
Organizations |
|
| ||
Request Participants |
|
|
...
Field Name | Expected input value | Examples |
---|---|---|
Account | The Account Id, key, or name should be provided. Key is preferred |
|
Team | Team ID should be provided. The Team ID can be obtained from the URL when you view or edit the team. |
|
...