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 comments.
Filter issues by multiple values of a single field.
Use comparison operators and logical operators in filters.
Specify functions as a comparison value.
Set the sort order for issues in the filter results.
Query format
To define a filter using the query language:
On the upper panel in Tracker, choose
.Click Query language in the upper-right corner.
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 the section 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
orIn progress
."Status": "Open", "In progress"
Issues created from January 1 to January 30, 2017:
"Created": "2017-01-01".."2017-01-30"
Multiple parameter values
parameter: "value1", "value2", " value3"
- Example
-
author: "vpupkin","iivanov"
This filter outputs all issues that were reported by
vpupkin
oriivanov
.
Filters with multiple conditions
You can combine multiple conditions in a single filter using Boolean operators:
Example:AND
— The logical AND operator. Conditions combined with this operator must all be met at the same time.parameter1: "value1" AND parameter2: "value2"
This query outputs the issues that have
parameter1
set tovalue1
andparameter2
set tovalue2
.Note. Instead of using theAND
operator, you can just list the fields separated by a space.
Example:OR
— The logical OR operator. At least one of the conditions combined with this operator must be met.parameter1: "value1" OR parameter2: "value2"
This query outputs the issues that meet at least one of these conditions:
parameter1
is set tovalue1
orparameter2
is set tovalue2
.
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.
#
operator:Summary: #"Lorem ipsum dolor sit amet"
- Example
-
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.
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 for searching 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 for searching for an exact match containing such a 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
. Such a query will display all issues followed by users with the first name Alice no matter what their last name is.Followers: alice
. Such a query will display all issues followed by the user with the usernamealice@
or any user named Alice.
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
- Time
-
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 is written as:
"3d 5h 32m"
When searching fields that contain a date, you can use the addition and subtraction operations, time ranges, and functions.
Here is an example of a filter for issues created no earlier than eight days ago:
Created: > today() - "1w 1d"
A filter for issues that were created in a certain period of time:
Created: 01-01-2017 .. 02-03-2017
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()
Function | Result | Example |
---|---|---|
| Empty value (parameter omitted) | Find issues that don't have an assignee: |
| Any non-empty value (parameter set) | Find issues that have a deadline set: |
| Name of the user who made the request | Find issues that you created: |
| Current time to the minute | Find issues created in the last 12 hours: |
| Time interval corresponding to the current date | Find issues created today: |
| Date range corresponding to the current week | Find issues created this week: |
| Date range corresponding to the current month | Find issues created in this month: |
| Date range corresponding to the current quarter | Find issues created in this quarter: |
| Date range for the current year | Find issues created this year: |
| No resolution | Find all issues that do not have a resolution set: |
| List of department employees | Find issues that employees of the Sales department are working on: |
Function | Result | Example |
---|---|---|
| Empty value (parameter omitted) | Find issues that don't have an assignee: |
| Any non-empty value (parameter set) | Find issues that have a deadline set: |
| Name of the user who made the request | Find issues that you created: |
| Current time to the minute | Find issues created in the last 12 hours: |
| Time interval corresponding to the current date | Find issues created today: |
| Date range corresponding to the current week | Find issues created this week: |
| Date range corresponding to the current month | Find issues created in this month: |
| Date range corresponding to the current quarter | Find issues created in this quarter: |
| Date range for the current year | Find issues created this year: |
| No resolution | Find all issues that do not have a resolution set: |
| List of department employees | Find issues that employees of the Sales department are working on: |
Search for parameter changes
"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 status "In progress" in a certain time period, make the query:
Status: changed(to: "In progress" by: "Alice Little" date: 01.09.2017 .. 15.09.2017)
Sort results
"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, set the sort order to ascending (ASC
) or descending (DESC
):
"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 for which you are the reporter, assigned, or follower.
(Followers: me() OR Assignee: me() OR Author: me()) AND Resolution: empty() AND Priority: Blocker, Critical
Filter parameters
Parameter | Value | Description |
---|---|---|
| Logins and usernames | Searching for issues that list specific users in the Access field. Example: |
| Version names | Searching for issues that list a specific value in the Affected version field. Example:
|
| Logins and usernames | Searching for issues that list specific users as the assignee. Example: |
| Logins and usernames | Searching for issues that list specific users as the reporter. Example: |
| Queue names or keys | Searching for issues that have dependent (blocked) issues in the specified queues. Example: |
| Issue keys | Searching for issues cloned from specific issues. Example: |
| Queue names or keys | Searching for issues cloned from issues in specific queues. Example: |
| Text string | Searching for issues that include a comment with a specific text. Example:
|
| Logins and usernames | Searching for issues that include comments left by specific users. Example: |
| Logins and usernames | Searching for issues that include components managed by specific users. Example: |
| Component names | Searching for issues that include specific components. Example: |
| Date or date range | Searching for issues created on a specific date or within a specific date range. Example: |
| Date or date range | Searching for issues with a deadline set for a specific date or date range. Example: |
| Queue names or keys | Searching for issues dependent on (blocked by) issues from specific queues. Example: |
| Issue keys | Searching for issues dependent on (blocked by) specific issues. Example: |
| Text string | Searching for issues with a specific text in the description. Example:
|
| Queue names or keys | Searching for issues that have duplicates in specific queues. Example: |
| Issue keys | Searching for issues that are duplicates of specific issues. Example: |
| Queue names or keys | Searching for issues that are duplicates of issues in the specified queues. Example: |
| Date or date range | Searching for issues whose End date value matches a specific date or its date range. Example: |
| Epic keys | Searching for issues from specific epics. Example: |
| Queue names or keys | Searching for epics that include issues from specific queues. Example: |
| Only the | Searching for your favorites. Example: |
| Filter names or IDs | Searching for issues that match the specified filters. Example: |
| Version names | Searching for issues that list a specific value in the To fix in version field. Example: |
| Logins and usernames | Searching for issues that list specific users as followers. Example: |
| Issue keys | Searching for issues from specific epics. Example: |
| Queue names or keys | Searching for issues that are somehow linked with issues from the specified queues (parent, related, duplicate, sub-issue, and so on). Example: |
| Text string | Searching for issues with a history that includes the words or forms of words from a specified phrase. The search is only performed on values of Issue name and Issue description fields. Example: |
| Queue names or keys | Searching for issues related to epics from specific queues. Example: |
| Issue keys | Searching for issues that block specific issues. Example: |
| Issue keys | Searching for issues that are duplicated by specific issues. Example: |
| Issue keys | Searching for epics that include specific issues. Example: |
| Issue keys | Searching for parent issues for specified sub-issues. Example: |
| Issue keys | Searching for sub-issues for specified parent issues. Example: |
| Issue keys | Searching for issues with specific keys. Example: |
| Date and time when the last comment was posted | Searching for issues that didn't receive any new comments during a particular timeframe. Example: |
| Issue keys | Searching for issues that are linked with the specified issues (parent, related, duplicate, sub-issue, and so on). Example: |
| Names of departments or teams | Searching for issues that are followed by specific departments or teams. Example: |
| Logins and usernames | Searching for issues recently updated by specific users. Example: |
| Queue names or keys | Searching for issues moved from the specified queues. Example: |
| Issue keys | Searching for clones of the specified issues. Example: |
| Time range using the format | Searching for issues with a specific initial score. Example: |
| Queue names or keys | Searching for issues that have clones in specific queues. Example: |
| Queue names or keys | Searching for issues that have sub-issues in the specified queues. Example: |
| Logins and usernames | Searching for issues with a pending reply from a specified user (the user has been invited to comment). Let's say you need to find issues pending a reply from a user with the username |
| Priority value | Search for issues that have the specified priority values. Example: |
| Project titles | Searching for issues from specific projects. Example: |
| Queue names or keys | Searching for issues from specific queues. Example: |
| Logins and usernames | Searching for issues that list specific users as queue owners. Example: |
| Logins and usernames | Searching for issues that list specific users as the assignees, reporters, or followers. Example: |
| Queue names or keys | Searching for issues that are related to issues from specific queues (the “Related” type link). Example: |
| Issue keys | Searching for issues related to specific issues (the“Related” type link). Example: |
| Date or date range | Searching for issues that have been closed (resolved) on a specific date or during a specific date range. Example: |
| Logins and usernames | Searching for issues that have been closed (resolved) by the specified users. Example: |
| Sprint names or IDs | Searching for issues from specific sprints. Example: |
| Issue Board ID (can be found in the Board page URL) | Searching for issues related to an active spring on the specified issue board. Example: |
| Issue Board ID (can be found in the Board page URL) | Searching for issues from specific boards. Example: |
| Date or date range | Searching for issues whose Start date value matches a specific date or falls within a date range. Example: |
| Status names | Searching for issues with specific status names. Example: |
| Story Points score | Searching for issues with a specific number of Story Points. Example: |
| Queue names or keys | Searching for issues that have parent issues in the specified queues. Example: |
| Text string | Searching for issues with a specific title. Example:
|
| Issue tags | Searching for issues with the specified tags. Example:
|
| Time range using the format | Searching for issues that took the specified amount of time to complete. Example: |
| Date or date range | Searching for issues with a deadline changed at a specific date or during a specific date range. Example: |
| Logins and usernames | Searching for issues voted on by specific users. Example: |
| Number of votes | Searching for issues with a specific number of votes. Example: |
Parameter | Value | Description |
---|---|---|
| Logins and usernames | Searching for issues that list specific users in the Access field. Example: |
| Version names | Searching for issues that list a specific value in the Affected version field. Example:
|
| Logins and usernames | Searching for issues that list specific users as the assignee. Example: |
| Logins and usernames | Searching for issues that list specific users as the reporter. Example: |
| Queue names or keys | Searching for issues that have dependent (blocked) issues in the specified queues. Example: |
| Issue keys | Searching for issues cloned from specific issues. Example: |
| Queue names or keys | Searching for issues cloned from issues in specific queues. Example: |
| Text string | Searching for issues that include a comment with a specific text. Example:
|
| Logins and usernames | Searching for issues that include comments left by specific users. Example: |
| Logins and usernames | Searching for issues that include components managed by specific users. Example: |
| Component names | Searching for issues that include specific components. Example: |
| Date or date range | Searching for issues created on a specific date or within a specific date range. Example: |
| Date or date range | Searching for issues with a deadline set for a specific date or date range. Example: |
| Queue names or keys | Searching for issues dependent on (blocked by) issues from specific queues. Example: |
| Issue keys | Searching for issues dependent on (blocked by) specific issues. Example: |
| Text string | Searching for issues with a specific text in the description. Example:
|
| Queue names or keys | Searching for issues that have duplicates in specific queues. Example: |
| Issue keys | Searching for issues that are duplicates of specific issues. Example: |
| Queue names or keys | Searching for issues that are duplicates of issues in the specified queues. Example: |
| Date or date range | Searching for issues whose End date value matches a specific date or its date range. Example: |
| Epic keys | Searching for issues from specific epics. Example: |
| Queue names or keys | Searching for epics that include issues from specific queues. Example: |
| Only the | Searching for your favorites. Example: |
| Filter names or IDs | Searching for issues that match the specified filters. Example: |
| Version names | Searching for issues that list a specific value in the To fix in version field. Example: |
| Logins and usernames | Searching for issues that list specific users as followers. Example: |
| Issue keys | Searching for issues from specific epics. Example: |
| Queue names or keys | Searching for issues that are somehow linked with issues from the specified queues (parent, related, duplicate, sub-issue, and so on). Example: |
| Text string | Searching for issues with a history that includes the words or forms of words from a specified phrase. The search is only performed on values of Issue name and Issue description fields. Example: |
| Queue names or keys | Searching for issues related to epics from specific queues. Example: |
| Issue keys | Searching for issues that block specific issues. Example: |
| Issue keys | Searching for issues that are duplicated by specific issues. Example: |
| Issue keys | Searching for epics that include specific issues. Example: |
| Issue keys | Searching for parent issues for specified sub-issues. Example: |
| Issue keys | Searching for sub-issues for specified parent issues. Example: |
| Issue keys | Searching for issues with specific keys. Example: |
| Date and time when the last comment was posted | Searching for issues that didn't receive any new comments during a particular timeframe. Example: |
| Issue keys | Searching for issues that are linked with the specified issues (parent, related, duplicate, sub-issue, and so on). Example: |
| Names of departments or teams | Searching for issues that are followed by specific departments or teams. Example: |
| Logins and usernames | Searching for issues recently updated by specific users. Example: |
| Queue names or keys | Searching for issues moved from the specified queues. Example: |
| Issue keys | Searching for clones of the specified issues. Example: |
| Time range using the format | Searching for issues with a specific initial score. Example: |
| Queue names or keys | Searching for issues that have clones in specific queues. Example: |
| Queue names or keys | Searching for issues that have sub-issues in the specified queues. Example: |
| Logins and usernames | Searching for issues with a pending reply from a specified user (the user has been invited to comment). Let's say you need to find issues pending a reply from a user with the username |
| Priority value | Search for issues that have the specified priority values. Example: |
| Project titles | Searching for issues from specific projects. Example: |
| Queue names or keys | Searching for issues from specific queues. Example: |
| Logins and usernames | Searching for issues that list specific users as queue owners. Example: |
| Logins and usernames | Searching for issues that list specific users as the assignees, reporters, or followers. Example: |
| Queue names or keys | Searching for issues that are related to issues from specific queues (the “Related” type link). Example: |
| Issue keys | Searching for issues related to specific issues (the“Related” type link). Example: |
| Date or date range | Searching for issues that have been closed (resolved) on a specific date or during a specific date range. Example: |
| Logins and usernames | Searching for issues that have been closed (resolved) by the specified users. Example: |
| Sprint names or IDs | Searching for issues from specific sprints. Example: |
| Issue Board ID (can be found in the Board page URL) | Searching for issues related to an active spring on the specified issue board. Example: |
| Issue Board ID (can be found in the Board page URL) | Searching for issues from specific boards. Example: |
| Date or date range | Searching for issues whose Start date value matches a specific date or falls within a date range. Example: |
| Status names | Searching for issues with specific status names. Example: |
| Story Points score | Searching for issues with a specific number of Story Points. Example: |
| Queue names or keys | Searching for issues that have parent issues in the specified queues. Example: |
| Text string | Searching for issues with a specific title. Example:
|
| Issue tags | Searching for issues with the specified tags. Example:
|
| Time range using the format | Searching for issues that took the specified amount of time to complete. Example: |
| Date or date range | Searching for issues with a deadline changed at a specific date or during a specific date range. Example: |
| Logins and usernames | Searching for issues voted on by specific users. Example: |
| Number of votes | Searching for issues with a specific number of votes. Example: |