Page History
| Page properties | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||
|
| UI Text Box | ||||
|---|---|---|---|---|
| ||||
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:
- readable fields
- writable fields
- virtual fields
- issue, project and user properties
Check out the following pages to familiarize yourself with field codes.
| UI Children |
|---|
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 | 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. |
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:
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). INSERT SCREENCAST
|
| UI Expand | ||
|---|---|---|
| ||
|
| UI Text Box | ||
|---|---|---|
| ||
Field codes for Jira standard or system fields will display the attribute in a legible form like All selected custom fieldsfield 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 |
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 % .
- Number fields can be referenced as numbers using the following notation: {issue.
somenumberfield}. (
no preceding % sign)- If a field is not set or does not return a number (e.g. a text field ), it is evaluated to
null.
- If a field is not set or does not return a number (e.g. a text field ), it is evaluated to
- String fields : Any field type or data type is susceptible of being 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 string will be returned.
- If a field has no value (
- Cascading Select fields are treated as string 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}
| UI Text Box | ||
|---|---|---|
| ||
A complete list of all available data types can be found here. |
| Anchor | ||||
|---|---|---|---|---|
|
Readable fields
The list below contains all fields that can be read by JWT.
| expanded | true |
|---|---|
| title | Issue-related fields |
Transition's comment Status colour Red title WORKFLOWS ONLY
| Status | ||||
|---|---|---|---|---|
|
{issue.versions.id}
| Status | ||||||
|---|---|---|---|---|---|---|
|
10010,10020,10030
{issue.versions.length}
%{issue.assignee}
%{issue.assignee.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.assignee.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.attachments}
{issue.attachments.length}
%{issue.cf10100}
| Status | ||||
|---|---|---|---|---|
|
All custom fields will be notated like this
%{issue.cfnnnnn} where nnnnn contains the Jira custom field id , that can be determined of the Jira custom field administration{issue.cf10133}All custom fields will be notated like this
{issue.cfnnnnn} where nnnnn contains the Jira custom field id , that can be determined of the Jira custom field administration%{issue.components}
{issue.components.id}
| Status | ||||||
|---|---|---|---|---|---|---|
|
%{issue.components.leads}
{issue.created}
Date and time when issue has been created.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.creator}
%{issue.creator.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.creator.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.description}
| Status | ||||
|---|---|---|---|---|
|
%{issue.dueDate}
Field that stores a date with no time part and is used to schedule issues.
It's formatted as follows: YYYY-MM-DD
%{issue.environment}
| Status | ||||
|---|---|---|---|---|
|
%{issue.fixVersions}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.fixVersions.length}
{issue.id}
%{issue.key}
| Status | ||||
|---|---|---|---|---|
|
%{issue.issueType}
Improvement
10056
%{issue.labels}
{issue.labels.length}
%{issue.lastComment}
| Status | ||||
|---|---|---|---|---|
|
%{issue.lastComment.author}
%{issue.status}
%{issue.status.id}%{issue.status.category}
%{issue.status.previous}
Name of the status the issue was just before current one
The name is shown in the user's language set in his profile
%{issue.links}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.links.length}
{issue.originalEstimate}
Time originally estimated for the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
{issue.remainingEstimate}
Remaining time estimated for the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
{issue.timeSpent}
Work time currently spent at the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
%{issue.priority}
%{issue.project}
%{issue.project.key}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project})| Status | ||||
|---|---|---|---|---|
|
%{issue.project.description}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.url}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.category}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.lead}
%{issue.project.lead.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.lead.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.reporter}
%{issue.reporter.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.reporter.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.resolution}
{issue.resolutionDate}
Date and time of the most recent update of field Resolution.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.securityLevel}
%{issue.subtasks}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.subtasks.length}
%{issue.summary}
| Status | ||||
|---|---|---|---|---|
|
%{issue.transitions.achievable}
| Status | ||||
|---|---|---|---|---|
|
Start Progress,Resolve Issue,Close Issue
%{issue.updated}
Date and time of the most recent issue update
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
{issue.votes}
%{issue.lastStatusChange}
Date and time of the most recent status change in the issue.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.watcher}
| title | Component fields |
|---|
| Status | ||||||
|---|---|---|---|---|---|---|
|
10010,10020,10030
{issue.versions.length}
%{issue.assignee}
%{issue.assignee.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.assignee.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.attachments}
{issue.attachments.length}
%{issue.cf10100}
| Status | ||||
|---|---|---|---|---|
|
All custom fields will be notated like this
%{issue.cfnnnnn} where nnnnn contains the Jira custom field id , that can be determined of the Jira custom field administration{issue.cf10133}All custom fields will be notated like this
{issue.cfnnnnn} where nnnnn contains the Jira custom field id , that can be determined of the Jira custom field administration%{issue.components}
| Status | ||||||
|---|---|---|---|---|---|---|
|
%{issue.components.leads}
%{issue.created}
Date and time when issue has been created.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.creator}
%{issue.creator.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.creator.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.description}
| Status | ||||
|---|---|---|---|---|
|
%{issue.dueDate}
Field that stores a date with no time part and is used to schedule issues.
It's formatted as follows: YYYY-MM-DD
%{issue.environment}
| Status | ||||
|---|---|---|---|---|
|
%{issue.fixVersions}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.fixVersions.length}
{issue.id}
%{issue.key}
| Status | ||||
|---|---|---|---|---|
|
%{issue.issueType}
Improvement
10056
%{issue.labels}
{issue.labels.length}
%{issue.lastComment}
| Status | ||||
|---|---|---|---|---|
|
%{issue.lastComment.author}
%{issue.status}
%{issue.status.id}%{issue.status.category}
%{issue.status.previous}
Name of the status the issue was just before current one
The name is shown in the user's language set in his profile
%{issue.links}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.links.length}
{issue.originalEstimate}
Time originally estimated for the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
{issue.remainingEstimate}
Remaining time estimated for the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
{issue.timeSpent}
Work time currently spent at the issue expressed in minutes
It's a real number, so it may have a non-zero fractional part
%{issue.priority}
%{issue.project}
%{issue.project.key}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project})| Status | ||||
|---|---|---|---|---|
|
%{issue.project.description}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.url}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.category}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.lead}
%{issue.project.lead.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.project.lead.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.reporter}
%{issue.reporter.displayName}
| Status | ||||
|---|---|---|---|---|
|
%{issue.reporter.email}
| Status | ||||
|---|---|---|---|---|
|
%{issue.resolution}
%{issue.resolutionDate}
Date and time of the most recent update of field Resolution.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.securityLevel}
%{issue.subtasks}
| Status | ||||||
|---|---|---|---|---|---|---|
|
{issue.subtasks.length}
%{issue.summary}
| Status | ||||
|---|---|---|---|---|
|
%{issue.transitions.achievable}
| Status | ||||
|---|---|---|---|---|
|
Start Progress,Resolve Issue,Close Issue
%{issue.updated}
Date and time of the most recent issue update
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
{issue.votes}
%{issue.lastStatusChange}
Date and time of the most recent status change in the issue.
It's formatted as follows: YYYY-MM-DDTH24:MM:SS.msTZ
%{issue.watcher}
