Page History
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
On this page
|
Overview
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.
| UI Text Box | ||
|---|---|---|
| ||
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:
- readable fields
- writable fields
- virtual fields
- issue, project and user properties
Field code notation
Depending on the context in which they are being used, field codes will contain a prefix following this notation: {origin.field}.
What is a context?
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.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). | |||||
Only valid for sub-tasks.| UI Expand | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
These additional contexts are available for automation rules:
|
These additional contexts are available for automation rules:
| Context | Description | Example |
|---|---|---|
trigger | The issue, user, version, component or project event that triggers the execution of the rule. | %{trigger.issue.description} The description of the issue triggering the automation rule. |
selector | The issue currently being processed by a selector (e.g. an issue returned by a JQL query). | %{selector.issue.cf10021} The value of the custom field with the ID 10021 from the issue currently being processed by a selector. |
| UI Text Box | ||
|---|---|---|
| ||
The additional contexts can be used in combination with the standard contexts (e.g. parent, seed). Example: %{trigger.parent.summary} |
