On this page |
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. |
Field codes will be automatically added to your expression when you insert them anywhere using the expression parser field code injector.
SCREENCAST, but a better one
Potentially with text / like the getting started video?
Field codes for Jira standard or system fields will display the attribute in a legible form like All custom fields 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.
|
The summary of the parent issue. | |
seed | The element currently being processed by a workflow function or automation rule that is capable of analyzing multiple elements (e.g. Create issue post function or the Create issue action). Elements can either be issues, texts or numbers, depending in your configuration. Read more about Seeds. |
The summary of a seed issue.
The currently processed element of the text or number list. | |
function | Some JWT expression parser functions creating its own issue context and itterate through it. To access this context, the function origin can be used. |
Returns a list of all subtasks of the current issue that have a due date set. | |
created.parent | The parent of the newly created issue within the current workflow function
|
The summary of the newly created issue's parent. |
An issue is tied to a workflow. This is why most field codes in JWT workflow functions have their issue context. Automation rules are not tied to individual issues. This is why sometimes it is necessary to define their context separately.
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) |
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 text will be returned.
%{issue.somefield.i}
A complete list of all available data types can be found here. |
Check out the following pages to familiarize yourself with field codes.
or search for a specific field code:
|