Expr allows you to access item properties within formulas, using the following notation: item.property. The available properties depend on the item type.
See below for a complete list of item types and their supported properties.
Issue
Accessible via: item, subtasks, parent, epic, epicStories
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
If wiki markup is used, the value is the marked up text (not HTML) |
|
|
Text |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Number (Boolean) |
|
|
|
Number |
|
|
|
Number |
|
|
|
Number (Date) |
|
|
|
Number (Duration) |
|
|
|
Number (Duration) |
|
|
|
Number (Duration) |
|
|
|
Text |
Issue's URL |
|
|
Array<Issue> |
|
|
|
Issue |
Parent issue, if this is a sub-task |
|
|
User |
|
|
|
User |
|
|
|
User |
|
|
|
IssueType |
|
|
|
Priority |
|
|
|
Project |
|
|
|
Resolution |
|
|
|
Status |
|
|
|
Array<Version> |
|
|
|
Array<Version> |
|
|
|
Array<Component> |
|
|
|
Array<Attachment> |
|
|
|
Array<Text> |
|
|
|
Variable |
Custom field value for custom field identified by its ID. |
|
|
Variable |
Custom field value for the field identified by its name. |
IssueType
Accessible via: issueType
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Number |
Used to sort issue types. |
|
|
Number (Boolean) |
True if the type is a sub-task type. |
User
Accessible via: assignee, reporter, creator
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
User's login name |
|
|
Text |
User key (used internally by Jira) |
|
|
Text |
User's full name |
|
|
Text |
User's email (if available) |
|
|
Number (Boolean) |
True if the user is active |
Attachment
Accessible via: attachments
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Number (Date/Time) |
|
|
|
Number |
|
|
|
Text |
|
|
|
User |
|
Comment
Accessible via: comments
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
Component
Accessible via: components
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
User |
|
Issue Link
Accessible via: issueLinks
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Issue |
|
|
|
Issue |
|
|
|
Number |
|
|
|
IssueLinkType |
|
Remote Link
Accessible via: remoteLinks
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Issue |
Can also use |
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
Server name for Atlassian applications |
|
|
Text |
URL for |
|
|
Text |
Title for |
|
|
Text |
Special string describing links to Atlassian apps. For example, it’s |
|
|
Text |
This and below are the attributes of a remote issue, if this link references an issue on a remote Jira |
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
Issue Link Type
Accessible via: issueLinks.type
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Number (Boolean) |
|
|
|
Number (Boolean) |
|
Option
Accessible via: "select" custom fields
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Number (Boolean) |
|
|
|
Text |
|
|
|
Option |
Useful with cascading select fields |
|
|
Number |
|
Priority
Accessible via: priority
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Number |
|
Project
Accessible via: project
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
|
|
User |
|
|
|
Text |
|
Resolution
Accessible via: resolution
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Number |
|
Sprint
Accessible via: sprint
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
Status
Accessible via: status
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
Version
Accessible via: affectsVersion, fixVersion
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Project |
|
|
|
Number (Boolean) |
|
|
|
Number (Boolean) |
|
|
|
Number (Date) |
|
|
|
Number (Date) |
|
Work Logs
Accessible via: workLogs
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
|
|
Number (Date/Time) |
|
|
|
Number (Duration) |
|
Change History Group
Accessible via: history
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
Alias for time |
|
|
Number (Date/Time) |
Alias for time |
|
|
Issue |
|
|
|
Issue |
Alias for issue |
|
|
Array<Change History Item> |
|
|
|
Array<Change History Item> |
Alias for changes |
Change History Item
Accessible via: history.changes
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
The name or id of the changed field. Can be used in ACCESS and HISTORICAL_VALUE functions. |
|
|
Variable |
Previous value, which corresponds to the field's type. May be a text value if the value of the field type is impossible to retrieve. |
|
|
Text |
Text representation of the previous value. This can sometimes be faster than using "from". |
|
|
Variable |
Changed value, which corresponds to field's type. May be a text value if the value of the field type is impossible to retrieve. |
|
|
Text |
Text representation of the changed value.This can sometimes be faster than using "to". |
|
incremental |
Number (Boolean) |
When true, the field's "from" and "to" indicate a change of a single value in a multi-valued field. (Add, remove, or change) |
|
|
Change History Group |
The Change History Group parent entity. Can be used to access the time and author of the change item. |