You can use Jira values to populate the grid with data in different cases:
initialise grid with data
set default values for grid columns
populate select lists with dynamic options retrieved from Jira
use custom field values in a grid: get data from a custom field which has a list of values and populate a grid with these values.
Supported values
Check the list of the supported values that you can get from Jira objects.
Basic Jira issue values
Placeholder expression | Result value | ||
---|---|---|---|
issue | |||
issue:id | id of the current issue | ||
issue:key | key of the current issue | ||
issue:summary | summary of the current issue | ||
issue:description | description of the current issue | ||
issue:logged | logged time spent working on the current issue
| ||
issue:created_date | date when the current issue has been created | ||
issue:resolution_date | resolution date of the current issue | ||
issue:updated_date | update date of the current issue | ||
issue:due_date | due date of the current issue | ||
issue:priority | priority of the current issue | ||
issue:votes | number of votes for the current issue | ||
issue:watches | number of watches for the current issue | ||
issue:workratio | percentage of work on the issue calculated by timespent/estimation | ||
time_tracking | |||
issue:time_tracking:estimate_seconds | estimate time of the current issue in seconds | ||
issue:time_tracking:remaining_seconds | remaining estimate time of the current issue in seconds | ||
issue:time_tracking:spent_seconds | spent time on the current issue in seconds | ||
issue:time_tracking:estimate | original estimate of the current issue
| ||
issue:time_tracking:remaining | remaining time of the current issue | ||
issue:time_tracking:spent | spent time on the current issue | ||
status | |||
issue:status:id | status id of the current issue | ||
issue:status:name | status name of the current issue
issue:status is equal to issue:status:name | ||
issue:status:description | status description of the current issue | ||
issue:status:url | status link of the current issue | ||
issue:status:icon_url | status link icon of the current issue | ||
status_category | |||
issue:status_category:id | id of the status category | ||
issue:status_category:name | name of the status category
issue:status_category:name is equal to issue:status_category | ||
issue:status_category:key | status category description of the current issue | ||
issue:status_category:color | status category color of the current issue | ||
issue:status_category:url | status category link of the current issue | ||
resolution | |||
issue:resolution:id | resolution id of the current issue | ||
issue:resolution:name | resolution name of the current issue
issue:resolution:name is equal to issue:resolution | ||
issue:resolution:description | description of the resolution for the current issue | ||
issue:resolution:url | resolution url of the current issue | ||
priority | |||
issue:priority:id | current issue priority id | ||
issue:priority:name | name of the priority for the current issue
issue:reporter:name is equal to issue:reporter | ||
issue:priority:description | description of the priority for the current issue | ||
issue:priority:sequence | order position of the priority for the current issue | ||
type | |||
issue:type:id | current issue type id | ||
issue:type:name | current issue type name
issue:type:name is equal to issue:type | ||
issue:type:description | current issue type description | ||
issue:type:url | current issue type url | ||
issue:type:icon_url | current issue type icon url | ||
assignee | |||
issue:assignee:id | current issue assignee id | ||
issue:assignee:url | current issue assignee url | ||
issue:assignee:name | current issue assignee name
issue:assignee:name is equal to issue:assignee | ||
issue:assignee:full_name | current issue assignee full name | ||
issue:assignee:email | current issue assignee email | ||
issue:assignee:email_domain | current issue assignee email domain | ||
issue:assignee:application_roles | current issue assignee application roles | ||
issue:assignee:application_roles:key | current issue assignee application roles keys separated by comma | ||
issue:assignee:application_roles:name | current issue assignee application roles names separated by comma | ||
issue:assignee:groups | current issue assignee groups separated by comma | ||
issue:assignee:groups:name | current issue assignee group names separated by comma | ||
reporter | |||
issue:reporter:id | current issue reporter id | ||
issue:reporter:url | current issue reporter url | ||
issue:reporter:name | current issue reporter name
issue:reporter:name is equal to issue:reporter | ||
issue:reporter:full_name | current issue reporter full name | ||
issue:reporter:email | current issue reporter email | ||
issue:reporter:email_domain | current issue reporter email domain | ||
issue:reporter:application_roles | current issue reporter application roles separated by comma | ||
issue:reporter:application_roles:key | current issue reporter application roles keys separated by comma | ||
issue:reporter:application_roles:name | current issue reporter application roles names separated by comma | ||
issue:reporter:groups | current issue reporter groups separated by comma | ||
issue:reporter:groups:name | current issue reporter groups names separated by comma | ||
components | |||
issue:components:id | current issue components ids separated by comma | ||
issue:components:name | current issue components names separated by comma
issue:components:name is equal to issue:components | ||
issue:components:description | current issue components descriptions separated by comma | ||
issue:components:url | current issue components urls separated by comma | ||
issue:components:isAssigneeTypeValid | current issue components assignee type valid | ||
fix_versions | |||
issue:fix_versions:id | current issue fix versions ids separated by comma | ||
issue:fix_versions:name | current issue fix versions names separated by comma
issue:fix_versions:name is equal to issue:fix_versions | ||
issue:fix_versions:description | current issue fix versions descriptions separated by comma | ||
issue:fix_versions:archived | current issue archived fix versions separated by comma | ||
issue:fix_versions:released | current issue released fix versions separated by comma | ||
labels | |||
issue:labels:name | current issue labels names separated by comma
issue:labels:name is equal to issue:labels | ||
attachments | |||
issue:attachments:id | current issue attachments ids separated by comma | ||
issue:attachments:filename | current issue attachments file names, separated by comma
issue:attachments:name is equal to issue:attachments | ||
issue:attachments:file_size | current issue attachments files sizes separated by comma | ||
issue:attachments:url | current issue attachments URLs separated by comma | ||
issue:attachments:content | current issue attachments links to the content, separated by comma | ||
issue:attachments:mimeType | current issue attachments MIME types separated by comma |
Parent issue values
Tip |
---|
Jira parent issue has the same values as Jira issue. You can use any of the above values either with parent or simple Jira issue. |
Placeholder expression | Result value | ||
---|---|---|---|
parent | |||
parent:id | id of the parent issue | ||
parent:key | key of the parent issue | ||
parent:summary | summary of the parent issue | ||
parent:description | description of the parent issue | ||
parent:estimate | original estimate of the parent issue
| ||
parent:logged | logged time spent working on the parent issue
| ||
parent:created_date | date when the parent issue has been created | ||
parent:resolution_date | resolution date of the parent issue | ||
parent:updated_date | update date of the parent issue | ||
parent:due_date | due date of the parent issue | ||
parent:priority | priority of the parent issue | ||
parent:votes | number of votes for the parent issue | ||
parent:watches | number of watches for the parent issue | ||
parent:workratio | percentage of work on the issue calculated by timespent/estimation |
Project level specific values
Placeholder expression | result value | ||
---|---|---|---|
project | |||
project:id | current project id | ||
project:key | current project key | ||
project:name | current project name
project:name is equal to project | ||
project:url | current project url | ||
project:description | current project description | ||
project:project_type | type of project | ||
roles | current project users roles | ||
project:roles:name | current project user roles names | ||
issue_types | |||
project:issue_types:id | current project issue types ids separated by comma | ||
project:issue_types:url | current project issue types urls separated by comma | ||
project:issue_types:description | current project issue types descriptions separated by comma | ||
project:issue_types:name | current project issue types name separated by comma | ||
project:issue_types:icon_url | current project issue types icons urls separated by comma | ||
category | |||
project:category:id | current project category id | ||
project:category:name | current project category name
project:category:name is equal to project:category | ||
project:category:description | current project category description | ||
project:category:url | current project category url | ||
lead | |||
project:lead:id | current project lead id | ||
project:lead:url | current project lead url | ||
project:lead:name | current project lead name
project:lead:name is equal to project:lead | ||
project:lead:full_name | current project lead full name | ||
project:lead:email | current project lead email | ||
project:lead:email_domain | current project lead email domain | ||
project:lead:application_roles | current project lead application roles | ||
project:lead:application_roles:key | current project lead application roles keys | ||
project:lead:application_roles:name | current project lead application roles names | ||
project:lead:groups | current project lead groups | ||
project:lead:groups:name | current project lead groups names | ||
components | |||
project:components:id | current project components ids separated by comma | ||
project:components:name | current project components ids separated by comma
project:components:name is equal to project:components | ||
project:components:description | current project components descriptions separated by comma | ||
project:components:url | current project components url | ||
versions | |||
project:versions:id | current project versions ids separated by comma | ||
project:versions:name | current project versions names separated by comma
project:versions:name is equal to project:versions | ||
project:versions:description | current versions descriptions separated by comma | ||
project:versions:is_archived | boolean value (true/false) of the current project versions is archived field | ||
project:versions:is_released | boolean value (true/false) of the current project versions is released field | ||
project:versions:url | urls of the current project versions |
User specific values
Placeholder expression | Result value | |
---|---|---|
current_user | current_user:id | id of the current user |
current_user: | url of the current user | |
current_user:name | name of the current user
current_user:name is equal to current_user | |
current_user:full_name | full name of the current user | |
current_user:email | email of the current user | |
current_user:email_domain | email domain of the current user | |
current_user:application_roles | application roles of the current user | |
current_user:application_roles:key | application roles keys of the current user | |
current_user:application_roles:name | application roles names of the current user | |
current_user:groups | current user groups | |
current_user:groups:names | names of the current user groups |
Custom Field values
As far as Jira provides different type of custom fields the values are divided by type. Check the table below.
custom field value type | Placeholder expression | Result value | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
single value custom fields | ||||||||||
url | customfield:{id} | string value type | ||||||||
text | customfield:{id} | text value type | ||||||||
date picker | customfield:{id} | date value type | ||||||||
date time picker | customfield:{id} | date time value type | ||||||||
date of first response | customfield:{id} | date of the first comment | ||||||||
days since last comment | customfield:{id} | date/time since last comment | ||||||||
last public comment date | customfield:{id} | date value of the last public comment | ||||||||
userpicker |
| user value of the custom field | ||||||||
number | customfield:{id} | number value of the custom field | ||||||||
group |
| |||||||||
version |
| selected version value of the custom field | ||||||||
select list |
| selected option of the custom field | ||||||||
radio buttons | customfield:{id} | selected option name of the custom field | ||||||||
multi value custom fields | ||||||||||
checkboxes |
| list of available options separated by comma
| ||||||||
labels | customfield:{id} | list of labels names separated by comma | ||||||||
groups picker |
| list of group names separated by comma
| ||||||||
select list(multiple choice) |
| list of options separated by comma | ||||||||
versions picker |
| |||||||||
user picker |
|
Example placeholders for custom field values
You can get custom field values with the help of the custom field id. Check the example below.
example
Code Block |
---|
customfield:10600 |
You can use the placeholder as a part of the SQL query to get custom field valued.
Code Block |
---|
select name,price from sandwich_menu where restaurant={customfield:10010} |
Info |
---|
Single Value types
|
See also