Query language in Tracker

If you want to do more than simple filters allow, set a filter using a query language.

The query language allows you to:

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

• Filter issues by multiple values of a single field.

• Use the comparison operators and logical operators in filters.

• Specify functions as a comparison value.

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

Query formatQuery format

To set up a filter using a query language:

1. Open the Issues page.

2. Click Query language in the top-right corner of the page.

3. Enter a query and click Apply.

General request format:

"<parameter>": "<value>"

To set a parameter, start typing its name and select a relevant one from the suggestion. For the full list of parameters, see Filter parameters.

ExamplesExamples

• Issues that are in the TEST queue:

  "Queue": "TEST"
  

• Issues with Ivan Ivanov as an assignee:

  "Assignee": "Ivan Ivanov"
  

• Issues with the Open or In Progress status.

  "Status": "Open", "In Progress"
  

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

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

Multiple parameter valuesMultiple parameter values

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

<parameter>: "<value_1>", "<value_2>", "<value_3>"

ExampleExample

author: "vpupkin","iivanov"

This filter will return all the issues that were reported by vpupkin or iivanov.

Filters with multiple conditionsFilters with multiple conditions

You can combine multiple conditions per filter using logical operators:

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

  For example:

  <parameter_1>: "<value_1>" AND <parameter_2>: "<value_2>"
  

  This query will return the issues that have <parameter_1> set to <value_1> AND <parameter_2> set to <value_2>.

  Note

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

• OR: Logical Or operator. At least one of the conditions must be fulfilled.

  For example:

  <parameter_1>: "<value_1>" OR <parameter_2>: "<value_2>"
  

  This query will return the issues that have at least one of the conditions met: <parameter_1> set to <value_1> Or <parameter_2> set to <value_2>.

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

<parameter_1>: "<value_1>" AND <parameter_2>: "<value_2>" OR <parameter_3>: "<value_3>"

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

<parameter_1>: "<value_1>" AND (<parameter_2>: "<value_2>" OR <parameter_3>: "<value_3>")

Searching by textSearching by text

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

All the textual fields of the issue are searchable: name, description, and comments.

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

  • Summary: Issue name.

  • Description: Issue description.

  • Comment: Text in comments.

  • History: Text in the history of changes.

  Description: "This area is familiar to me as the outskirts of China"
  

  This filter will return all the issues whose descriptions include the words from the original query and their forms.

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

  Summary: #"Version 2.0"
  

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

• To only find issues that contain text exactly matching the query text and additional text, use the # operator and add the || operator where the additional text is placed:

  Description`: #"Make ||"
  

  This filter will only return the issues with text that contains the word "Make" and some more words after it. For example, "Make lists" or "Make a map".

  The || operator can only be used together with the # operator.

• To only find issues that have no text fragment in a given field, use the ! operator:

  Summary: !"UI"
  

  This filter will only return the issues whose name does not contain a UI text fragment.

• To only find issues whose name does not exactly match the query text, use the ~ operator. This operator only applies to the Summary field:

  Summary: ~"UI Update 2.0"
  

  This filter will only return the issues whose name does not match the query text.

Searching by userSearching by user

You can search issues by names and usernames specified in the issue fields. There are several ways to specify names and usernames in queries.

• Username with @ at the end: login@. Use it to search for an exact match containing the username.

  For example:

  Assignee: user3370@
  

  This query will display all issues that have user3370 specified as the assignee. This is the most accurate way to search by user.

• Full name in quotation marks: "<full_name>". Use it to search for matches containing the user's full name.

  For example:

  Author: "Ivan Ivanov"
  

  This query will display all issues that have Ivan Ivanov specified as the reporter. Please note that the output may contain issues of other reporters with the username or name similar to Ivan Ivanov. To avoid this, search by username with the @ character.

• Full name and username. Use it to search for exact matches containing any of these.

  Examples:

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

  • Followers: ivan. This query will display all issues followed by a user with the ivan@ username or with the first name Ivan .

Searching by local fieldSearching by local field

To specify a local issue field in the query, enter the key of the queue to which the field is linked, followed by a dot and the field's name in Russian or English. If the field's name includes several words, enclose the name in double quotes. Examples:

DEVS.Test engineer: "Ivan Ivanov"

DEVS."Lead test engineer": "Ivan Ivanov"

DEVS.tester: user3370@

Date and time parametersDate and time parameters

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

DateDate

• MM/DD/YYYY

  For example:

  04/30/2017
  

• DD.MM.YYYY

  For example:

  30.04.2017
  

• DD-MM-YYYY

  For example:

  30-04-2017
  

• YYYY-MM-DD

  For example:

  2017-04-30
  

Date and timeDate and time

To specify exact date and time, use the format:

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

For example:

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

Time intervalsTime intervals

• You can express 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 expressed as:

  "3d 5h 32m"
  

• You can set intervals using acceptable date formats:

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

  For example, a filter for the issues created within a certain interval:

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

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

  For example, a filter for the issues created not earlier than a week and one day ago.

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

Comparison operatorsComparison operators

Apart from checking for an exact match, 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>
  

• In the range

  The operation only applies to numeric parameters.

  <parameter>: <number_1> ... <number_2>
  

ExamplesExamples

Search for issues with a deadline in a few days or today:

• Issues with a deadline in 3 days:

  Deadline: <= today() +3d and deadline: >= today()
  

To customize parameters, use functions in a query:

• Issues with a deadline today:

  Deadline: today()
  

FunctionsFunctions

In addition to exact parameter values, you can use functions. A function is a variable whose value is calculated at the query runtime. For example, the function today() takes the value of today's date. To show all issues created today, use the query:

Created: today()

Searching by parameter changeSearching by parameter change

If you know when and how the issue parameter was changed, you can use these criteria in the filter:

"<parameter>": changed(from: "<old_value>" to: "<new_value>" by: "<who_changed>" date: "<when_changed>")

For example, to get a list of issues that Ivan Ivanov changed to the In Progress status over a certain period of time, create the following query:

Status: changed(to: "In Progress" by: "Ivan Ivanov" date: 01.09.2017 .. 15.09.2017)

To get a list of issues that Ivan Ivanov changed to the In Progress status over the last week, use the following function in your query:

Status: changed(to: "In Progress" by: "Ivan Ivanov" date: >today()-1w)

Sorting resultsSorting results

You can sort filter results by adding "Sort By" at the end of the query. Specify the name of the sort field as a value:

"Sort By": Created

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

"Sort By": Created ASC

To specify several sort fields, list them through a comma in the priority order:

"Sort By": Created ASC, Updated DESC

Useful queriesUseful queries

Try to run some ready-made queries to get a better idea of how they work:

• Active issues whose reporter you are:

  Author: me() Resolution: empty()
  

• Active issues that were assigned to you:

  Assignee: me() Resolution: empty()
  

• Active issues that you follow:

  Followers: me() Resolution: empty()
  

• Issues where you are an assignee and deadline is due within a week:

  Assignee: me() Deadline: week()
  

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

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

Filter parametersFilter parameters