YouTrack InCloud 2017.3 Help

Search Query Reference

This page provides a list of attributes and keywords that are used in YouTrack query language. Each attribute is followed by a value in a search query. Keywords represent a single value.

For predefined attribute values, you can use both singular and plural forms. For example, #my #show-stopper and #my #show-stoppers yield identical results.
For more information on YouTrack search syntax, see Search Query Grammar.

Text Search

YouTrack lets you search for issues that contain words or combinations of words. You can either search for words in any issue attribute, or limit the search query to find words in a specific attribute.

If text indexing is enabled for the language that you use in YouTrack, YouTrack returns issues that contain all forms of the words that you enter in a search query. Text in English is indexed by default. For more information, see Text Search.

Follow these guidelines to search for text in a query:

  • Enter a single word to find issues that contain this word. If the language has been indexed, YouTrack also returns issues that contain morphological variants of the specified word.
  • Set multiple words in braces to find issues that contain any of these words in any order. If the language has been indexed, YouTrack also returns issues that contain morphological variants of the specified words.
  • Set text in quotes to find issues that contain words in a specific order. If the language has been indexed, YouTrack returns issues that contain variants of every word in the specified order.
  • Use wildcards to expand the text search to include characters that do not exactly match your search criteria.
    • * — matches zero or more characters in a string. You can also use this wildcard in other search attributes. For more information, see Wildcards in Search Attributes
    • ? — matches any single character in a string. You can only use this wildcard to search the text attributes that appear in the following table. You cannot use this wildcard to search for values in custom fields that store values as a string type.

If you do not specify which attribute to search in, YouTrack returns all issues that contain matching words and their morphological variants in any text attribute. You can limit the search to find words in one of the following attributes.

AttributeValuesDescriptionExamples
summaryword
{multiple words}
"sequence of words"
Returns issues that contain word forms that match the specified word or words in the issue summary.To find issues with either 'scrum' or 'board' in the summary, enter:
summary: {scrum board}
To find issues in the 'TS' project that are assigned to the user 'john.johnson' with the words 'Agile management' in the summary (appearing in this order), enter:
in: TS assigned to: john.johnson summary: "Agile management"
descriptionword
{multiple words}
"sequence of words"
Returns issues that contain word forms that match the specified word or words in the issue description.To find unresolved issues in the 'GR' project with the string 'groovy.lang.resolve.CollectClassMembersUtil' in the description, enter:
in: GR #unresolved description: "groovy.lang.resolve.CollectClassMembersUtil"
commentsword
{multiple words}
"sequence of words"
Returns issues that contain word forms that match the specified word or words in a comment.To find issues in the 'JT' project with the type 'Feature' in the 'Agile management' subsystem that have comments that contain the word 'burndown', enter:
in: JT #Feature Subsystem: {Agile management} comments: burndown
attachmentsfilenameReturns issues that include attachments with the specified filename.To find unresolved issues that are assigned to me and have an attachment with a filename that starts with 'sketch', enter:
#unresolved for: me attachments: sketch*
codeword
{multiple words}
"sequence of words"
Returns issues that contain word forms that match the specified word or words inside {code} markup tags.
The {code} markup can be used in the issue description and comments. When you search by code, the query returns issues that contain variants of the specified words in the description or a comment.
To find unresolved issues in the TS project with the words 'foo' and 'bar' inside {code} tags in a description or comment, enter:
in: TS #unresolved code: {foo bar}

Operators

Use the following operators to create logical combinations of attributes in a search query.

OperatorDescriptionExamples
-Exclude a subset from a set of search query results. When you use this operator with an attribute value, do not use the number sign.To find all unresolved issues except for issues with minor priority and sort the list of results by priority in ascending order, enter:
#unresolved -minor sort by: priority asc
ANDCombine multiple search attribute subsets to expand the search request. Use this operator for issue fields with enum[*] types and tags.
The AND-expression is always processed as group and has a higher priority than OR-expressions in the query.
To find all issues in the 'TEST project' that have both the 'Next build' and 'to be tested' tags, enter:
in: TEST and (tag:{Next build} and tag:{to be tested})
To find all issues that are have the priority 'Critical' in project 'A' or have the priority 'Major' and are assigned to the current user in project 'B', enter:
in: A #Critical or in: B #Major and for: me
ORCombine multiple search attribute subsets to restrict the search request. To find all issues in the 'TEST' project that are assigned to the current user or have the tag 'to be tested' in any project, enter:
in: TEST for: me or tag: {to be tested}
( )Combine various search attributes to change the order in which attributes and operators are processed. The part of a search query inside the parentheses has priority and is always processed as a single unit.

A parentheses-expression can be used only as argument for OR- or AND-expressions. For example, the search query in:A #Critical (in:B and for:me) cannot be processed.

To find all issues that are assigned to the current user and are either 'Critical' in project 'A' or 'Major' in project 'B', enter:
(in: A #Critical or in: B #Major) and for: me

Symbols

The following symbols can be used to extend or refine a search query.

SymbolDescriptionExamples
,List multiple values for a single attribute. Can be used in combination with a range.To find all issues assigned to, reported or commented by the current user, which were created today or yesterday, enter:
#my created: Today, Yesterday
..Defines a range of values.To find all issues fixed in version 1.2.1 and in all versions from 1.3 to 1.5, enter:
fixed in: 1.2.1, 1.3 .. 1.5
To find all issues created since March 10 until March 13, 2011, enter:
created: 2011-03-10 .. 2011-03-13
#Indicates that the attribute is a keyword or a single value. To find all unresolved issues in the 'MRK' project that were reported by, assigned to, or commented by the current user, enter:
#my #unresolved in: MRK
{ }Encloses attribute values that contain spaces.To find all issues with the 'Fixed' state that have the tag 'to be tested', enter:
#Fixed tag: {to be tested}

Keywords

The attributes in the following table are keywords. When you use a keyword in a search query, you do not specify a value for the attribute. A keyword is preceded by the number sign (#) or the minus operator. In the YouTrack Search Query Grammar, these keywords correspond to a <SingleValue>.

KeywordDescriptionExamples
me
my
Returns issues that are assigned to, reported by, or commented by the current user.To find all issues assigned to or reported by current user that have any state except 'Resolved', enter:
#issues assigned to: me or reported by: me -Resolved

returns the same result as #me -Resolved and #my -Resolved

userReturns issues that are assigned to, reported by, or commented by the specified user.To find all issues that were assigned to, or reported by, or commented by the user with the login 'john' and were updated yesterday, enter:
#john updated: Yesterday
issue IDReturns an issue with the specified ID. You do not need to use the number sign to search by issue ID. When you search for an issue by ID, the result is displayed in full page view. To find an issue with the ID 'JT-4232', enter:
JT-4232
unassignedReturns issues that are not assigned to a specific user.To find unassigned issues in the 'ReSharper' project, enter:
project: ReSharper #unassigned
{has attachment}Returns issues that include attachments. This keyword follows the syntax for attribute values and requires both the number sign and braces. To find all unresolved issues with attachments, enter:
#unresolved #{has attachment}
resolvedReturns issues that are assigned a State that is considered to be resolved. For example, Fixed, Duplicate, or Obsolete.To find all resolved issues that were updated today, enter:
#resolved updated: Today
unresolvedReturns issues that are assigned a State that is considered to be unresolved. For example, Submitted, Open, or In Progress.To find all unresolved issues that are assigned to the user 'john.doe' in the 'Test' project, enter:
#unresolved project: Test for: john.doe

Boolean Search

The has keyword functions as a Boolean search term. When used in a search query, it returns all issues that contain a value for the specified attribute. Use the minus operator (-) before the specified attribute to find issues that have empty values.

For example, to find all issues in the 'TST' project that are assigned to the current user, have a duplicates link, have attachments, but do not have any comments, enter:
in: TST for: me has: duplicates , attachments , -comments

You can use the has keyword in combination with the following attributes:

AttributeDescription
attachmentsReturns issues that have attachments.
{Board <board name>}Returns issues that are assigned to the specified agile board.
commentsReturns issues that have comments.
descriptionReturns issues that do not have an empty description.
<field name>Returns issues that contain any value in the specified custom field. Enclose field names that contain spaces in brackets.
<link name>Returns issues that have links that match the specified outward name or inward name. Enclose link names that contain spaces in brackets.
linksReturns issues that have any issue link type.
starReturns issues that have the star tag for the current user.
votesReturns issues that have one or more votes.
workReturns issues that have one or more work items.

Search Attributes

The following table includes all supported search attributes and their corresponding values. These attributes represent an <Attribute> in the Search Query Grammar. Their values correspond to the <Value> or <ValueRange> parameter.

AttributeValuesDescriptionExamples
commented<date>
<custom period>
relative date parameter
user
group
Returns issues to which comments were added on the specified date, within the specified period, by the specified user, or by a member of the specified group.To find all issues in the 'YouTrack' project that are assigned to the current user and were commented during the last week, enter:
#YouTrack for: me commented: {Last Week}
commented by
commenter
user
group
Returns issues that were commented by the specified user or by a member of the specified groupTo find all issues which were created today, assigned to the current user, and commented by the user with the login 'John', enter:
created: today for: me commented by: John
<issue link type>issue IDReturns issues that have links of the specified type to the specified issue. You can enter the outward name or inward name of any issue link type used in your YouTrack instance. To find all tasks that are assigned to the current user and are related to the issue with the ID 'JT-5072' or duplicate the issue with the ID 'JT-4367', enter:
for: me #task relates to: JT-5072 or duplicates: JT-4367
linksissue IDReturns all issues that contains links to the specified issue.To find all issues in the 'TEST' project that are linked to the issue 'ABC-4532', enter:
in: TEST links: ABC-4532
for
assigned to
user
me
group
Returns all issues that are assigned to the specified user, the current user, or a member of the specified group.To find all issues with priority 'Show-stopper' that are assigned to the user with the login 'John', enter:
priority: show-stopper for: John
by
created by
reported by
user
me
group
Returns issues that were created by the specified user, the current user, or a member of the specified user group.To find all bugs reported by the user with the login 'yarko' except for those with minor or normal priority, enter:
#bug by: yarko -minor -normal or
#bug created by: yarko -minor -normal
updater
updated by
user
me
group
Returns issues that were updated by the specified user, the current user, or a member of the specified user group.To find all major issues that were updated yesterday by the current user, enter:
updater: me updated: yesterday priority: major or
updater: me #yesterday #major
issue idissue IDReturns issues that match the specified issue ID. The issue ID is an auto-generated identifier that typically consists of the project short name followed by a dash and a number. To find two specific issues: 'XX-2' and 'MPS-3143', enter:
issue id: XX-2, MPS-3143
state submitted
open
in progress
reopened
resolved
unresolved
fixed
won't fix
can't reproduce
duplicate
incomplete
obsolete
to be discussed
Returns issues that match the specified state.
The Resolved and Unresolved states cannot be assigned to an issue directly, as they are properties of specific values that are stored in the State field.
By default, Fixed, Won't fix, Duplicate, Incomplete, Obsolete, and Can't reproduce states are set as Resolved.
The Submitted, Open, In Progress, Reopened, and To be discussed states are set as Unresolved.
To find all critical bugs that are assigned to the user with the login 'john' that were closed with the state 'Won't fix', enter:
#{won't fix} #critical #bug for: john or
state: {won't fix} priority: critical #bug for: john
created<date>
<custom period>
relative date parameter
Returns issues that were created on a specific date or within a specified time frame.To find all issues that were created today and are assigned to the current user, enter:
#my #issues created: today or
#my created: today
updated<date>
<custom period>
relative date parameter
Returns issues that were updated on a specific date or within a specified time frame. To find all issues that are resolved in the 'MPS' project that were updated this month, enter:
#MPS updated: {this month} #resolved
resolved date<date>
<custom period>
relative date parameter
Returns issues that were resolved on a specific date or within a specified time frame. To find all issues that are resolved in the 'MPS' project this month, enter:
#MPS resolved date: {this month}
type bug
task
feature
cosmetics
exception
meta issue
usability problem
performance problem
Returns issues that match the specified issue type.To find all issues that are assigned the 'Exception' type and are assigned to the current user, enter:
#exception assigned to: me
priority minor
normal
major
critical
show-stopper
Returns issues that match the specified priority level.To find all unresolved issues with the priority 'Show-stopper' that are assigned to the current user, enter:
#my #unresolved #show-stoppers or
#my state: unresolved priority: show-stopper
project<project name>Returns issues that were created in the specified project.To find all issues that were created in the 'ReSharper' project that are assigned to current user, enter:
#my #ReSharper #issues or
#my #ReSharper
subsystem<field value>Returns issues that are assigned to a specific subsystem within a project.To find all issues that belong to the 'Smart UI' subsystem, enter:
subsystem: {smart ui}
<custom field><field value>Returns issues that contain a matching value in the specified custom field.To find all issues that are assigned to the current user with the a value in the 'Deadline' field that matches today's date, enter:
for: me Deadline: Today
inproject or subsystemReturns issues that are assigned to the specified project or subsystem.To find all issues that were reported by the user 'kostik' in the 'MPS' project, enter:
#issues created by: kostik in: MPS
that affect<version field value>Returns issues that were detected in the specified version or build.To find all issues that are assigned to the user 'John' that were observed in version 'EAP3' of the product, enter:
affects: EAP3 assigned to: John or #issues affecting: EAP3 assigned to: John or
#issues that affect: EAP3 assigned to: John
fix for<version field value>Returns issues that are to be fixed in a specified version of the product.To find all issues in the 'TEST' project that are assigned to the user 'John' and should be fixed for version '1.0.2' of the product, enter:
in: Test for: John fix for: 1.0.2
fixed in<version field value>Returns issues that were fixed in a specified version of the product.To find all issues that are assigned to the user 'John' that were fixed in version 'EAP3' of the product, enter:
for: John fixed in: EAP3
tag
tagged as
<tag>Returns issues that match a specified tag.To find all issues with the priority 'Minor' that were associated with the 'myparser' tag, enter:
#minor tag: myparser or
#minor #issues tagged as: myparser
saved search<saved search>Returns issues that match the search criteria of a saved search.To find issues that match the search query that was saved as 'resharper this week', enter:
saved search: {resharper this week}
Board <board name><sprint name>Returns issues that are assigned to the specified sprint on the specified agile board. Enclose sprint names with more than one word in braces.

You can also substitute the sprint name with {current sprint} to find issues that are assigned to the current sprint. To learn how YouTrack identifies the current sprint, see Work with Sprints.

To find all issues that are assigned to sprint 21 on the YouTrack scrum board, enter:
Board YouTrack scrum: {sprint 21}

Wildcards in Search Attributes

You can use the * character as a wildcard in search attributes that reference values in many custom fields and sprints. This wildcard matches zero or more characters in the search request. You can only add a wildcard to the end of an attribute value.

  • You can use the * wildcard to find values in custom fields that store an enum, state, ownedField, version, or build. You can also use this wildcard for sprint names.
  • Wildcards are not supported for fields that store a user, date, period, float, or integer.
  • The ? wildcard is not supported in attribute-based search queries, even for custom fields that store a string type.

Search Attributes for Time Tracking

There is a dedicated set of search attributes that you can use to find issues that contain time tracking data. These attributes look for specific values that have been added as work items to an issue.

AttributeValuesDescriptionExamples
work authoruser
me
Returns issues that have work items that were added by the specified user.To find all issues in the 'TST' project that have work items that were added by the current user, enter: in: TST work author: me
work type<work item type>Returns issues that have work items that are assigned the specified work item type. The query work type: {No type} returns issues that have work items that are not assigned a work item type.To find all issues in the 'TST' project that have work items that are assigned the Development work item type, enter: in: TST work type: Development
work date<date>
<custom period>
relative date parameter
Returns issues that have work items that are recorded for the specified date or within the specified time frame.To find all issues in the 'TST' project that have work items that were added last week, enter: in: TST work date: {Last week}

Date and Period Values

Several search attributes reference values that are stored as a date. You can search for dates as single values or use a range of values to define a period.

Specify dates in the format: YYYY-MM-DD or YYYY-MM or MM-DD. You also can specify a time in 24h format: HH:MM:SS or HH:MM. To specify both date and time, use the format: YYYY-MM-DD}}T{{HH:MM:SS. For example, the search query created: 2010-01-01T12:00 .. 2010-01-01T15:00 returns all issues that were created on 1 January 2010 between 12:00 and 15:00.

You can also use pre-defined relative parameters to search for date values. The values for these parameters are calculated relative to the current date according to the time zone of the current user. The actual value for each parameter is shown in the query assist panel.

/help/img/youtrack/2017.3/relativeDateCalculations.png

The following relative date parameters are supported:

ParameterDescription
TodayThe current calendar day.
YesterdayThe previous calendar day.
SundayThe calendar Sunday for the current week.
MondayThe calendar Monday for the current week.
TuesdayThe calendar Tuesday for the current week.
WednesdayThe calendar Wednesday for the current week.
ThursdayThe calendar Thursday for the current week.
FridayThe calendar Friday for the current week.
SaturdayThe calendar Saturday for the current week.
{This week}The period from 00:00 Monday to 23:59 Sunday for the current week.
{Last week}The period from 00:00 Monday to 23:59 for the previous week.
{Two weeks ago}The period from 00:00 Monday to 23:59 for the calendar week two weeks prior to the current date.
{Three weeks ago}The period from 00:00 Monday to 23:59 for the calendar week three weeks prior to the current date.
{This month}The period from the first day to the last day of the current calendar month.
{Last month}The period from the first day to the last day of the previous calendar month.
OlderThe period from 1 January 1970 to the last day of the month two months prior to the current date.

Sort Attributes

You can specify the sort order for the list of issues that are returned by the search query.

AttributeValueSort CriteriaExample
sort by
order by
attribute nameasc
desc
To find all issues with the 'Fixed' state that were either assigned to or reported by the current user, and sort them by the date of the last update in descending order, displaying the most recently updated issue first, enter:
#my #fixed sort by: updated desc

You can sort issues by any of the attributes on the following list. In the Search Query Grammar, these attributes represent the <SortAttribute> value.

star
updated
updater
{resolved date}
project
reporter
{issue id}
votes
summary
<custom field>
Last modified: 6 September 2017