Table Values Search in JQL
Single values
You can use an advanced JQL search to return issues with a specific value in a table column.
Use the following syntax:
”Table Name _Columnname” = “value”
For example, the following JQL will show all issues that have the value "Services" in the Column "Element" of the table "Deal Positions".
"Deal Positions_Element" = "Services"Multiple values
"TableName_ColumName" = "value1" and "TableName_ColumNname" = "value2"Column Type | Supported operators | Functions | Keywords |
|---|---|---|---|
Text | ~ , !~ , |
|
|
Number | = , != , <= , >= , > , < , not in , in |
| ORDER BY (ASC / DESC) |
Decimal Number | = , != , <= , >= , > , < , not in , in |
| ORDER BY (ASC / DESC) |
Select List | = , !=, not in , in |
| ORDER BY (ASC / DESC) |
Status | = , != , not in , in |
|
|
User Picker | = , != , not in, in |
| ORDER BY (ASC / DESC) |
Checkbox | = , != , not in, in |
| unchecked, ORDER BY (ASC / DESC) |
Formula | = , != , <= , >= , > , < , not in , in |
| ORDER BY (ASC / DESC) |
Date | = , != , <= , >= , > , < , not in , in | currentLogin(), endOfDay(), endOfMonth(), endOfWeek(), endOfYear(), lastLogin(), now(), startOfDay(), startOfMonth(), startOfWeek(), startOfYear() | ORDER BY (ASC / DESC) |
The accuracy of the JQL results is affected by table context updates.
For example, a table is set up to be displayed in both Story and Task issues, and it has values in issues of both types. If the Task issue type is then removed from the context, the JQL query will continue to list Task issues in the results. This occurs because the app stores table values in issue properties, and they are not cleared after the context is updated.
Adding a context filter to the JQL query, e.g. project = ABC, type = XYZ, easily solves the issue.
Search status in table configuration
On the Tables configuration page (Jira administration → Manage apps → STAGIL Tables → Tables configuration), each table shows a Search status column.
When the status is Activated , the table’s values are indexed and can be searched via JQL.
Please note that Jira allows us to keep only a limited number of tables searchable at the same time (currently up to 100 tables). If your instance exceeds this limit, some tables may temporarily appear as UnActivated , until capacity becomes available again. For example, if an older table is removed or the overall indexing load is reduced, previously unsearchable columns may automatically switch to Activated without any manual action.