Query language

If the basic filters don't give you enough options, use the query language to define a filter.

The query language allows you to:

• Search for issues by name, description, and comment.

• Filter issues by multiple values in a single field.

• Use comparison operators and logical operators in filters.

• Specify functions as a comparison value.

• Set the sorting order for issues in the filter results.

Query format

To define a filter using the query language:

1. On the top panel in Tracker, choose Issues → Find issues.

2. Click Query language in the upper-right corner.

3. Enter a query and click Apply.

The basic format of the query is:

"parameter": "value"

To set the parameter, start typing its name and choose the appropriate one from the suggestions. For the full list of parameters, see Filter parameters.

Examples

• Issues that are in the TEST queue:

  "Queue": "TEST"
  

• Issues that are assigned to Alice Little:

  "Assignee": "Alice Little"
  

• Issues with the status Open or In progress.

  "Status": "Open", "In progress"
  

• Issues created from January 1 to January 30, 2017:

  "Created": "2017-01-01".."2017-01-30"
  

Multiple parameter values

If you want to filter issues by multiple values for the same parameter, separate them with commas:

parameter: "value1", "value2", " value3"

Example

author: "vpupkin","iivanov"

This filter outputs all issues that were reported by vpupkin or iivanov.

Filters with multiple conditions

You can combine multiple conditions in a single filter using Boolean operators:

• AND: The logical AND operator. Conditions combined with this operator must all be met at the same time.

  Example:

  parameter1: "value1" AND parameter2: "value2"
  

  This query outputs issues where parameter1 is set to value1 and parameter2 is set to value2.

  Note

  Instead of using the AND operator, you can just list the fields separated by a space.

• OR: The logical OR operator. At least one of the conditions combined with this operator must be met.

  Example:

  parameter1: "value1" OR parameter2: "value2"
  

  This query outputs issues where parameter1 is set to value1 or parameter2 is set to value2.

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

parameter1: "value1" AND parameter2: "value2" OR parameter3: "value3"

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

parameter1: "value1" AND (parameter2: "value2" OR parameter3: "value3")

Text search

In addition to searching by parameters, you can also use the familiar text search. To do this, enter text in the query field and click Apply.

The search is performed across all the text fields in the issue: name, description, and comments.

• To search in only one of the fields, use the parameter to specify it:

  • Summary: The issue name.

  • Description: The issue description.

  • Comment: Text in comments.

  • History: Text in the history of changes.

  Description: "Off with her head"
  

  This filter outputs all the issues that have a description containing the words and close forms of the words in the query.

• To only find issues with text that exactly matches the query text, use the # operator:

  Summary: #"Lorem ipsum dolor sit amet"
  

  This filter only outputs the issues whose name exactly matches the query text.

• To only find issues that have no text specified in the query, use the ~ operator:

  Comment: ~"Consectetur adipiscing elit"
  

  This filter only outputs the issues whose comments don't match the query text.

Searching by user

You can search for issues by users' real names and usernames specified in issue fields. There are multiple ways to specify a real name or a username in your query:

• Putting the first and last name in quotation marks: "first_name last_name". Used to search for an exact match with the user's first and last name.

  Example:

  Author: "Alice Little"
  

  Entering this query will display all issues where the author is specified as Alice Little.

• Entering a username and putting @ at the end: login@. Used to search for an exact match containing this username.

  Example:

  Assignee: user3370@ 
  

  This query will display all issues that have user3370 specified as the assignee.

• Entering a user's first name, last name, or username. Used for searching for exact matches containing either of those.

  Examples:

  • Followers: Alice. This query will display all issues followed by users with the first name Alice no matter what their last name is.

  • Followers: alice. This query will display all issues followed by the user with the username alice@ or any user named Alice .

Searching by local field

To specify the value of an issue local field in a query, enter the key of the queue that the field is linked to and then the field name or key after a dot. Examples:

DEVS."Tester": "Alice Little"

DEVS.tester: user3370@

Date and time parameters

Many issue parameters have date and time values. The query language supports several formats for these parameters:

Date

• MM/DD/YYYY

  Example:

  04/30/2017
  

• DD.MM.YYYY

  Example:

  30.04.2017
  

• DD-MM-YYYY

  Example:

  30-04-2017
  

• YYYY-MM-DD

  Example:

  2017-04-30
  

Date and time

To specify the exact date and time, use this format:

"YYYY-MM-DD XXh:XXm:XXs"

Example:

"2017-04-30 17:25:00"

Time intervals

• You can set time intervals in weeks, days, hours, minutes and seconds in the format:

  "XXw XXd XXh XXm XXs"
  

  For example, a time interval of 3 days, 5 hours, and 32 minutes can be written as:

  "3d 5h 32m"
  

• You can set intervals using valid date formats:

  DD-MM-YYYY .. DD-MM-YYYY
  

  Here's an example of a filter for issues that were created in a certain period of time:

  Created: 01-01-2017 .. 02-03-2017
  

• Time intervals can be set using functions as well as comparison, addition, and subtraction operations.

  Here is an example of a filter for issues created no earlier than eight days ago:

  Created: > today() - "1w 1d"
  

Comparison operations

In addition to looking for exact matches, the query language supports comparisons:

• Not equal to

  parameter: !"value"
  

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

  These operations are only applied to numeric parameters and date and time parameters.

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

• In the range

  This operation is only applied to numeric parameters.

  parameter: number1 .. number2
  

Functions

In addition to explicit parameter values, you can use functions. A function is a variable with a value that is calculated when the request is executed. For example, the function today() takes the value of today's date. To show all issues created today, use the query:

Created: today()

Search for parameter changes

If you know when and how a parameter was changed for an issue, you can create a filter for it:

"parameter": changed(from: "old value" to: "new value" by: "who changed" date: "when changed")

For example, to get a list of issues that user Alice Little switched to the In progress status in a certain period of time, you need to make a request:

Status: changed(to: "In progress" by: "Alice Little" date: 01.09.2017 .. 15.09.2017)

For example, to get a list of issues that user Alice Little switched to the In progress status during the last week, use a function in your request:

Status: changed(to: "In progress" by: "Alice Little" date: >today()-1w)>

Sort results

You can sort the filter results by setting the "Sort By" parameter at the end of the query. For the value, specify the name of the field to sort by:

"Sort By": Created

If necessary, sort by ascending (ASC) or descending (DESC) order:

"Sort By": Created ASC

To specify multiple fields to sort by, separate them with commas in order of priority:

"Sort By": Created ASC, Updated DESC

Useful queries

Try a few ready-made queries to learn how they work:

• Active issues that you created:

  Author: me() Resolution: empty()
  

• Active issues that you are assigned to:

  Assignee: me() Resolution: empty()
  

• Active issues that you are following:

  Followers: me() Resolution: empty()
  

• Issues that you are assigned to that have a deadline during the current week:

  Assignee: me() Deadline: week()
  

• Issues with Critical or Blocker priority that you are the reporter, assignee, or follower for.

  (Followers: me() OR Assignee: me() OR Author: me()) AND Resolution: empty() AND Priority: Blocker, Critical
  

Filter parameters