The following tokens can be used as part of texts in config screen.
Issue Fields
|
Token |
Return Type |
Description |
Sample Value |
Can be followed by other tokens? |
|---|---|---|---|---|
|
{issue} |
Issue |
References the current issue. If used by itself, returns the key of the issue. |
ABC-123 |
Y |
|
{issue.affectsversion} |
Text |
Affected Version(s) field on the issue. Values are separated by comma if there are more than one. |
v1, v2, v3 |
|
|
{issue.assignee} |
User |
References the Assignee field of the current issue. If used by itself, returns the username of the assignee. |
john.doe |
Y |
|
{issue.components} |
Text |
Components field of the current issue |
Component 1, Component 2 |
|
|
{issue.created} {issue.createddate} |
Text |
Created Date of the issue. |
2019-08-27 14:58 |
|
|
{issue.creator} |
User |
Creator field of the issue. If used by itself, returns the username of the assignee. |
john.doe |
Y |
|
{issue.description} |
Text |
Description field of the issue |
Some sample description text |
|
|
{issue.due} {issue.duedate} |
Text |
Due Date field of the issue |
2019-08-27 |
|
|
{issue.environment} |
Text |
Environment field of the issue |
Some sample environment text |
|
|
{issue.fixversion} |
Text |
Fix Version(s) field of the issue |
v1, v2, v3 |
|
|
{issue.issuetype} {issue.type} |
Text |
IssueType of the issue |
Task |
|
|
{issue.key} |
Text |
Issue Key of the issue |
ABC-123 |
|
|
{issue.labels} |
Text |
Label(s) field of the issue |
Label 1, Label 2, Label 3 |
|
|
{issue.parent} |
Issue |
Parent issue of the issue. If used by itself, returns the key of the parent. If there is no parent (the current issue is not a subtask) returns empty. |
ABC-122 |
Y |
|
{issue.parentkey} |
Text |
Key field of parent issue. If there is no parent (the current issue is not a subtask) returns empty. |
ABC-122 |
|
|
{issue.priority} |
Text |
Priority field of the issue |
High |
|
|
{issue.project} |
Project |
Project that the issue belongs to. If used by itself, return the project key. |
ABC |
Y |
|
{issue.projectkey} |
Text |
Key of the project that the current issue belongs to. |
|
|
|
{issue.reporter} |
User |
Reporter field of the issue If used by itself, returns the username of reporter. |
jane.doe |
Y |
|
{issue.resolution} |
Text |
Resolution field of the issue. |
Done |
|
|
{issue.resolutiondate} {issue.resolved} |
Text |
Resolution Date of the issue |
2019-08-27 14:58 |
|
|
{issue.status} |
Text |
Status of the issue |
In Progress |
|
|
{issue.summary} |
Text |
Summary of the issue |
My sample issue |
|
|
{issue.updated} {issue.updateddate} |
Text |
Updated Date field of the issue |
2019-08-27 14:58 |
|
|
{issue.<cf_12345>} (non JQL Issue Select custom field) |
Text |
The custom field with ID 12345 of the issue. The field ID can be any field defined in the system. |
Some custom field value |
|
|
{issue.<cf_98765>} (JQL Issue Select custom field) |
Issue(s) |
The issue(s) selected in JQL Issue Select field with ID 98765. 98765 can be the field ID of any JQL Issue Select field defined in the system (JQL Advanced Field or one of the deprecated fields). If used by itself, return the keys of the selected issue or issues. Please see Using JIS Fields in Token Strings for the advanced uses of JQL Issue Select custom field tokens. |
ABC-156, ABC-157 |
Y |
|
{issue.<cf_34567> (Single or Multi User Picker custom field) |
User |
The users(s) selected in JQL Issue Select field with ID 34567. If used by itself, return the usernames of the selected users. |
john.doe, jane.doe |
Y |
|
{issue.<cf_23456>} {Date custom field} |
Text |
The custom field of type Date with ID 23456. The field ID can be any field defined in the system. |
2019-08-27 |
|
|
{issue.<cf_45678>} {DateTime custom field} |
Text |
The custom field of type DateTime with ID 45678. The field ID can be any field defined in the system. |
2019-08-27 14:58 |
|
{issue} token and any token string that starts with {issue.} do not work on create screens because the issue is not created yet.
You can use {parent}, {project} or {currentuser} tokens and their fields on create screens.
Parent Fields
{parent} token references the parent issue. It can be followed by all the issue field tokens listed in "Issue Fields" section.
{parent} token works pretty much the same as {issue.parent} but can also be used on Create screen. {issue} token does not work on create screens because the issue is not created yet.
|
Token |
Return Type |
Description |
Sample Value |
Can be followed by other tokens? |
|---|---|---|---|---|
|
{parent} |
Issue |
Returns the parent issue of the current issue (if any) |
ABC-122 |
Y |
Project Fields
{project} token references the current project.
{project} token works pretty much the same as {issue.project} but can also be used on Create screen. {issue} token does not work on create screens because the issue is not created yet.
|
Token |
Return Type |
Description |
Sample Value |
Can be followed by other tokens? |
|---|---|---|---|---|
|
{project} |
Project |
Returns the current project. |
ABC |
Y |
|
{project.key} |
Text |
Returns the key of the current project |
ABC |
|
|
{ project.id } |
Text |
Returns the ID of the current project |
10123 |
|
|
{ project.name } |
Text |
Returns the name of the current project |
My sample project |
|
|
{project.lead} |
User |
Returns the Project Lead user of the current project. If used by itself, return the username of the project lead user. |
john.doe |
Y |
|
{project.components} |
Text |
Returns all the components defined in the current project |
Component 1, Component 2, Component 3 |
|
|
{project.versions} |
Text |
Returns all the versions defined in the current project |
v1, v2, v3 |
|
User Fields
Any user object (that is returned by a system or a custom field token) can be followed by the tokens below.
The samples below reference {issue.assignee} but can be replaced by any token string that returns a user.
|
Token |
Return Type |
Description |
Sample Value |
Can be followed by other tokens? |
|---|---|---|---|---|
|
{issue.assignee} |
User |
Returns the user that is the assignee of the issue. If used by itself, return the username of the assignee. |
john.doe |
Y |
|
{issue.assignee.name} {issue.assignee.username} |
Text |
Returns the username of the assignee of the issue. |
john.doe |
|
|
{issue.assignee.displayname} |
Text |
Returns the Display Name of the assignee of the issue. |
John Doe |
|
|
{issue.assignee.email} |
Text |
Returns the e-mail of the assignee of the issue. |
john.doe@gmail.com |
|
|
{issue.assignee.<property_name>} |
Text |
Returns the property value of the user that is defined by property_name. Returns empty if a property with property_name is not found. |
Some property value |
|
Current User
{currentuser} is a token that returns the current logged in user. It can be followed by all the user field tokens listed in "User Fields" section.
|
Token |
Return Type |
Description |
Sample Value |
Can be followed by other tokens? |
|---|---|---|---|---|
|
{currentuser} |
User |
Returns the currently logged in user |
john.doe |
Y |