Versions Compared

Key

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

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 Set field value to constant or Groovy template. Click on Expected Value. The help editor displays the expected text/Groovy templates values for the selected field.

You might also want to look at Standard fieldsPredefined custom fields, and User-created custom fields to know how to access the fields of an issue object.

...

 Field Name

Expected input value

Examples

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
SprintString representing the ID of the sprint should be provided.

1

Story pointsString representing the number of story points should be provided

5

Jira Service Desk fields

 Field Name

Expected input value

Examples

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

It is recommended you use Username(s) because Email address(es) and Full name(s) are not unique in Jira.



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
Request Participants
  • 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.
Note

It is recommended you use Username(s) because Email address(es) and Full name(s) are not unique in Jira.



...

 Field Name

Expected input value

Examples

Account

The Account Id, key, or name should be provided. Key is preferred

  • 23
  • ACCOUNT1
  • Account 1

Team

Team ID should be provided. The Team ID can be obtained from the URL when you view or edit the team.
  • 2
  • 3

...