...
Column Type | Supported operators | Functions | Keywords | |
|---|---|---|---|---|
Simple Text | ~ , !~ , is not , is | EMPTY | ||
Number | = , != , <= , >= , > , < , is not , is , not in , in | EMPTY, ORDER BY (ASC / DESC) | ||
Decimal Number | = , != , <= , >= , > , < , is not , is , not in , in | EMPTY, ORDER BY (ASC / DESC) | ||
Select List | = , !=, is not , is , not in , in | ORDER BY (ASC / DESC), EMPTY | ||
Status | = , != , is not , is , not in , inEMPTY | |||
User Picker | = , != , is not , is, not in, in | EMPTY, ORDER BY (ASC / DESC) | ||
Checkbox | = , != , is not , is, not in, in | unchecked, ORDER BY (ASC / DESC) | ||
Formula | = , != , <= , >= , > , < , is not , is , not in , in | EMPTY, ORDER BY (ASC / DESC) | ||
Date | = , != , <= , >= , > , < , is not , is , not in , in | currentLogin(), endOfDay(), endOfMonth(), endOfWeek(), endOfYear(), lastLogin(), now(), startOfDay(), startOfMonth(), startOfWeek(), startOfYear() | EMPTY, ORDER BY (ASC / DESC) |
| Note |
|---|
The accuracy of the JQL results are 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. |