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 | Username 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. |
|
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. |
|
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 | Username 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. The To obtain the Account ID can be obtained in the URL displayed at the bottom when you hover over the Account name. navigate to the Account and look at the end of the page URL in the navigation bar to find the ID, as shown below. |
|
Approvers | Username 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. |
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 |
|
Flagged | Option value should be provided. |
|
Organizations | ID of the Organization. You can add multiple Organizations by typing them separated by commas. The Organization ID can be obtained in the URL displayed at the bottom when you hover over the Organization name.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. Eg: https://jmwe-test-2.atlassian.net/projects/PSDF/organization/1 |
|
Raised during | Session ID should be provided. The session ID can be obtained from the URL when you view the session. |
|
Request Participants | Username should be provided. You can add multiple users by typing them separated by commas. |
|
Satisfaction Date | Date in ISO_8601 format |
|
Story points | Any number |
|
Team | Team ID should be provided. The team ID can be obtained from the URL when you view the tempo team. |
|
Test Sessions | Session ID should be provided. The session ID can be obtained from the URL when you view the session. You can add multiple sessions by typing them separated by commas. |
|
...