JQL Functions

Custom field name duplicates

If you have custom fields with the same name as Jira default fields, Enhanced Search will prioritise Jira’s default fields during searches. We recommend renaming your custom fields before using them in search queries, as Jira’s default fields will be used instead of custom fields with the same name.

Enhanced Search features several advanced JQL functions not available as default in Jira, which are documented within this section. 

Almost all functions require a subquery as a first parameter. If you provide an empty string (e.g.,""), your query will be inefficient because it matches all issues in your Jira instance.

You should be aware if you use the statement below within your subqueries, means that other users will see your results, not their own results:

assignee = currentUser()

For example, issueFunction in linkedIssuesOf("assignee = currentUser()") saved as an Enhanced Search filter will always show the issues linked to the filter owner's tickets, regardless of who views the filter.

Space Required After Commas

If you see an error message informing you that "Function 'X' does not exist", then you should check that you have entered a space after the comma in the query you are running.

Operators

Enhanced Search uses the  in and not in operators for all JQL functions. You can also use some additional operators for the Date Function.

On this page