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.
On this page:
Standard Jira fields
Field Name | Expected input value | Examples | |
---|---|---|---|
Affects Version/s |
|
| |
Assignee | Username should be provided |
| |
Component/s |
|
| |
Description | Any simple single/multi-line text should be provided |
| |
Due Date | String representing a timestamp in the format specified in Jira system settings. |
| |
Environment | Any simple single/multi-line text should be provided |
| |
Fix Version/s |
|
| |
Issue type | Use with caution! Changing the issue type should only be done if the current and new issue types share the same workflow, or if the issue's Status exists in both the current and new workflow. Otherwise, the operaton will fail. Also, when changing the issue type of the current issue, make sure to move the post-function below the "Set issue status to the linked status of the destination workflow step" built-in post-function. String representing the issue type name or id |
| |
Labels |
|
| |
Original Estimate | Number representing the estimate in seconds or a duration string should be provided. |
| |
Priority | Priority name or id (id takes precedence over the name) should be provided |
| |
Remaining Estimate | Number representing the estimate in seconds or a duration string should be provided. |
| |
Reporter | Username should be provided |
| |
Resolution | Resolution name or ID (id takes precedence over the name) should be provided |
| |
Security level | Security level name or id (id takes precedence over the name) should be provided |
| |
Status | Use with caution! Changing the Status of an issue is normally done only through an issue transition. Changing the Status field value directly will not validate potentially required fields (such as the Resolution field), and will leave no trace in the issue history. This should be used only in specific cases. Also, when changing the Status of the current issue, make sure to move the post-function below the "Set issue status to the linked status of the destination workflow step" built-in post-function. Finally, the Status field cannot be set during a Create transition. String representing the status name or status id |
|
|
Summary | Any simple single/multi-line text should be provided |
| |
Time Spent | Number representing the time spent in seconds or a duration string should be provided. |
| |
Votes |
|
| |
Watchers |
|
|
Pre-defined custom fields
Capture for JIRA fields
Field Name | Expected input value | Examples |
---|---|---|
All Capture for JIRA fields | Any simple single/multi-line text should be provided |
|
Raised during | Session ID should be provided. The session ID can be obtained from the URL when you view the session. |
|
Jira Software fields
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 |
|
|
Portfolio for Jira fields
Field Name | Expected input value | Examples |
---|---|---|
Parent Link | Issue KEY of an Initiative should be provided. Note: You can use this field to create a link (Jira Portfolio Parent Link) from Epic to Initiative | KP-9 |
Tempo fields
Field Name | Expected input value | Examples |
---|---|---|
Account | Account Id should be provided |
|
Team | Team ID should be provided. The Team ID can be obtained from the URL when you view or edit the team. |
|
User-created custom fields
The value expected by custom fields depends on the Custom Field Type:
Select list type
Custom field type | Expected input value | Examples |
---|---|---|
Checkboxes/Select List (multiple choices) |
|
|
Radio Buttons/Select List (single choice) | Option id or value (value takes precedence over the id) should be provided. The option id can be obtained from the URL when you edit the option. |
|
Select List (cascading) |
|
|
Multi-level cascading select list |
|
|
Group picker
Custom field type | Expected input value | Examples |
---|---|---|
Group Picker (single group) | Group name should be provided |
|
Group Picker (multiple groups) |
|
|
User picker
Custom field type | Expected input value | Examples |
---|---|---|
User Picker (multiple users) |
|
|
User Picker (single user) | Username should be provided. |
|
Version picker
Custom field type | Expected input value | Examples |
---|---|---|
Version Picker (single version) |
|
|
Version Picker (multiple versions) |
|
|
Text
Custom field type | Expected input value | Examples |
---|---|---|
Text Field (single line) | Any simple single/multi-line text should be provided |
|
Text Field (multi-line) | Any simple single/multi-line text should be provided |
|
Date/Time picker
Custom field type | Expected input value | Examples |
---|---|---|
Date Picker | String representing a timestamp in the format specified in Jira system settings |
|
Date Time Picker | String representing a timestamp in the format specified in Jira system settings |
|
Watchers Field type
Custom field type | Expected input value | Examples |
---|---|---|
Watchers field |
|
|
Others
Custom field type | Expected input value | Examples |
---|---|---|
Project Picker (single project) | Project id or name or key should be provided |
|
Labels |
|
|
URL Field | Any simple text of URL format should be provided | |
Number Field | Number should be provided |
|