You can 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.
Comment
Accessible via: comment, lastComment
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
Component
Accessible via: components
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
|
|
User |
|
Field History
Accessible via: {field}History, where {field} is the name of the custom field. Ex. statusHistory
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
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”. |
|
|
Number (Date/Time) |
|
Issue Link
Accessible via: issueLinks
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Issue |
|
|
|
Issue |
|
|
|
IssueLinkType |
|
Issue Link Destination
Accessible via: issueLinks.destination
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
text |
|
|
|
text |
|
|
|
Text |
|
|
|
Status |
|
|
|
Status |
|
|
|
Text |
|
|
|
Text |
|
Issue Link Source
Accessible via: issueLinks.source
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
text |
|
|
|
text |
|
|
|
Text |
|
|
|
Status |
|
|
|
Status |
|
|
|
Text |
|
|
|
Text |
|
Issue Link Type
Accessible via: issueLinks.type
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Text |
|
|
|
Text |
|
IssueType
Accessible via: issueType
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
number |
|
|
|
Number |
Used to sort issue types. |
|
|
Number (Boolean) |
True if the type is a sub-task type. |
Project
Accessible via: project
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
|
|
Text |
|
Sprint
Accessible via: sprint
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
|
|
Number |
|
|
|
text |
|
Status
Accessible via: status
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
|
|
Text |
|
User
Accessible via: assignee, reporter, creator, author
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
User's login name |
|
account |
Text |
|
|
|
Text |
|
|
|
Number (Boolean) |
True if the user is active |
Version
Accessible via: affectsVersion, fixVersion
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
Text |
|
|
|
Number |
|
|
|
Text |
|
|
|
Text |
Project name |
|
|
Number (Boolean) |
|
|
|
Number (Boolean) |
|
|
|
Number (Date) |
|
|
|
Number (Date) |
|
Work Logs (Jira)
Accessible via: jiraWorkLogs
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
Alias for startDate |
|
|
Number (Duration) |
|
|
|
Number |
|
Work Logs (Tempo)
Accessible via: tempoWorkLogs
|
Property Name |
Type |
Comments |
|---|---|---|
|
|
User |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
|
|
|
Text |
|
|
|
Number (Date/Time) |
|
|
|
Number (Date/Time) |
Alias for startDate |
|
|
Number (Duration) |
|
|
|
Number (Duration) |
|
|
|
Number |
|
Tempo Work Attributes
If you’ve created custom Tempo Work Attributes, these values can also be used in formulas: tempoworklogs.<WORKATTRIBUTEKEY> (Replace “<WORKATTRIBUTEKEY>” with the key for the work attribute you want to use.)
If you don’t know a work attribute’s key, create a column with the formula FLATTEN(tempoworklogs.workattributekeys)- this will provide a list of available work attribute keys.