On this page

One of the main features of JWT for Jira Cloud is the easy access to Jira data through the use of field codes.

JWT field codes are currently only available to be used in post functions and the following Parsing modes:

Conditions and validators use the Jira expression mode and a different set of field codes.

Field code notation


Depending on the context in which they are being used, field codes will contain a prefix following this notation {origin.field} .


Available contexts (or origins) in JWT for Jira Cloud are:

ContextDescription

issue

The issue that is processed by the workflow post function

parent

The parent of the issue that is processed by the workflow post function - if available
seed

The field value will be retrieved from the element currently being processed by a workflow function that is capable of analyzing multiple elements (e.g. Create issue post function).

Elements can be:

  • texts
  • numbers
  • issues

depending in your configuration. Read more about seeds.

system

Some data does not have an issue context (e.g. the currently logged in user or the system date and time)


The prefix, denoting the origin (where the data should be read from / written to), is a referential part of the field code and will be inserted into the expression whenever you select a field from a drop-down list.   

Here are some examples:  

Field codeOutput

%{issue.description}

The description of the current issue

%{parent.summary}

The summary of the parent issue

%{issue.project.lead}

The project lead of the project the issue belong to
%{seed.issue.summary}

The summary of the current element of the issue list when using the mode "Multiple issues based on an issue list"

%{seed.text}The text of the current element of the text list when using the mode "Multiple issues based on a text list"
%{seed.number}The value of the current number when using the mode "Multiple issues based on a number"

%{system.currentUser}

The current user (executing the post function)


Numbers vs. text


Field codes must always be enclosed by curly brackets but if they are used for text-strings, the brackets must be preceded by a percent sign %

  • Numeric fields can be referenced as numbers using the following notation: {issue.somenumberfield} . ((info) no preceding % sign)
    • If the field is not set or doesn't return a number (e.g. if the issue summary equals "Issue's summary" and you enter {issue.summary}  ), it is evaluated to null .
  • Text fieldsAny field type or data type can be transformed to text, so any field can be referenced as a text-string value using the following notation:  %{issue.somefield}
    • If a field has no value (null), an empty text will be returned.
  • Cascading Select fields are treated as text fields, where i is the index that represents the level to be accessed. ( i = 0 is used for base level) are notated as %{issue.somefield.i}


For some fields not only their value can be returned, but also the respective IDThis ID is typically used when writing a field value, but it can also be used when reading a field value.

If a custom field is able to return an ID it can be accessed using the field code %{somefield.id} . The column ID in the table below shows a value for the respective field, if applicable.


Readable fields


Issue related fields can belong to an issue or it's parent. In case you want to retrieve the value of the parent issue, "issue" has to be replaced "parent" as in  %{parent.summary}

In case, a field is not set (or even non-existent), this field is evaluated to null , i.e. an empty text.

Issue-related fields
Field nameField codeTypeOutputExample output
Affects version/s%{issue.versions}

TEXT

Comma separated list of version namesVersion 1.0,Version 1.2
Affects version/s ID

{issue.versions.id}

NUMBER LIST

Comma separated list of version IDs

10010,10020,10030

Number of affects version/s

{issue.versions.length}

NUMBER

Number of affected versions in current issue3
Assignee

%{issue.assignee}

TEXT

The Atlassian account ID of the user who has the issue assigned10007
Assignee's full name

%{issue.assignee.displayName}

TEXT

Name and surname of the user who currently has the issue assignedAlbert Einstein
Assignee's email

%{issue.assignee.email}

TEXT

Email address of the user who currently has the issue assignedalbert.einstein@yahoo.com
Attachments

%{issue.attachments}

TEXT

Comma separated list of file names of all files attached to the issuefile1.txt,readme.pdf,screenshot.png
Number of attachments

{issue.attachments.length}

NUMBER

Number of files attached to current issue3
Component/s

%{issue.components}

TEXT

Comma separated list of component namesWeb Site,Authenticator,Statistics
Component/s ID

{issue.components.id}

NUMBER LIST

Comma separated list of component IDs10010,10020,10030
Component/s leads

%{issue.components.leads}

TEXT

Comma separated list of the Atlassian account IDs of the leads for the components557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554,765428:168p0983-5987-444e-80e4-1160dd57g114
Date and time of creation

%{issue.created}

TEXT

Date and time when issue has been created.

It is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ 

2019-04-01T14:19:07.060+0200
Creator

%{issue.creator}

TEXT

Atlassian account ID of the user who actually creates the issue in JIRA765428:168p0983-5987-444e-80e4-1160dd57g114
Creator's full name

%{issue.creator.displayName}

TEXT

Name and surname of the user who actually created the issue in JIRARichard Feynman
Creator's email

%{issue.creator.email}

TEXT

Email address of the user who actually created the issue in JIRArichard.feynman@gmail.com
Description

%{issue.description}

TEXT

Issue descriptionTake your Jira to the next level by using JWT for Jira Cloud
Due date

%{issue.dueDate}

TEXT

Field that stores a date with no time part and is used to schedule issues. 

It is formatted as follows: YYYY-MM-DD

2019-10-22
Environment

%{issue.environment}

TEXT

Field to describe the environment where the issue has occurredTake your Jira to the next level by using JWT for Jira Cloud
Fix version/s

%{issue.fixVersions}

TEXT

Comma separated list of fix version names1.0,2.0,2.1
Fix version/s ID

{issue.fixVersions.id}

NUMBER LIST

Comma separated list of fix versions IDs10010,10020,10030
Number of fix version/s

{issue.fixVersions.length}

NUMBER

Number of fixed versions in current issue5
Issue ID

{issue.id}

NUMBER

ID of the current issue10001
Issue key

%{issue.key}

TEXT

Issue key of the current issueCRM-25
Issue type

%{issue.issueType}

TEXT

Name of issue's Issue Type in the user's language set in his profile

Improvement 

Issue type ID

{issue.issueType.id}

NUMBER

ID of issue's Issue Type

10056

Labels

%{issue.labels}

TEXT

Comma separated list with all the labels of the issueweb,customer,java,mobile
Number of labels

{issue.labels.length}

NUMBER

Number of labels in current issue4
Last comment

%{issue.lastComment}

TEXT

Last comment entered in the issueTake your Jira to the next level by using JWT for Jira Cloud
Last commenter

%{issue.lastComment.author}

TEXT

Atlassian account ID of the user who entered the last comment in the issue557068:145e0983-5707-439c-80e4-1160dd57g114
Issue status

%{issue.status}

TEXT

Name of current status of the issue in the user's language set in his profileOpen
Issue status ID%{issue.status.id}

NUMBER

ID of current status of the issue10100
Issue status category

%{issue.status.category}

TEXT

Name of the category in the user's language set in his profileDone
Previous issue status

%{issue.status.previous}

TEXT

Name of the status the issue was just before current one

The name is shown in the user's language set in his profile

Closed 
Available target statuses%{issue.status.achievable}

TEXT

A comma-separated list with status names In Progress,Resolved,Closed
Keys of linked issues

%{issue.links}

TEXT

Comma separated list of issue keysCRM-13,HR-25,SD-12
Number of linked issues

{issue.links.length}

NUMBER

Number of issues linked to current issue3
Original estimate

%{issue.originalEstimate}

TEXT

Time originally estimated for the issue expressed in the format which is defined in "Time display format" in the "Time tracking settings" for Issues

3h 30m
Original estimate (minutes){issue.originalEstimate}NUMBER


Time originally estimated for the issue expressed in minutes

It is a real number, so it may have a non-zero fractional part

210
Remaining estimate

%{issue.remainingEstimate}

TEXT

Remaining time estimated for the issue expressed in the format which is defined in "Time display format" in the "Time tracking settings" for Issues

2h 45m
Remaining estimate (minutes){issue.remainingEstimate}

NUMBER

Remaining time estimated for the issue expressed in minutes

It is a real number, so it may have a non-zero fractional part

165
Total time spent (minutes)

{issue.timeSpent}

NUMBER

Work time currently spent at the issue expressed in minutes

It is a real number, so it may have a non-zero fractional part

90
Priority

%{issue.priority}

TEXT

Name of the priority in the user's language set in his profileCritical
Priority ID

{issue.priority.id}

NUMBER

ID of the priority the issue belongs to10010
Project

%{issue.project}

TEXT

Project Key of the project the issue belongs toHR
Project ID

{issue.project.id}

NUMBER

Project ID of the project the issue belongs to10100
Project key

%{issue.project.key}

TEXT

Project Key of the project the issue belongs to (identically to Project, i.e %{issue.project})HR
Project name

%{issue.project.name}

TEXT

Name of the project the issue belongs toCustomer Relationship Management
Project description

%{issue.project.description}

TEXT

Field description of the project the issue belongs toTake your Jira to the next level by using JWT for Jira Cloud
Project URL

%{issue.project.url}

TEXT

Field URL of the project the issue belongs tohttps://www.decadis.de/x
Project category

%{issue.project.category}

TEXT

Name of the Category of the project the issue belongs toTake your Jira to the next level by using JWT for Jira Cloud
Project lead

%{issue.project.lead}

TEXT

Atlassian account ID of the user who leads the project the issue belongs to557068:145e0983-5707-439c-80e4-1160dd57g114
Project lead's full name

%{issue.project.leadDisplayName}

TEXT

Name and surname of the user who leads the project the issue belongs toGalileo Galilei
Project lead's email

%{issue.project.leadEmail}

TEXT

Email address of the user who leads the project the issue belongs togalileo.galilei@me.com
Reporter

%{issue.reporter}

TEXT

Atlassian account ID of the user who reported the issue557068:145e0983-5707-439c-80e4-1160dd57g114
Reporter's full name

%{issue.reporter.displayName}

TEXT

Name and surname of the user who created the issueAlbert Einstein
Reporter's email

%{issue.reporter.email}

TEXT

Email address of the user who created the issuealbert.einstein@yahoo.com
Resolution

%{issue.resolution}

TEXT

The name of the resolution currently set at the issue. The name of the resolution is shown in the user's language set in his profileWon't fix

Date and time of resolution

%{issue.resolutionDate}

TEXT

Date and time of the most recent update of field Resolution.

It is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ 

2019-04-01T14:19:07.060+0200
Security level

%{issue.securityLevel}

TEXT

Name of the security level the issue currently hasClassified
Security level ID

{issue.securityLevel.id}

NUMBER

ID of the security level the issue currently has10001
Keys of sub-tasks

%{issue.subtasks}

TEXT

Comma separated list of issue keysCRM-23,CRM-26,CRM-31
Number of sub-tasks

{issue.subtasks.length}

NUMBER

Number of sub-tasks of current issue3
Summary

%{issue.summary}

TEXT

The issue summaryTake your Jira to the next level by using JWT for Jira Cloud
Available transitions

%{issue.transitions.achievable}

TEXT

A comma separated list with the names of transitions with origin in current issue status

Start Progress,Resolve Issue,Close Issue


Date and time of last update

%{issue.updated}

TEXT

Date and time of the most recent issue update

It is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ

2019-04-01T14:19:07.060+0200
Number of votes received

{issue.votes}

NUMBER

Number of votes received by the issue5
Date and time of latest status change

%{issue.lastStatusChange}

TEXT

Date and time of the most recent status change in the issue. 

It is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ

2019-04-01T14:19:07.060+0200


Watchers

%{issue.watcher}

TEXT

Comma separated list of Atlassian account IDs of current watchers of the issue557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554


Issue-related custom fields

The field codes for all custom fields are notated in the following format:  %{issue.cfnnnnn},  where  nnnnn  contains the Jira  custom field ID.

Below you will find a table of all available custom field types instead of their names. 


Custom field TypeOutputExample outputID

Checkboxes 

TEXT

List of the Checkbox values which were chosen out of multiple values using checkboxesCheckbox 1,Checkbox 210101

Date Picker

NUMBER

A custom field that stores dates and uses a date picker (no time part). 

It is formatted as follows: YYYY-MM-DD

2020-04-22

Date Time Picker 

NUMBER

A custom field that stores dates with a time component.

It is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ

2020-04-23T14:26:00.000+0100

Days since last comment 

NUMBER

Date/time since last comment (restricted comments are considered on a per user basis)2

Domain of Assignee

TEXT

The domain name of the assigneedecadis.de

Domain of Reporter

TEXT

The domain name of the reporteratlassian.com

Group Picker (single group)

TEXT

A group nameadmin

Group Picker (multiple groups)

TEXT

Comma separated list of group namesadmin,jira-developers

Labels

TEXT

Comma separated list of labelsdevelopment,test

Last commented by a User Flag

BOOLEAN

Displays true if last commenter who is not a JIRA developer (jira-developers group member)true

Last public comment date

DATE_TIME

Date/time of last public comment (restricted comments are ignored)Thu Feb 13 10:34:55 UTC 2020

Number Field

NUMBER

A custom field that stores numbers (floating point)2.7181

Number of attachments

NUMBER

A custom field that stores the number of attachments for an issue5

Number of comments

NUMBER

A custom field that stores the number of comments for an issue7

Participants of an issue

USER LIST

Displays reporter, current assignee and all commenters of the issue as a comma separated list of Atlassian account IDs557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554

Project Picker (single project)

TEXT

A custom field for storing the name of a single projectDevelopment Project10100

Radio Buttons

TEXT

A custom field which stores an option out of a list of radio buttonsRadio 110166

Select list (cascading)

TEXT

A custom field consisting of two select lists; the value is displayed as first (parent) value and second (child) value, separated by a commaParent,child10051, 10034

Select List (multiple choices)

TEXT LIST

A comma separated list of the selected values out of a list of optionsOption1,Option310041, 10042

Select List (single choice)

TEXT

The selected option from a list of optionsOption 210042

Text Field (multi-line)

TEXT

The multi-line text area is displayed

A text with a

couple of lines.


Text field (single line)

TEXT

The content of a single line text fieldOne-liner

URL Field

TEXT

A single URLapps.decadis.net

Username of last updater or commenter

TEXT

Shows the Atlassian account ID of the last updater or commenter depending on which happened most recently777068:145e0983-5707-439c-80e4-1160dd57x554

User Picker (single user)

TEXT
 

The Atlassian account ID of the user which is stored in the custom field557068:145e0983-5707-439c-80e4-1160dd57g114

User Picker (multiple users)

TEXT

The Atlassian account IDs of the users which are stored in the custom field557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554

Version Picker (single version)

TEXT

The name of version which is stored in this custom fieldVersion 1.210010

Version Picker (multiple versions)

TEXT

The names of the versions which are stored in this custom field as a comma separated listVersion 1.0,Version 1.210010, 10011
Jira Software fields

If Jira Software is installed on your Jira instance, you can retrieve the data stored in the Jira Software related field with Jira Workflow Toolbox for Jira Cloud as well. You can access those, like any other custom field in your instance, i.e. %{issue.cfnnnn},  where nnnnn contains the Jira custom field ID.


Field nameTypeOutputExample outputID
Epic Color

TEXT

A text which represents the color which is defined for the Epic (only available if Issue type equals "Epic")ghx-label-2
Epic Link

TEXT

The issue key of the Epic to which the issue is linked - if it is not linked to an Epic, the value is empty (only available for non-epic Issue types)PRJ-2
Epic Name

TEXT

A short name to identify this epic (only available if Issue type equals "Epic")This is my Epic's name
Epic Status

TEXT

Epic Status field for Jira Software use only (only available if Issue type equals "Epic")To Do10016
Rank

TEXT

Global Rank field for Jira software use only0|i0016n:
Sprint

TEXT LIST

Jira Software Sprint fieldFirst sprint,Second sprint1,2
Story point estimate

NUMBER

Measurement of complexity and/or size of a requirement40
System-related fields
Field nameField codeTypeOutputExample output
Current user

%{system.currentUser}

USER

Atlassian account ID of the user who is executing the event777068:145e0983-5707-439c-80e4-1160dd57x554
Current user's full name

%{system.currentUser.displayName}

TEXT

Name and surname of the user who is executing the eventIsaac Newton
Current user's email

%{system.currentUser.email}

TEXT

Email address of the user who is logged inisaac.newton@gmail.com
Current date and time

%{system.currentDateTime}

DATE_TIME

Current date and time of Jira server's clock

When cast to text, it is formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ

2019-04-01T14:19:07.060+0200

JIRA base URL

%{system.baseUrl}

TEXT

Returns the base URL of current JIRA instancehttps://jwt-cloud.atlassian.net


Writable fields


Writable fields can be updated by JWT for Jira Cloud post functions. All writable fields are also readable (see list above).

Issue-related fields
Field nameField code

Allowed value TEXT

Allowed value NUMBER

Example input
Affects Version/s%{issue.versions.id}
Comma separated list of version IDs10054, 10056
Assignee

%{issue.assignee}

The Atlassian account ID of the issue assignee
557068:145e0983-5707-439c-80e4-1160dd57g114
Component/s

%{issue.components.id}


Comma separated list of component IDs10000, 10001
Description

%{issue.description}

Unlimited text textNumbers are cast to textTake your Jira to the next level by using JWT for Jira Cloud
Due date

%{issue.dueDate}

Date in the form YYYY-MM-DD
2019-10-22
Environment

%{issue.environment}

Unlimited textNumbers are cast to textTake your Jira to the next level by using JWT for Jira Cloud
Fix version/s

%{issue.fixVersions.id}


Comma separated list of fixed version IDs10007, 10000
Issue type

%{issue.issueType}


ID of issue's Issue Type 

10003

Labels

%{issue.labels}

Comma separated list of labels. If a label doesn't exist, it will be created.Numbers are cast to textweb, customer, java, mobile
Original estimate (minutes)

%{issue.originalEstimate}

Cast from text to number will be attemptedNumber of minutes60
Priority

%{issue.priority.id}


ID of the priority10004
Project

%{issue.project.id}


ID of the project10200
Remaining estimate (minutes)

%{issue.remainingEstimate}

Cast from text to number will be attemptedNumber of minutesTake your Jira to the next level by using JWT Cloud
Reporter

%{issue.reporter}

The Atlassian account ID of the user who reported the issue. This field is editable, while Creator field isn't.
557068:145e0983-5707-439c-80e4-1160dd57g114
Resolution

%{issue.resolution.id}


ID of the resolution that shall be set10200

Security Level

%{issue.securityLevel.id}


ID of a Security Level10010
Summary

%{issue.summary}

Text trimmed to 255 charactersNumbers are cast to textTake your Jira to the next level by using JWT for Jira Cloud
Issue-related custom fields

If options are defined for a custom field, you can only choose those ones which are available in the global context.

The field codes for all custom fields are notated in the following format:  %{issue.cfnnnnn},  where  nnnnn  contains the Jira  custom field ID.

Below you will find a table of all available custom field types instead of their names. 


Custom field type

Allowed value TEXT

Allowed value NUMBER

Example input

Checkboxes   


Comma separated list of IDs for the options available for this custom field10003,10004

Date Picker

Date (without time part) as a text in the format YYYY-MM-DD


2020-04-22

Date Time Picker 

Date with time part as a text in the format YYYY-MM-DDTH24:MM:SS.msTZ


2020-04-23T14:26:00.000+0100

Group Picker (single group)

Text which contains a group name
admin

Group Picker (multiple groups)

Text list which contains a comma separated list of group names
admin, jira-developers

Labels

Text list which contains a comma separated list of labels defined for this field


development,test

Number Field


A valid floating number12.12

Project Picker (single project)


A valid project ID10045

Radio Buttons


An ID for the one of the options available for this custom field10012

Select list (cascading)


IDs for parent and child for this select list which are separated by a comma10034,10555

Select List (multiple choices)


A comma separated list of IDs for the options available for this custom field

Select List (single choice)


An ID for the one of the options available for this custom field

Text Field (multi-line)

Text (with line breaks) 

A text with a

couple of lines.

Text Field (single line)

Single-line text                                       
One-liner

URL Field

A valid URL                                              


apps.decadis.net

User Picker (single user)


A valid Atlassian account ID557068:145e0983-5707-439c-80e4-1160dd57g114

User Picker (multiple users)


A list of valid Atlassian account ID separated by a comma557068:145e0983-5707-439c-80e4-1160dd57g114,777068:145e0983-5707-439c-80e4-1160dd57x554

Version Picker (single version)


A version IDVersion 1.2.0

Version Picker (multiple versions)


A list of version IDs, separated by a commaVersion 1.0,Version 1.2
Jira Software fields

If Jira Software is installed on your Jira instance, you can set Jira Software related fields with Jira Workflow Toolbox for Jira Cloud as well. You can access those, like any other custom field in your instance, i.e. %{issue.cfnnnn},  where nnnnn contains the Jira custom field ID.


Custom field type

Allowed value TEXT

Allowed value NUMBER

Example input
Epic LinkIssue key of the Epic to which the issue is linked
PRJ-2
Epic NameName of the Epic
This is my Epic's name
Sprint
ID of the sprint2
Story point estimate
Floating point number which represents the complexity and/or size of a requirement34

Please note that the field you want to set must be located on the corresponding screen and the executing user must have all the necessary permissions and access to the issue.