Jira Issues (JQL) - Variables available in editor template
Table of Contents
When an Elements Connect field is connected to Jira issues (JQL) datasource, you don't have to select the result set attributes in the query: all the issue fields are available in the template field.
This pages lists all the variables that can be used in the template field when using a JQL datasource.
Fields
| Field | Type |
|---|---|
| assignee | User |
created | Date |
creator | User |
customfield_xxxx | Depends on the custom field. Any returned type among Date, User, Project or an Issue constant are handled |
duedate | Date |
issuetype | IssueType |
priority | Priority |
| project | Project |
| reporter | User |
resolution | Resolution |
| resolutiondate | Date |
status | Status |
| updated | Date |
Other fields are handled as text.
Alternate evaluation by data type
To any of the types listed above, you can instruct the marker to change the value evaluation.
This can be achieved by adding an extension to the name reference.
Short examples:
| Example | Extention | Result |
|---|---|---|
| {project} | <none> | Displays the project name |
| {project.key} | key | Displays the project key |
| {assignee.displayName} | displayName | Displays the assignee display name instead of the login |
Here are all the extensions by type :
Dates
Any date type can be formatted into JIRA default style:
| Extension | Example of use | Expected result | Example of output |
|---|---|---|---|
| <no extension> | {created} | same as datetime below | 21/Jul/16 9:05 AM |
| date | {created.date} | Displays the date like the Date fields with JIRA default | 21/Jul/16 |
| datetime | {created.datetime} | Displays the date like the Datetime fields with JIRA default | 21/Jul/16 9:05 AM |
User
Can be used on any field of type User (both system & custom fields).
| Extension | Example of use | Expected result | Example of output |
|---|---|---|---|
<no extension> | {assignee} | same as displayName : The user display name | Administrator |
name | {assignee.name} | The use login name | admin |
displayName | {assignee.displayName} | The user display name | Administrator |
Issue constants
Can be used on issue type, priority, resolution and status.
| Extension | Example of use | Expected result | Example of output |
|---|---|---|---|
| <no extension> | {priority} | The priority name | Major |
| id | {resolution.id} | The issue resolution id | 10400 |
| name | {status.name} | The issue status name | In Progress |
iconUrl | {issuetype.iconUrl} ( | The issue type icon url | /jira/secure/viewavatar?size=xsmall&avatarId=10400&avatarType=issuetype |
Project
| Extension | Example of use | Expected result | Example of output |
|---|---|---|---|
<no extension> | {project} | same as name: The project name | My Plugin |
id | {project.id} | The project id | 10000 |
key | {project.key} | The project key | MYPL |
| name | {project.name} | The project name | My Plugin |
Examples
| Template | Expected result |
|---|---|
<a href="/jira/browse/{project.key}">Go to {project.name} configuration</a>
| A link like this: Go to PLUGIN configuration |
Created by {creator.displayName} on {created.date}
| Created by Mike on 01/12/11 |
<div>
<img src="{issuetype.iconUrl}"/> <span>{issuetype.name}</span>
</div>
| An issue type with the issue type icon in front |