The following table lists keywords that are provided in YouTrack query language to denote attributes before specifying their values, among other purposes. For every keyword, all supported attribute values, description, and sample queries are provided.
Note that you can use both singular and plural forms for predefined attribute values. For example, #my #show-stopper and #my #show-stoppers yield identical results.
See Search Query Grammar for details on YouTrack syntax rules.
Advanced Text Search Options
Here's the list of the new expanded text search options and search attributes:
Please note that in text search you can use '*' and '?' wildcards.
| Attribute | Values | Keyword meaning | Sample query |
|---|---|---|---|
| summary | {"phrase"} {words} |
Search in issue summary | Find issues with the words 'scrum' and 'board’ in the summary: In project TS, find issues assigned to user 'john.johnson' with the phrase 'Agile management' in description: |
| description | {"phrase"} {words} |
Search for text in issue description | In project 'GR', find unresolved issues with the phrase 'groovy.lang.resolve.CollectClassMembersUtil' in description: |
| comment | {"phrase"} {words} |
Search for text in a comment | In project JT, find issues of type 'Feature' with 'Agile management' subsystem, that have comments containing the word 'burndown': |
| attachments | filename | Search for issues with attached files with specified filename | Find unresolved issues assigned to me that have attached files with filename starting with ‘sketch’: |
| code | {"phrase"} {words} |
Search for text within {code} tags.
|
In project 'TS', find unresolved issues with 'foo' and 'bar' within the {code} tags in a description or comment: |
Search Query Operators and Specific Symbols
| Operator or symbol |
Description |
Sample query |
|---|---|---|
| - | The minus operator allows excluding a subset from a set of search query results. Note that using this operator with an attribute value doesn't require that you precede it with a hash mark. | Find all unresolved issues except for issues with minor priority; sort the list of results by priority in ascending order: |
| OR | This operator allows you to combine multiple search attribute subsets thus expanding the search request. | Find all issues in project "TEST" assigned to the current user or issues tagged "to be tested" (in any project): |
| , | The comma allows listing several values for an attribute. Can be combined with a range. | Find all issues assigned to, reported or commented by the current user, which were created yesterday or today: |
| .. | Two-dots sign between two values defines a range of values. | Find all issues fixed in version 1.2.1 and in all versions from 1.3 to 1.5: Find all issues created since March 10 till March 13, 2011: |
| # | The hash mark should precede Shortcut Keywords and single values. | Find all unresolved issues in project "MRK", which were reported by, assigned to, or commented by the current user: |
| { } | Curly braces should surround attribute values with spaces. | Find all issues with state "Fixed" and tagged "to be tested": |
| * | YouTrack supports wildcards in search requests. Please note that currently only wildcards specified in the end of an attribute's value are supported. | Find all issues fixed in builds 3.2.1, 3.2.2, 3.2.2.1 in the project 'Test': |
Shortcut Keywords
All search query attributes in the following table are so called shortcut keywords which should be used in an search query without any values, and always preceded by the hush mark "#" or the minus operator. In the YouTrack Search Query Grammar these keywords corresponds to <SingleValue>.
 | Please note that some of the values mentioned in the General Search Attributes section below can also be used in a search queue as a <SingleValue>. |
| Keyword | Keyword meaning | Sample query | ||
|---|---|---|---|---|
| me or my | Issues assigned to, reported by, or commented by the current user. | "Find all issues assigned to or reported by current user that have any state except resolved": |
||
| user name | Issues assigned to, reported by, or commented by the specified user | "Find all issues that were assigned to, or reported by, or commented by the user "john" and were updated Yesterday ": |
||
| issueID | Search an issue by its issueID. Notice, that the hash mark is not mandatory to search for an issue ID. Also, when you search for particular issueID, the issue, if found, will be opened in the full-screen mode, skipping search results list. | Find an issue with issueID 'jt-4232': |
||
| viewed or read |
Issues that have been "touched" by the current user — expanded in the issue list, or opened in the full screen mode — at least once.
|
"Find all tasks created yesterday and assigned to me, which I already viewed": |
||
| {not viewed} or unread |
Issues that have never been expanded in the issue list or opened in the full screen mode by the current user.
|
"Find all usability problems reported or updated this week, assigned to me, but which I have not yet viewed:" |
||
| unassigned | Issues that were not assigned to a specific user | "Find unassigned issues (with empty assignee) in project ReSharper:" |
||
| asc, desc | Sort order for sort criteria specified by the "sort by" keyword | "Find all unresolved issues and sort the list of issues by priority in ascending order:" |
||
| {has attachment} |
Filter for issues that contain attachments |
"Find all unresolved issues with attached files:" |
||
| Resolved | Filter for issues with State considered as resolved, for example; Fixed, Duplicate, Obsolete, etc. | 'Find all resolved issues, which were updated today:' |
||
| Unresolved | Filter for issues with State considered as unresolved, for example; Submitted, Open, In progress, etc. | 'Find all unresolved issues assigned to john.doe in project Test:' |
General Search Attributes
The following table include all supported search attributes with their values and description. These attributes define <Attribute> in the Search Query Grammar and their values correspond to <Value> parameter.
| Attribute | Values | Keyword meaning | Sample query | ||
|---|---|---|---|---|---|
| has | star comments links attachments votes <link name> -<field name> |
Search for issues which have star tag, comments, links, votes, or links of the specific name. |
"In project "TST", find all issues assigned to the currently logged-in user, which have duplicate link and have attachments, but have no comments": |
||
| commented | <date> <custom period> Today Yesterday {This week} {This month} {Last week} {Last month} Older username |
Search for issues that were commented during specified period or by specified user. Particular date and time can be specified in the following format: YYYY-MM-DD or YYYY-MM or MM-DD. You also can specify particular time: HH:MM:SS or HH:MM in 24h format. If you wish to use both date and time, then use the following format: YYYY-MM-DD}}T{{HH:MM:SS , For example: the search query created: 2010-01-01T12:00 .. 2010-01-01T15:00 will find all issues that were created on January, 1st, 2010 between 12:00 and 15:00 |
"Find all issues in project YouTrack assigned to the current user, which were commented during the last week:" |
||
| commented by or commenter |
username | Search for issues that were commented by specified user. | "Find all issues which were created today, assigned to the current user, and commented by John:" |
||
| relates to duplicates is duplicated by depends on is required for |
issue ID | Search for issues that have links of specified type to certain issues.
|
"Find all tasks assigned to the current user, which either relate to JT-5072 or duplicate JT-4367:" |
||
| links | issueID | Specifies an issue, to which issues to be find have any links. | "In project TEST find all issues, which are linked with an issue ABC-4532:" |
||
| for assigned to |
user login | User that an issue was assigned to | "Find all issues with priority show-stopper that were assigned to user John:" |
||
| by created by |
user login me |
User that created an issue | "Find all bugs reported by user yarko except for those with minor or normal priority:" |
||
| updater updated by |
user login me |
User that updated an issue | "Find all major issues updated yesterday by the current user" |
||
| issue id | issue identifier | Automatically generated issue identifier, typically consisting of project short name and number code | "Find two specific issues: XX-2 and MPS-3143:" |
||
| state | submitted open in progress reopened resolved unresolved fixed won't fix can't reproduce duplicate incomplete obsolete to be discussed |
The current state of an issue Note that resolved and unresolved are special states that can't be assigned to an issue but instead are used to search for issues that can have any state from a specified set. resolved covers the following states: fixed, won't fix, duplicate, incomplete, obsolete, can't reproduce. unresolved covers the following states: submitted, open, in progress, reopened, to be discussed. |
"Find all critical bugs assigned to user john that were closed with state won't fix:" |
||
| created | <date> <custom period> older today yesterday last week this week last month this month |
Time span during which an issue was created. Particular date and time can be specified in the following format: YYYY-MM-DD or YYYY-MM or MM-DD. You also can specify particular time: HH:MM:SS or HH:MM in 24h format. If you wish to use both date and time, then use the following format: YYYY-MM-DD}}T{{HH:MM:SS , For example: the search query created: 2010-01-01T12:00 .. 2010-01-01T15:00 will find all issues that were created on January, 1st, 2010 between 12:00 and 15:00 |
"Find all issues that were created today and assigned to current user": |
||
| updated | <date> <custom period> older today yesterday last week this week last month this month |
Time span during which an issue was last updated. Particular date and time can be specified in the following format: YYYY-MM-DD or YYYY-MM or MM-DD. You also can specify particular time: HH:MM:SS or HH:MM in 24h format. If you wish to use both date and time, then use the following format: YYYY-MM-DD}}T{{HH:MM:SS , For example: the search query created: 2010-01-01T12:00 .. 2010-01-01T15:00 will find all issues that were created on January, 1st, 2010 between 12:00 and 15:00 |
"Find all resolved issues in project mps that were updated during this month": |
||
| type | bug task feature cosmetics exception meta issue usability problem performance problem |
One of several predefined types of an issue | "Find all issues of type exception assigned to current user": |
||
| priority | minor normal major critical show-stopper |
One of several predefined priority levels of an issue | "Find all unresolved issues with priority show-stopper assigned to me": |
||
| project | administrator-defined | Name of a project configured in your YouTrack installation that an issue belongs to | "Find all issues within project ReSharper assigned to current user": |
||
| subsystem | administrator-defined | Name of a subsystem within a project that an issue belongs to | "Find all issues that belong to subsystem smart ui": |
||
| <custom field> | administrator-defined | Specifies any existing custom field of an issue. | "Find all issues assigned to the current user with the deadline set for today": |
||
| in | project or subsystem | Specifies project or subsystem that an issue belongs to | "Find all issues reported by user kostik in project MPS": |
||
| affects that affect affecting |
administrator-defined | Code of version where an issue was observed | "Find all issues assigned to user John that were observed in version EAP3": |
||
| fix for | administrator-defined | Code of version where an issue should be fixed. | "Find all issues in project Test assigned to user John, which should be fixed for version 1.0.2": |
||
| fixed in | administrator-defined | Code of version where an issue was fixed | "Find all issues assigned to user John that were fixed for version EAP3": |
||
| tag tagged as |
user-defined | Tag assigned to an issue | "Find all issues with priority minor that were associated with tag myparser" |
||
| saved search | user-defined | Name of a previously saved search query | "Re-execute search query that was saved as resharper this week": |
||
| sort by order by |
name of any other category | Sort criteria | "Find all issues with state fixed that were either assigned to or reported by current user, and sort them by date of last update in descending order, displaying the most recently updated issue first": |
Sort Attributes
The following list is the list of all issue's attributes (search keywords), by which search results can be sorted. In the Search Query Grammar these attributes define <SortAttribute> value.
|
|
|