This document lists the expected text input value This document lists the expected text input value that should be provided to set Jira Standard and Custom fields. You might also want to look at Standard Jira fields, Predefined Custom fields and User-created custom fields to know how to access the fields of an issue.
...
Field Name | Expected input value | Examples | ||
---|---|---|---|---|
Affect Version/s | Version name should be provided. You can add multiple versions by typing them separated by commas. |
| ||
Assignee | AccountId should be provided, or empty string for Unassigned |
| ||
Attachments | Attachment URL should be provided. You can add multiple attachments typing the URL's separated by commas. | |||
Components | Component name should be provided. You can add multiple components by typing them separated by commas. |
| ||
Description | Any simple single/multi-line text should be provided |
| ||
Due Date | Date in ISO_8601 format |
| ||
Environment | Any simple single/multi-line text should be provided |
| ||
Fix Version/s | Version name should be provided. You can add multiple versions by typing them separated by commas. |
| ||
Issue Type | Issue Type name should be provided. |
| ||
Labels | Any simple text should be provided. You can add multiple labels by typing them separated by spaces. |
| ||
Linked Issues | You cannot set this field using a text value. See JSON input for fields to set this. | NA | Original JSON input for fields to set this. | NA |
Original Estimate | A Number of seconds or a duration string. |
| ||
Priority | Priority name should be provided. |
| ||
Remaining Estimate | A Number of seconds or a duration string. |
| Priority | Priority name |
Reporter | Username should be provided. |
| ||
Resolution | Resolution name should be provided. |
| ||
Security level | Security level name should be provided. |
| ||
Summary | Any single-line text should be provided. |
| ||
Remaining Estimate | A Number of seconds or a duration string. |
| ||
Reporter | Username should be provided. |
| ||
Resolution | Resolution name should be provided. |
| ||
Security level | Security level name should be provided. |
| ||
Summary | Any single-line text should be provided |
| ||
Time Tracking | You cannot set this field using a text value. See JSON input for fields to set this. | NA | ||
Watchers
| ||||
Time Tracking | You cannot set this field using a text value. See JSON input for fields to set this. | NA | ||
Watchers | AccountId should be provided. You can add multiple users by typing them separated by commas. |
|
Predefined Custom fields
Field Name | Expected input value | Examples |
---|---|---|
Account | Account ID should be provided. To obtain the Account ID navigate to the Account and look at the end of the page URL in the navigation bar to find the ID, as shown below. Eg: https://test.atlassian.net/plugins/servlet/ac/io.tempo.jira/tempo-accounts#!/account/2/ |
|
Approvers | AccountId should be provided. You can add multiple users by typing them separated by commas. |
|
|
Predefined Custom fields
Field Name | Expected input value | Examples | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Account | Account ID
| |||||||||||
All Capture for Jira fields | Any simple single/multi-line text should be provided | All the Capture for Jira fields expect a text value. | ||||||||||
Customer Request Type | The Customer Request Type ID or name should be provided. ToTo obtain the Account ID navigate to the Account and look at the end of the page URL in the navigation bar to find the ID, as shown below.Eg: https://test.atlassian.net/plugins/servlet/ac/io.tempo.jira/tempo-accounts#!/account/2/ |
| ||||||||||
Approvers | AccountId should be provided. You can add multiple users by typing them separated by commas. |
| ||||||||||
All Capture for Jira fields | Any simple single/multi-line text should be provided | All the Capture for Jira fields expect a text value. | Customer Request Type |
Note |
---|
Note that you can set the Customer Request Type field only in the Create issue post-function using the |
Note |
---|
Note that while setting the Customer Request Type, you must provide a value for any field that is declared as mandatory for that request type. |
41
Travel Request
ghx-label-6
TEST-300
TP-33
Creation of a new issue
To Do
Done
Option value should be provided.
Impediment
ID of the Organization. You can add multiple Organizations by typing them separated by commas. To obtain the Organization ID navigate to the Organization and look at the end of the page URL in the navigation bar to find the ID, as shown below.
1
1,33
Customer Request Type ID
- Manually set the Customer Request Type for an issue
- In the Nunjucks tester, test for the id of the Customer Request Type for the issue:
{{ issue.fields['Customer Request Type'].requestType.id }}
Note |
---|
Note that you can set the Customer Request Type field only in the Create issue post-function using the |
Note |
---|
Note that while setting the Customer Request Type, you must provide a value for any field that is declared as mandatory for that request type. |
41
Travel Request
ghx-label-6
TEST-300
TP-33
Creation of a new issue
To Do
Done
Option value should be provided.
Impediment
The value should be a comma-separated list of Organization names or IDs. To obtain an Organization ID, navigate to the Organization and look at the end of the page URL in the navigation bar to find the ID, as shown below:
1
1,33
Org 1, Org 2
Org 1, 4
10011
accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e
accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e
,accountId:557145:3a41d4ee-3331-4363-8cdf-f90a2da926h9
2016-08-05
Sprint ID should be provided.
To identify the Sprint ID, add the Sprint to an issue and use the Nunjucks Script tester with the following template: {{issue.fields["Sprint"] }}
and look at the id field in the result.
3
12
3.1
10
Team
10011
accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e
accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e
,accountId:557145:3a41d4ee-3331-4363-8cdf-f90a2da926h9
2016-08-05
Eg: https://test.atlassian.net/plugins/servlet/ac/io.tempo.jira/tempo-teams#!/team/2
3
1
(for the default team)
Team ID should be provided.
Team
To identify the Sprint team ID, add the Sprint Team to an issue and use the Nunjucks Script tester with the following template: {{ issue.fields["Sprint"] }}
and look at the id field in the result.
3
12
3.1
10
.Team }}
Note | ||
---|---|---|
| ||
You cannot clear this field, nor set it if it already has a value. This is due to JIRA Portfolio bugs. |
3
1
Eg: https://test.atlassian.net/plugins/servlet/ac/io.tempo.jira/tempo-teams#!/team/2
3
1
(for the default team)
Team ID should be provided.
To identify the team ID, add the Team to an issue and use the Nunjucks Script tester with the following template: {{ issue.fields.Team }}
Note | ||
---|---|---|
| ||
You cannot clear this field, nor set it if it already has a value. This is due to JIRA Portfolio bugs. |
3
1
10011
10012, 10013
User-created custom fields
The value expected by custom fields depends on the Custom Field Type:
Custom field type | Expected input value | Examples | ||
---|---|---|---|---|
Check boxes / Multi select list | Option value(s) or id(s) should be provided. You can add multiple options by typing the value(s) or id(s) separated by commas.
To obtain an option ID, you can go to the custom field configuration, navigate to the Option, edit it and look at the end of the page URL in the navigation bar to find the ID. |
| ||
Radio buttons / Single select list | Option value or id should be provided
To obtain an option ID, you can go to the custom field configuration, navigate to the Option, edit it and look at the end of the page URL in the navigation bar to find |
10011
10012, 10013
User-created custom fields
The value expected by custom fields depends on the Custom Field Type:
Custom field type | Expected input value | Examples | ||
---|---|---|---|---|
Check boxes / Multi select list | Option value should be provided. You can add multiple options by typing them separated by commas. |
| ||
Radio buttons / Single select list | Option value should be provided the ID. |
| ||
Select list (cascading) | Parent value or id - Child value or id should be provided to set both the parent and child levels. To set just the parent, you should provide only the parent valueset both the parent and child levels. To set just the parent, you should provide only the parent value or id.
To obtain the parent or child ID, you can go to the custom field configuration, navigate to the parent or child, edit it and look at the end of the page URL in the navigation bar to find the ID. |
| ||
Single Group Picker | Group name should be provided |
| ||
Multi Group Picker | Group name should be provided. You can add multiple groups by typing them separated by commas. |
| ||
Project Picker (single project) | Project key should be provided |
| ||
User Picker (single user) | AccountId should be provided. |
| ||
User Picker (multiple users) | AccountId should be provided. You can add multiple users by typing them separated by commas. |
| ||
Version Picker (single version) | Version name should be provided. |
| ||
Version Picker (multiple versions) | Version name should be provided. You can add multiple versions by typing them separated by commas. |
| ||
Text Field (single line) | Any simple single text should be provided |
| ||
Text Field (multi line) | Any simple single/multi-line text should be provided |
| ||
Text Field (read only) | Any simple single/multi-line text should be provided |
| ||
URL Field | Text representing a URL should be provided | |||
Number Field | Number should be provided |
| ||
Labels | Any simple text should be provided. You can add multiple labels by typing them separated by spaces. |
| ||
Date picker | Text representing a date should be provided |
| ||
Date Time Picker | Text representing a date/time should be provided |
|
...