Filtering issues on a board using the query language

On new issue boards, you can use the query language to:

• Create a filter for automatically adding issues to a board.

• Add a quick filter on a board or in a backlog.

The query language allows you to:

• Filter issues by parameter value.

• Search for issues by name or description.

• Use the comparison operators and logical operators in filters.

Query format

To set up an issue filter using the query language:

1. Open the page on which you want to make a query:

   • In the top right corner of the board or backlog page, select the  Filters option and then click QL.

   • On the board setup page, under Adding issues to the board, enable the Query language option.

2. Enter the query:

   • To set an issue parameter, start typing its name or key and select a relevant parameter from the suggestion.

     To find out parameter keys, go to Tracker on the Issue fields page.

   • Enter the parameter value to filter issues by.

     For statuses, queues, usernames, and other parameters with preset values, you will see suggestions.

   • To specify multiple parameters, add a logical operator and enter a new parameter and value.

   When typing the names of issue parameters and queues, statuses, usernames and other values like that, be sure to select them from the provided suggestions, or else your query may be read incorrectly. Yandex Tracker will underscore incorrect query items with a red line.

3. Save the filter and board settings.

General request format:

<name of parameter 1>: <value 1> AND <name of parameter 2>: <value 2>

Examples

• Issues that are in the TEST queue:

  

• Issues with Ivan Ivanov as an assignee:

  

• Issues with the Open or In progress status.

  

• Issues created after September 1, 2024:

  

Multiple parameter values

If you want to filter issues by multiple values of the same parameter, use a comma-separated list of values:

<parameter>: <value 1>, <value 2>, <value 3>

Example

Type: Issue, Error

This filter will return all issues with the Issue or Error type.

Filters with multiple conditions

You can combine multiple conditions per filter using logical operators:

• AND: Conditions combined with the logical operator AND must be fulfilled simultaneously.

  Example:

  Type: Issue AND Status: In progress
  

  This query will return the issues with the Issue type and the In progress status.

• OR: If you use the logical operator OR, At least one of the conditions must be fulfilled.

  Example:

  Type: Error OR Components: Testing
  

  This query returns the issues that have at least one of the conditions met: the issue type is Error or the Components field is set to Testing.

You can create complex filters by combining multiple operators in a single request:

Type: Issue AND Author: Ivan Ivanov OR Components: Testing

When complex filters are processed, the AND operators are applied first. To change the order of actions, use parentheses:

Type: Issue AND (Author: Ivan Ivanov OR Components: Testing)

Searching by text

You can use the query language to search for issues by their text parameters, such as name or description.

If your search text contains multiple words, enclose it in quotation marks. For example:

Description: "New issue"

Searching by local field

To specify the value of a local issue field in your query:

1. Start typing the name or key of a local field.

   In the suggestion provided, after the local field name, you will see the name of the queue it refers to.

   

2. Select a parameter that belongs to your queue.

3. Set the value to search by.

Date and time parameters

• To specify a date as an issue parameter value, use YYYY-MM-DD format. Example:

  2024-10-30
  

• To set a parameter value that is greater or less than a specific date, use comparison operators. Example:

  Created: >= 2024-10-30
  

Comparison operators

In addition to checking for exact matches of values, the query language supports the following comparison operations

• Not equal to

  <parameter>: !<value>
  

• Greater than, Less than, Less than or equal to, and Greater than or equal to

  The operations accept only numeric and date-and-time parameters.

  <parameter>: > <number>
  <parameter>: < <number>
  <parameter>: >= <number>
  <parameter>: <= <number>
  

Example:

Story Points: > 8

Functions

The query language supports the empty() function that stands for a missing parameter. For example:

Assignee: empty()

Resolution: empty()