Versions Compared

Old Version 25

changes.mady.by.user Radhika Vijji.

Saved on

compared with

New Version 26

changes.mady.by.user Radhika Vijji.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 NameExpected input valueExamples
Affect Version/s

Version name should be provided. You can add multiple versions by typing them separated by commas.

  • 2.0
  • 2.0,3.0
Assignee

Username should be provided, or empty string for Unassigned

  • carter

AttachmentsAttachment 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.

  • C1

  • C1,C2

DescriptionAny simple single/multi-line text should be provided
  • This is a description
Due DateDate in ISO_8601 format
  • 2016-08-05
Environment Any simple single/multi-line text should be provided
  • This is the QA Environment
  • QA
Fix Version/s

Version name should be provided. You can add multiple versions by typing them separated by commas.

  • 2.0
  • 2.0,3.0
Issue TypeIssue Type name should be provided.
  • Bug
  • Task
Labels

Any simple text should be provided. You can add multiple labels by typing them separated by spaces.

  • NewLabel
  • Label1 Label2 Label3
  • 1 2 3
Linked IssuesYou cannot set this field using a text value. See JSON input for fields to set this.NA
Original Estimate

A Number of seconds or a duration string.

  • 25200
  • 3w
  • 4w 2d 1h
Priority
Priority name should be provided.
  • Highest
  • Low
Remaining Estimate

A Number of seconds or a duration string.

  • 25200
  • 3w
  • 4w 2d 1h
Reporter

Username should be provided.

  • carter
Resolution

Resolution name should be provided.

  • Won't Do
  • Duplicate
Security level

Security level name should be provided.

  • QA Domain
  • Security Level for Dev
SummaryAny single-line text should be provided
  • Credit Card issue module
Time TrackingYou 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.

  • carter
  • carter,john

Predefined Custom fields

 Field NameExpected input valueExamples
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/

  • 1
ApproversUsername should be provided. You can add multiple users by typing them separated by commas.
  • carter
  • carter,john
All Capture for Jira fieldsAny 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. To obtain the 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 Set fields of new issue option.


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
Epic ColorAny simple single/multi-line text should be provided
  • ghx-label-6
Epic LinkIssue KEY of an Epic should be provided.
  • TEST-300
  • TP-33
Epic NameAny simple single/multi-line text should be provided
  • Creation of a new issue
Epic StatusStatus value should be provided
  • To Do
  • Done
Flagged

Option value should be provided.

  • Impediment
Organizations

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.

Eg: https://test.atlassian.net/projects/PSDF/organization/1

  • 1
  • 1,33
Raised duringSession ID should be provided. The session ID can be obtained from the URL when you view the session. To obtain the Session ID navigate to the Session and look at the end of the page URL in the navigation bar to find the ID.
  • 10011
Request ParticipantsUsername should be provided. You can add multiple users by typing them separated by commas.
  • carter
  • carter,john
Satisfaction DateDate in ISO_8601 format
  • 2016-08-05
Sprint

Sprint ID should be provided. 

(info) 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
Story pointsAny number
  • 3.1
  • 10

Team

Team ID should be provided. To obtain the Team ID navigate to the Team 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-teams#!/team/2

  • 3
  • 1 (for the default team)
Team (Portfolio)

Team ID should be provided. 

(info) 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
titleLimitations when setting this field

You cannot clear this field, nor set it if it already has a value. This is due to JIRA Portfolio bugs.


  • 3
  • 1
Test SessionsSession ID should be provided. You can add multiple sessions by typing them separated by commas. To obtain the Session ID navigate to the Session and look at the end of the page URL in the navigation bar to find the ID.
  • 10011
  • 10012, 10013

...