Dynamic JQL
As a project administrator, you can choose which issues you want to display in an overview.
To do so, you need to configure a JQL, the same as the ones you could use in native Jira.
Issues to display
Issue to retrieve
You are prompted to enter a JQL in this section to filter issues that will be displayed in the table. This value can be left empty.
When using a table display, issues are paginated by pages of 25, displaying a maximum of 30 issues in total. This means up to 25 issues will be shown on the first page and 5 on the second page. When using the Card display, all issues are listed, up to a maximum of 30 issues.
The JQL can be static or leverage dynamic values from the current issue where the overview is displayed. Using variables in the JQL enhances its power, enabling the display of dynamic content that adds context-specific information, such as support requests raised by the same reporter or incidents related to the same component.
Example: project = OSD AND reporter = ${issue.reporter}
In this example, {$issue.reporter} will be dynamically evaluated in each overview where it's configured, and the JQL will be adjusted accordingly.
Variables can be injected using the + Insert button located at the right end of the JQL input form.
Supported field types
Field type | State |
|---|---|
Short text | SUPPORTED |
Number | SUPPORTED |
Single user | SUPPORTED |
Status | SUPPORTED |
Select list (single choice) | SUPPORTED |
Select list (multiple choice) | SUPPORTED |
Select list (cascading) | NOT SUPPORTED |
Labels | SUPPORTED |
Versions | SUPPORTED |
Single group picker | NOT SUPPORTED |
Multi groups picker | NOT SUPPORTED |
Multi user | SUPPORTED |
Text multi line | NOT SUPPORTED |
Date picker | SUPPORTED |
Parent key | SUPPORTED |
Current issue key | SUPPORTED |
Current project key/name | SUPPORTED |
If you require a field type that is not currently supported, please contact our support with your request. We continually review feedback to enhance our features and may consider adding new field types based on user needs.
Test your configuration
When configuring a JQL, don't waste time on testing it on Jira. Use Elements Overview instead, and test your query against an issue.
If you have entered a variable in the filter, using the test issue will replace the variable by the value of the selected field.