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 are available for:
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 | Seed issues of the issue that is processed by a workflow post function or an automation rule. More info... |
The summary of a seed issue. | |
issue.project | |||
system | Some data does not have an issue context (e.g. the currently logged in user or the system date and time). |
The current user (e.g. executing the post function). | |
These additional contexts are available for automation rules:
|
Field codes for Jira standard or system fields will display the attribute in a legible form like All selected custom fields will be notated like The purpose of using the |
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)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
.
%{somefield}.
If a field has no value (null)
, an empty string will be returned.
Cascading Select fields, where i is the index that represents the level to be accessed. (i = 0 is used for base level) are notated as %{somefield.i}