|
One of the most important features of JWT is the easy accessibility to Jira data stored in system fields, custom fields and a significant number of other virtual fields that are made available by the JWT implementation. You can access, validate, do mathematical calculations and manipulate the values found in these fields through the use of field codes . A field code is a unique identifier (key) that can be used in any parser expression. At the same time a field code is a safety feature that makes your expressions immune to custom field renaming. |
Check out the following pages to familiarize yourself with field codes.
Field codes for Jira standard or system fields will display the attribute in a legible form like All selected custom field will be notated like Once an expression has been saved, the real name will be displayed in the configuration element. The purpose of using the |
Depending on the context in which they are being used, field codes will contain a prefix following this notation :
{origin.field}
.
A context basically determines where JWT will pull data from. Available contexts (or
origins
) in JWT are:
Context | Description | Example | |
---|---|---|---|
issue
| The issue that currently being processed by a workflow function or automation rule.
|
The description of the current issue. | |
parent | The parent of the issue that is processed by a workflow post function or an automation rule. Only valid for sub-tasks. |
The summary of the parent issue. | |
seed.issue
| The issue currently being processed by a workflow function that is capable of analyzing multiple issues (e.g. subtasks()). These issues are called seed issues. Alternatively you can add ^ as a prefix. Read more about Seeds. |
The summary of a seed issue. |
These additional contexts are available for automation rules:
The prefix is a referential part of the field code and will be inserted into the expression whenever you select a field from a dropdown list (as shown below).
Find a full list of automation-only field code here: Field codes (automation-only) |
Numbers vs. text (strings)
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 % .
somenumberfield
}. ( no preceding % sign)
null
.
%{issue.somefield}.
null)
, an empty string will be returned.
%{issue.somefield.i}
A complete list of all available data types can be found here. |
Looking for a field?