Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
Yandex Tracker
  • Getting started
    • Activating Yandex Tracker
    • Logging in to Yandex Tracker
    • Adding users
    • Configuring access to Yandex Tracker
    • Setting up Yandex Tracker
    • Working with Yandex Tracker
      • Start page
      • My issues
      • Working with issues
      • Favorite issues, boards, and dashboards
      • Personal settings
    • Migrating to Yandex Tracker
    • Disabling paid services
  • Yandex Tracker mobile app
  • Tutorials
    • Setting up Yandex Tracker for a development team
      • Overview
      • Creating a queue for a development team
      • Structuring issues
      • Using Agile methodologies
      • Configuring issue templates
      • Connecting repositories
      • Automating recurring actions
      • Integrating Yandex Tracker with other platforms
    • Setting up Yandex Tracker for a support team
      • Overview
      • Creating a queue for the support team
      • Accepting requests by mail and via forms
      • Configuring multi-tiered support
      • Sending emails from the issue page
      • Grouping requests by topic
      • Tracking the time it takes to process a request
      • Collecting request statistics
      • Configuring integration with third-party platforms
  • Concepts
    • Service overview
    • Concepts
    • Roles and access rights
  • Configuring queues
    • Overview
    • Create a queue
    • Queue templates
    • Viewing issues in a queue
    • Changing basic queue settings
    • Changing basic queue settings
      • Overview
      • Configuring issue types
      • Creating a workflow
      • Setting up statuses
      • Configuring transitions
      • Setting up resolutions
    • Local issue fields
    • Adding a queue team
    • Setting access rights for queues
    • Advanced queue features
    • Viewing the history of queue changes
    • Delete a queue
  • Working with issues
    • Create an issue
      • Overview
      • Creating an issue via email
      • Creating an issue from a form
      • Cloning an issue
    • Edit an issue
      • Overview
      • Adding comments to issues
      • Creating a checklist
      • Editing issue links
      • Attaching images and files to an issue
      • Formatting text in issues
      • Voting for an issue
      • Move an issue to another queue
      • Changing multiple issues
    • Setting up an issue reminder
    • Registering time spent
    • Adding issue fields
    • Viewing the history of issue changes
    • Getting access to an issue
    • Deleting an issue
  • Structuring issues
    • Overview
    • Links between issues
    • Projects
      • Overview
      • Create a project
      • List of project issues
      • Gantt chart
    • Components
    • Versions
  • Agile development tools
    • Overview
    • Create a board
    • Working with an agile board
    • Editing or deleting a board
    • Backlog
    • Sprints
    • Epics
    • Collaborative workload estimation
    • Burn down charts
  • Issue boards (beta)
    • Overview
    • Create a board
    • Working with an agile board
    • Setting up a board
  • Find issues
    • Finding issues by key or name
    • Finding my issues
    • Finding issues in queues
    • Creating an issue filter
    • Query language
  • Notifications and subscriptions
    • Overview
    • Subscribing to notifications
    • Receiving update reports
    • Subscribing other users to queue updates
    • Email notification settings
      • Overview
      • Notifications about your issues
      • Notifications about your subscriptions
    • Sending notifications to mailboxes in your domain
  • Statistics and dashboards
    • Dashboards
      • Overview
      • Creating a dashboard
      • Widgets
      • Editing a dashboard
      • Shared access to dashboards
      • Making a dashboard your start page
    • Queue statistics
    • Gantt chart
  • Automation and templates
    • Overview
    • Triggers
      • Overview
      • Creating triggers
      • Setting trigger conditions
      • Configuring trigger actions
      • Editing and deleting triggers
      • Examples
    • Auto actions
      • Overview
      • Automatic issue updates
      • Scheduled issue creation
      • Editing or deleting auto actions
    • Macros
    • Templates
      • Overview
      • Creating a template in Yandex Forms (beta)
      • Creating a template
      • Editing a template
      • Deleting a template
      • Using shared templates
    • Variables
    • Using a form as a template for creating issues
  • Configuring an SLA for issues
    • Overview
    • Configuring rules
    • Work schedule
  • Integration with other services
    • Email
    • Yandex Forms
    • Yandex Wiki
    • Messengers
      • Overview
      • Slack
      • Telegram
    • Setting up links to external applications
      • Overview
      • Setting up an external application
      • Sending your application data to the Tracker team
  • Developer tools
    • API
    • Python client
    • Connecting repositories
  • Pricing policy
    • Billing
    • Setting up a billing account
    • Paying for services
    • Viewing service usage details
  • API reference
    • Overview
    • API access
    • General query format
    • Issues
      • Get issue parameters
      • Edit an issue
      • Create an issue
      • Moving an issue to another queue
      • Find out the number of issues
      • Search for issues
      • Release scroll view resources
      • Get priorities
      • Get transitions
      • Make a status transition
      • Get the history of issue changes
      • Issue links
        • Link issues
        • Get issue links
        • Remove issue links
    • Checklists
      • Create a checklist or add items to it
      • Get checklist parameters
      • Edit a checklist
      • Delete a checklist
    • Projects
      • Create a project
      • Get project parameters
      • Get a list of all projects
      • Get a list of project queues
      • Edit a project
      • Delete a project
    • Comments
      • Add comment
      • Get issue comments
      • Edit a comment
      • Delete a comment
    • Macros
      • Get queue macros
      • Get a macro
      • Create a macro
      • Edit a macro
      • Delete a macro
    • External links
      • Get a list of external applications
      • Get a list of issue external links
      • Add an external link
      • Delete an external link
    • Attached files
      • Get a list of attached files
      • Download a file
      • Download a thumbnail
      • Attach a file
      • Upload a temporary file
      • Delete a file
    • Queues
      • Create a queue
      • Get queue parameters
      • Get a list of queues
      • Get queue versions
      • Get required fields for the queue
      • Delete a queue
      • Restore a queue
      • Remove a tag from a queue
      • Automation
        • Auto actions
          • Create an auto action
          • Get auto action parameters
        • Triggers
          • Creating a trigger
          • Get trigger parameters
    • Issue boards
      • Get parameters of all boards
      • Get board parameters
      • Create a board
      • Edit a board
      • Delete a board
      • Columns
        • Get parameters of all columns
        • Get column parameters
        • Create a column
        • Edit a column
        • Delete a column
      • Sprints
        • Get all sprints of a board
        • Get a sprint
        • Create a sprint
    • Components
      • Get a list of components
    • Import
      • Import an issue
      • Import files
      • Import comments
      • Import links
    • Bulk operations
      • Perform a bulk move of issues to a different queue
      • Bulk changes to issues
      • Make bulk changes to issue statuses
    • Time tracking
      • Add a record of time spent
      • Edit a record of time spent
      • Delete a record of time spent
      • Get records of time spent
        • Get all records for an issue
        • Select records by parameters
    • Issue fields
      • Get global issue fields
      • Create an issue field
      • Get issue field parameters
      • Edit issue field names
      • Edit possible values of issue fields
      • Create an issue field category
      • Local fields
        • Create a local queue field
        • Get local queue fields
        • Get information about a local queue field
        • Edit a local queue field
    • Get information about the current user
    • Possible response codes
  • Questions and answers
    • General questions
    • Billing
  • Revision history
    • November 2022
    • October 2022
    • September 2022
    • August 2022
  • Support
  1. Find issues
  2. Query language

Query language in Tracker

Written by
Yandex Cloud
  • Query format
  • Multiple parameter values
  • Filters with multiple conditions
  • Searching by text
  • Searching by user
  • Searching by local field
  • Date and time parameters
  • Comparison operations
  • Functions
  • Searching by parameter change
  • Sorting results
  • Useful queries
  • Filter parameters

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 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 format

To define a filter using the query language:

  1. On the Tracker top panel, select 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 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 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 the issues that have parameter1 set to value1 and parameter2 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 the issues that have at least one of the conditions met: 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")

Searching by text

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: #"Version 2.0"
    

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

  • To only find issues that don't have a particular text fragment in a given field, use the ! operator:

    Summary: !"UI"
    

    This filter only returns issues whose name doesn't contain a UI text fragment.

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

    Summary: ~"UI Update 2.0"
    

    This filter only returns issues whose name doesn'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's local field in a query, enter the key of the queue that the field is linked to and then the field name in English or Russian after a dot. If the field name is comprised of several words, specify the name in quotation marks. Examples:

DEVS.Tester: "Alice Little"
DEVS."Lead 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 query 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() Empty value (parameter omitted) Find issues that don't have an assignee:
Assignee: empty()
notEmpty() Any non-empty value (parameter set) Find issues that have a deadline set:
Deadline: notEmpty()
me() Name of the user executing the query Find issues that you created:
Author: me()
now() Current time to the minute Find issues created in the last 12 hours:
Created: >now()-12h
today() Time interval corresponding to the current date Find issues created today:
Created: today()
week() Date range corresponding to the current week Find issues created this week:
Created: week()
month() Date range corresponding to the current month Find issues created this month:
Created: month()
quarter() Date range corresponding to the current quarter Find issues created in this quarter:
Created: quarter()
year() Date range for the current year Find issues created this year:
Created: year()
unresolved() No resolution Find all issues that do not have a resolution set:
Resolution: unresolved()
group() List of department employees Find issues that employees of the Sales department are working on:
Assignee: group(value: "Sales department")

Searching by parameter change

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 create a query:

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 over the last week, use a function in your query:

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

Sorting results

You can sort 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 in 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 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 parameters

Parameter Value Description
"Access" User logins and names Searching for issues with certain users specified in the Access field.
For example:
"Access": user3370@, "Alice Little"
"Affected Version" Version names Searching for issues that list a specific value in the Affected Version field.
For example:
"Affected Version": "14.09.1978"
"Assignee" User logins and names Searching for issues with specific assignees.
For example:
"Assignee": user3370@, "Alice Little"
"Author" User logins and names Searching for issues with specific reporters.
For example:
"Author": user3370@, "Alice Little"
"Block Queue" Queue names or keys Searching for issues that have dependent (blocked) issues in the specified queues.
For example:
"Block Queue": TEST
"Clone" Issue keys Searching for issues cloned from specific issues.
For example:
"Clone": "TASK-123", "TASK-321"
"Clones Of Queue" Queue names or keys Searching for issues cloned from issues in specific queues.
For example:
"Clones Of Queue": TEST, DEVELOP
"Comment" Text string Searching for issues that have comments with specific text.
For example:
  • Find issues with comments that contain the words and forms of words in the phrase:
    "Comment": "great job"
  • Find issues with comments that contain the exact phrase:
    "Comment": #"great job"
"Comment Author" User logins and names Searching for issues with comments made by specific users.
For example:
"Comment Author": user3370@, "Alice Little"
"Component Owner" User logins and names Searching for issues that include components managed by specific users.
For example:
"Component Owner": user3370@, "Alice Little"
"Components" Component names Searching for issues that refer to specific components.
For example:
"Components": "backend", " frontend"
"Created" Date or date range Searching for issues created on a specific date or within a specific date range.
For example:
"Created": 2017-01-01..2017-01-30
"Deadline" Date or date range Searching for issues with a deadline set for a specific date or date range.
For example:
"Deadline": 2017-01-30
"Depend On Queue" Queue names or keys Searching for issues dependent on (blocked by) issues from specific queues.
For example:
"Depend On Queue": TEST
"Depends On" Issue keys Search for issues dependent on (blocked by) specific issues.
For example:
"Depends On": "TASK-123", "TASK-321"
"Description" Text string Searching for issues that have a description with specific text.
For example:
  • Find issues that have a description containing the words and word forms in the phrase:
    "Description": "invent the wheel"
  • Find issues that contain the exact phrase in their description:
    "Description": #"invent the wheel"
"Duplicated In Queue" Queue names or keys Searching for issues that have duplicates in specific queues.
For example:
"Duplicated In Queue": TEST
"Duplicates" Issue keys Searching for issues that duplicate specific issues.
For example:
"Duplicates": "TASK-123", "TASK-321"
"Duplicates In Queue" Queue names or keys Searching for issues that are duplicates of issues in the specified queues.
For example:
"Duplicates In Queue": TEST
"End Date" Date or date range Searching for issues whose End date value matches a specific date or date range.
For example:
"End Date": 2017-01-30
"Epic" Epic keys Searching for issues that refer to specific epics.
For example:
Epic: "TASK-123", "TASK-321"
"Epics For Queue" Queue names or keys Searching for epics that include issues from specific queues.
For example:
"Epics For Queue": TEST, DEVELOP
"Favorited by" Only the function me() can be used as the parameter value Searching for your favorite issues.
For example:
"Favorited by": me()
"Filter" Filter names or IDs Search for issues that match specific filters.
For example:
"Filter": "Issues in my department"
Note. If different users set filters with the same names, they may get different results when running the same query with the filter name specified, because a search is performed using the filter created by the user who initiates the query.
"Fix Version" Version names Searching for issues that list a specific value in the Fix Version field.
For example:
"Fix Version": "12.11.1986"
"Followers" User logins and names Searching for issues with specific followers.
For example:
"Followers": user3370@, "Alice Little"
"Has Epic" Issue keys Searching for issues that refer to specific epics.
For example:
"Has Epic": TASK-123
"Have Links To Queue" 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).
For example:
"Have Links To Queue": TEST
"History" Text string Searching for issues with a history that includes the words or forms of words from a specific phrase.
A search is only made by the Summary and Description field values.
For example:
"History": "easy as pie"
"In Epics Of Queue" Queue names or keys Searching for issues related to epics from specific queues.
For example:
"In Epics Of Queue": TEST
"Is Dependent By" Issue keys Searching for issues that block specific issues.
For example:
"Is Dependent By": "TASK-123", "TASK-321"
"Is Duplicated By" Issue keys Searching for issues that are duplicated by specific issues.
For example:
"Is Duplicated By": "TASK-123", "TASK-321"
"Is Epic Of" Issue keys Searching for epics that include specific issues.
For example:
"Is Epic Of": "TASK-123", "TASK-321"
"Is Parent Task For" Issue keys Searching for issues that are parent to specific issues.
For example:
"Is Parent Task For": "TASK-123", "TASK-321"
"Is Subtask For" Issue keys Searching for sub-issues for specified parent issues.
For example:
"Is Subtask For": "TASK-123", "TASK-321"
"Key" Issue keys Searching for issues with specific keys.
For example:
"Key": "TASK-123", "TASK-321"
"Last comment" Date and time when the last comment was posted Searching for issues that didn't receive any new comments during a particular timeframe.
For example:
"Last Comment": < now()-1h
"Linked to" Issue keys Searching for issues that are somehow linked with the specified issues (parent, related, duplicate, sub-issue, and so on).
For example:
"Linked to": "TASK-123", "TASK-321"
"Modifier" User logins and names Searching for issues recently updated by specific users.
For example:
"Modifier": user3370@, "Alice Little"
"Old Queue" Queue names or keys Searching for issues moved from the specified queues.
For example:
"Old Queue": TEST
"Original" Issue keys Searching for clones of specified issues.
For example:
"Original": "TASK-123", "TASK-321"
"Original Estimate" Time range in the format "XXw XXd XXh XXm XXs" Searching for issues with a specific initial estimate.
For example:
"Original Estimate": "5d 2h 30m"
"Originals Of Queue" Queue names or keys Searching for issues that have clones in specific queues.
For example:
"Originals Of Queue": TEST
"Parent Tasks For Queue" Queue names or keys Searching for issues that have sub-issues in specific queues.
For example:
"Parent Tasks For Queue": TEST, DEVELOP
"Pending Reply From" User logins and names Searching for issues with a pending reply from a specific 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 user3370 or a user with the first and last name Alice Little:
"Pending Reply From": user3370@, "Alice Little"
"Priority" Priority value Searching for issues with a specific priority.
For example:
"Priority": "Minor", "Normal"
"Project" Project titles Searching for issues from specific projects.
For example:
"Project": "Perpetuum mobile"
"Queue" Queue names or keys Searching for issues from specific queues.
For example:
"Queue": TEST
"Queue Owner" User logins and names Searching for issues from queues with specific owners.
For example:
"Queue Owner": user3370@, "Alice Little"
"Related" User logins and names Searching for issues with specific reporters, assignees, or followers.
For example:
"Related": user3370@, "Alice Little"
"Related To Queue" Queue names or keys Searching for issues that are related to issues from specific queues (the Related link type).
For example:
"Related To Queue": TEST
"Relates" Issue keys Searching for issues related to specific issues (the Related link type).
For example:
"Relates": "TASK-123", "TASK-321"
"Resolved" Date or date range Searching for issues that were closed (resolved) on a specific date or during a specific date range.
For example:
"Resolved": 2017-01-01..2017-01-30
"Resolver" User logins and names Searching for issues that were closed (resolved) by a specific users.
For example:
"Resolver": user3370@, "Alice Little"
"Sprint" Sprint names or IDs Searching for issues from specific sprints.
For example:
Sprint: "TrackerSprint32"
"Sprint In Progress By Board" Issue Board ID (can be found in the Board page URL) Searching for issues related to an active sprint on a specific issue board.
For example:
"Sprint In Progress By Board": 87
"Sprints By Board" Issue Board ID (can be found in the Board page URL) Searching for issues from specific boards.
For example:
"Sprints By Board": 87
"Start Date" Date or date range Searching for issues whose Start date value matches a specific date or date range.
For example:
"Start Date": <2017-01-30
"Status" Status names Searching for issues with specific statuses.
For example:
"Status": Open, Resolved, Closed
"Story Points" Story Points score Searching for issues with a specific number of Story Points.
For example:
"Story Points": >=5
"Subtasks For Queue" Queue names or keys Searching for sub-issues that have parent issues in the specified queues.
For example:
"Subtasks For Queue": TEST
"Summary" Text string Searching for issues whose name contains specific text.
For example:
  • Find issues that have a title containing the words and word forms in the phrase:
    "Summary": "invent the wheel"
  • Find issues whose name completely matches the following phrase:
    "Summary": #"invent the wheel"
"Tags" Issue tags Searching for issues with specific tags.
For example:
"Tags": "Support", "wiki"
"Time Spent" Time range in the format "XXw XXd XXh XXm XXs" Searching for issues with a specific amount of time spent.
For example:
"Time Spent": >"5d 2h 30m"
"Type" Issue type Search for issues with the specified type. For example:
"Type": Epic
"Updated" Date or date range Searching for issues updated on a specific date or within a specific date range.
For example:
"Updated": >2017-01-30
"Voted by" User logins and names Searching for issues that have been voted for by specific users.
For example:
"Voted By": user3370@, "Alice Little"
"Votes" Number of votes Searching for issues with a specific number of votes.
For example:
"Votes": > 6

Was the article helpful?

Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
In this article:
  • Query format
  • Multiple parameter values
  • Filters with multiple conditions
  • Searching by text
  • Searching by user
  • Searching by local field
  • Date and time parameters
  • Comparison operations
  • Functions
  • Searching by parameter change
  • Sorting results
  • Useful queries
  • Filter parameters