---
title: "Raw value/text input for fields"
canonical: "https://support.appfire.com/space/JMWE/461406738/Raw%20value%2Ftext%20input%20for%20fields"
format: markdown
---
> Macro (aura-html)

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](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461897846). It <span style="color: #091e42">lists the possible expected values for the selected</span><span style="color: #091e42"> </span>`Field`<span style="color: #091e42"> </span><span style="color: #091e42">and</span><span style="color: #091e42"> </span>`Value Type`<span style="color: #091e42">. This is applicable in contexts where you set a field value or comment an issue or write a conditional Groovy script. Select the</span><span style="color: #091e42"> </span>`Field`<span style="color: #091e42"> </span><span style="color: #091e42">and</span><span style="color: #091e42"> </span>`Value Type as ``Set field value to constant or Groovy template.`<span style="color: #091e42"> Click on</span>` ``Expected Value.`<span style="color: #091e42"> </span><span style="color: #091e42">The help editor displays the expected text/Groovy templates values for the selected field.</span>

<span style="color: #000000">Y</span><span style="color: #000000">ou might also want to look at </span>[<span style="color: #000000">Standard fields</span>](https://appfire.atlassian.net/wiki/display/JMWE/Standard+JIRA+fields)<span style="color: #000000">, </span>[<span style="color: #000000">Predefined custom fields</span>](https://appfire.atlassian.net/wiki/display/JMWE/Pre-defined+custom+fields)<span style="color: #000000">, and </span>[<span style="color: #000000">User-created custom fields</span>](https://appfire.atlassian.net/wiki/display/JMWE/Pre-defined+custom+fields)<span style="color: #000000"> to know how to access the fields of an issue object.</span>

**On this page: **


### Standard Jira fields

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">Affects Version/s</span> | - Version *name* or* id* *(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name) *should be provided
- To set multiple values, you should provide version *names* or *ids (i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name)* separated by a comma. | - `2.0`
- `10000`
- `2.0,3.0`
- `10020,V1` |
| Assignee | Any of the following user detail should be provided:<br>- Username
- Email address
- Full name<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White` |
| <span style="color: #000000">Component/s</span> | - <span style="color: #000000">Component </span>*<span style="color: #000000">name</span>*<span style="color: #000000"> or </span>*<span style="color: #000000">id</span>*<span style="color: #000000"> </span>*<span style="color: #000000">(id</span>*<span style="color: #000000"> </span><span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*<span style="color: #000000">name) </span>*<span style="color: #000000">should be provided</span>
- To set multiple values, you should provide component *names* or *ids (id* <span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name)* separated by a comma. | - `C1`
- `C1,C2`
- `10000` |
| Description | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | - `Test`
- `Testing of`  
`First project`  
`Second project` |
| Due Date | String representing a timestamp in the [format](http://docs.oracle.com/javase/6/docs/api/index.html?java/text/SimpleDateFormat.html) specified in [Jira system settings](https://confluence.atlassian.com/adminjiraserver073/configuring-the-look-and-feel-of-your-jira-applications-861253125.html#ConfiguringthelookandfeelofyourJIRAapplications-Howtochangedateandtimeformats)*.* | - `11/Apr/17` |
| Environment | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | - `QA Environment` |
| <span style="color: #000000">Fix Version/s</span> | - Version *name* or *id* *(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name) *should be provided
- To set multiple values, you should provide version *names* or *ids* *(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name) *separated by a comma | - `2.0`
- `2.0,3.0`
- `10020` |
| <span style="color: #000000">Issue type</span> | > ⚠️ **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.<br>String representing the issue type name or id | - `Bug`
- `10020` |
| Labels | - String representing a label should be provided.
- To set multiple labels, you should provide values separated by *space*. | - `NewLabel`
- `Label1 Label2 Label3` |
| Original Estimate | Number representing the estimate in seconds or a duration string should be provided. | - `36000`
- `3w 2d`
- `2w 4d 5h 50m` |
| Priority | Priority *name* or *id **(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000"> </span>*name)* should be provided | - `High`
- `2` |
| Remaining Estimate | Number representing the estimate in seconds or a duration string should be provided. | - `36000`
- `3w 2d`
- `2w 4d 5h 50m` |
| Reporter | Any of the following user detail should be provided:<br>- Username
- Email address
- Full name<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White` |
| Resolution | <span style="color: #000000">Resolution </span>*name*<span style="color: #000000"> or </span>*ID **(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000">* *</span>*name)*<span style="color: #000000"> should be provided</span> | - `Won't Do`
- `11212` |
| Security level | Security level *name* or *id* *(i**d** *<span style="color: #000000">takes precedence over the</span><span style="color: #000000"> </span>*name) *should be provided | - `QA1`
- `10001` |
| <span style="color: #000000">Status</span> | > ⚠️ **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.<br>String representing the status name or status id | - `Open`
- `10020` |
| Summary | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | - `This is the summary of the issue` |
| Time Spent | Number representing the time spent in seconds or a duration string should be provided. | - `36000`
- `3w 2d`
- `2w 4d 5h 50m` |
| Votes | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |
| Watchers | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |

### Pre-defined custom fields

#### Capture for JIRA fields

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">All Capture for JIRA fields</span> | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | <span style="color: #000000">All the Capture for JIRA fields expect a text value.</span> |
| <span style="color: #000000">Raised during</span> | <span style="color: #000000">Session </span>*ID*<span style="color: #000000"> should be provided. The session ID can be obtained from the URL when you view the session.</span> | `10010` |

#### Jira Software fields

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">Epic Color</span> | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | `ghx-label-6` |
| <span style="color: #000000">Epic Link</span> | <span style="color: #000000">Issue </span>*KEY*<span style="color: #000000"> of an Epic should be provided</span> | - `TEST-300`
- `TP-33` |
| Epic Name | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | `Creation of a new issue` |
| Epic Status | <span style="color: #000000">Status </span>*<span style="color: #000000">value</span>*<span style="color: #000000"> should be provided</span> | - `To Do`
- `Done` |
| Sprint | String representing the ID of the sprint should be provided. | `1` |
| Story points | String representing the number of story points should be provided | `5` |

#### <span style="color: #707070">Jira Service Desk fields</span>

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Approvers | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |
| Customer Request Type | - *Customer Request Type* name or internal ID | - IT help
- `sd/desktoplaptopsupport` |
| Organizations | - Organization name ID should be provided.
- To set multiple values, you should provide the Organization* names *or *IDs* separated by a comma. | - `Org1`
- `Org1,Org2`
- `1`
- `1,33` |
| <span style="color: #000000">Request Participants</span> | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |

#### <span style="color: #000000">**Portfolio for Jira fields**</span>

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">Parent Link</span> | <span style="color: #000000">Issue </span>*KEY*<span style="color: #000000"> of an Initiative should be provided. </span><br>**<span style="color: #000000">Note:</span>**<span style="color: #000000"> You can use this field to create a link (Jira Portfolio Parent Link) from Epic to Initiative</span> | KP-9 |

#### Tempo fields

| <span style="color: #000000">** Field Name**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">Account</span> | The Account* Id, key, or name* should be provided. Key is preferred | - `23`
- `ACCOUNT1`
- `Account 1` |
| <span style="color: #000000">Team</span> | <span style="color: #000000">Team </span>*ID*<span style="color: #000000"> should be provided. The Team ID can be obtained from the URL when you view or edit the team.</span> | - `2`
- `3` |

###   
<span style="color: #000000">User-created custom fields</span>

<span style="color: #000000">The value expected by custom fields depends on the Custom Field Type:</span>

#### <span style="color: #000000">Select list type</span>

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Checkboxes/Select List (multiple choices) | - <span style="color: #000000">Option </span>*<span style="color: #000000">id</span>*<span style="color: #000000"> or </span>*<span style="color: #000000">value</span>**<span style="color: #000000"> </span>**<span style="color: #000000">(value </span>*<span style="color: #000000">*takes precedence over the*</span><span style="color: #000000">* id)*</span><span style="color: #000000"> should be provided. The option id can be obtained from the URL when you edit the option.</span>
- <span style="color: #000000">T</span><span style="color: #000000">o set multiple options, you should provide option </span>*<span style="color: #000000">values</span>*<span style="color: #000000"> or </span>*<span style="color: #000000">ids</span>*<span style="color: #000000"> </span>*<span style="color: #000000">(value </span>**<span style="color: #000000">takes precedence over the</span>**<span style="color: #000000"> id) </span>*<span style="color: #000000">separated by a comma.</span> | - `10000`
- `Option1, Option2`
- `10000,10002` |
| Radio Buttons/Select List (single choice) | <span style="color: #000000">Option </span>*id*<span style="color: #000000"> or </span>*value **(value **takes precedence over the** id)*<span style="color: #000000"> should be provided. </span><span style="color: #000000">The option id can be obtained from the URL when you edit the option.</span> | - `10003`
- `Option2` |
| Select List (cascading) | - Cascading parent *value* or *id* should be provided
- Cascading parent *value* or *id* and child option *value* or *id* should be provided in `<parent value> - <child option>` format. | - `2`
- `2 - 2.1`
- `10202`
- `10202 - 10301` |
| [Multi-level cascading select list](https://marketplace.atlassian.com/apps/5008/multi-level-cascading-select) | - A comma-separated list of option values, from parent to child
- A comma-separated list of option IDs, from parent to child | - `Parent 1,Child A,Child b`
- `10010,10011,10100` |


#### Group picker

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Group Picker (single group) | Group *name* should be provided | - `jira-administrators` |
| Group Picker (multiple groups) | - Group *name* should be provided
- To set multiple values, you should provide group *names* separated by a comma. | - `jira-administrators,jira-software-users` |

#### User picker

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| User Picker (multiple users) | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |
| User Picker (single user) | Any of the following user detail should be provided:<br>- Username
- Email address
- Full name<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White` |

#### Version picker

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Version Picker (single version) | - Version *id* or *name **(i**d** *<span style="color: #000000">*takes precedence over the*</span><span style="color: #000000">* *</span>*name)* should be provided | - `10020`
- `2.0` |
| Version Picker (multiple versions) | - Version *id* or *name **(i**d** *<span style="color: #000000">*takes precedence over the*</span><span style="color: #000000">* *</span>*name)* should be provided
- To set multiple values, you should provide version *ids* or *names **(i**d** *<span style="color: #000000">*takes precedence over the*</span><span style="color: #000000">* *</span>*name) *separated by a comma. | - `10020`
- `2.0`
- `10020,10010`
- `1.0,2.0` |

#### Text

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Text Field (single line) | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | - `This is a text line` |
| Text Field (multi-line) | <span style="color: #000000">Any simple single/multi-line text should be provided</span> | - `First line`  
`Second line` |

#### Date/Time picker

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Date Picker | String representing a timestamp in the [format](http://docs.oracle.com/javase/6/docs/api/index.html?java/text/SimpleDateFormat.html) specified in [Jira system settings](https://confluence.atlassian.com/adminjiraserver073/configuring-the-look-and-feel-of-your-jira-applications-861253125.html#ConfiguringthelookandfeelofyourJIRAapplications-Howtochangedateandtimeformats) | - `23/Dec/16` |
| Date Time Picker | String representing a timestamp in the [format](http://docs.oracle.com/javase/6/docs/api/index.html?java/text/SimpleDateFormat.html) specified in [Jira system settings](https://confluence.atlassian.com/adminjiraserver073/configuring-the-look-and-feel-of-your-jira-applications-861253125.html#ConfiguringthelookandfeelofyourJIRAapplications-Howtochangedateandtimeformats) | - `23/Dec/16 2:00 AM` |

#### Watchers Field type

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| <span style="color: #000000">Watchers field</span> | - Any of the following user detail should be provided:
  - Username
  - Email address
  - Full name
- To set multiple values, you can provide a combination of user details (as mentioned above) separated by a comma.<br>> ⚠️ It is recommended you use *Username(s)* because *Email **<span style="color: #172b4d">address(es)</span>*<span style="color: #172b4d"> and </span>*<span style="color: #172b4d">Full name(s)</span>*<span style="color: #172b4d"> are not unique in Jira.</span> | - `carter`
- `carter,charlie`
- [charliej@abc.com](mailto:johndoe@abc.com)
- `Joe White, `[charliej@abc.com](mailto:charliej@abc.com) |

#### Others

| <span style="color: #000000">**Custom field type**</span> | <span style="color: #000000">**Expected input value**</span> | <span style="color: #000000">**Examples**</span> |
| --- | --- | --- |
| Project Picker (single project) | <span style="color: #000000">Project </span>*id or name or key *<span style="color: #000000">should be provided</span> | - `10000`
- `TEST`
- `Test` |
| Labels | - String representing a label should be provided.
- To set multiple labels, you should provide values separated by *space*. | - `NewLabel`
- `Label1 Label2 Label3` |
| URL Field | <span style="color: #000000">Any simple text of URL format should be provided</span> | - [https://innovalog.com](https://innovalog.com/) |
| Number Field | Number should be provided | - `33`
- `0.5` |