Contextual Help. Search for Issues

Search
Searching YouTrack Documentation
Table of Contents

You search for issues by composing a search query. A search query must contain one or more of the following:

  • Keyword-value pairs (example: project: TeamCity) that identify attributes of issues that you search for. Issue attributes include issue ID, state, assignee, reporter, date of creation/update, type, priority, tags etc. For unambiguous values, you may omit keywords. For example, state: unresolved means exactly the same as #unresolved because #unresolved can only identify the state of an issue. On the other hand, #today is an ambiguous value because it is valid for two keywords: updated and created.
  • Shortcut keywords that represent one of the following:
    • A set of attribute values. Examples: #my (searches for issues assigned to or reported by the current user), #unresolved (searches for all submitted, open, reopened issues, issues in progress and due to be discussed).
    • A special state of an issue. Examples: #unassigned, #{has attachment}.
  • An arbitrary string for full-text search in issue summaries, descriptions etc.

To distinguish search by attributes from full-text search:

  • Attributes should be followed by a colon:
    state:
  • Attribute values that contain spaces should be surrounded by curly braces:
    in: {JetBrains Tracker}
  • If an attribute value is specified without attributes, it should be preceded by the hash mark:
    #unresolved

You can also use the "-" operator to subtract subsets from search query results. For example, #unresolved -critical displays all unresolved issues except for critical issues. Note that using the "-" operator before an attribute value doesn't require that you precede it with a hash mark.

YouTrack provides query completion in the search box to help you choose appropriate keywords and values. To display query completion at any caret position in the search box, press Ctrl+Space or Alt+Down.
In addition, after you have entered them in the search box, keywords are underlined with grey and values with black. If you've entered an incorrect query, YouTrack uses red dotted underline to highlight errors.

Most of the following commands are applicable in the Command window as well but if you use them in commands, the aforementioned rules regarding colons, curly braces and hash marks are not applied.

Keyword Possible values Keyword meaning Sample query Sample query meaning
my none Issues assigned to or reported by current user
#my #unresolved
or
#my #unresolved #issues
"Find all issues assigned to or reported by current user that have any state except resolved"
me none Issues assigned to or reported by current user
#issues assigned to: me or reported by: me
is equal to
#me
"Find all issues that were assigned to or reported by current user"
for user login User that an issue was assigned to
priority: show-stopper for: John
"Find all issues with priority show-stopper that were assigned to user John"
assigned to Same as "for"
unassigned none Issues that were not assigned to a specific user
project: ReSharper #unassigned
"Find unassigned issues (with empty assignee) in project ReSharper"
by user login User that created an issue
#bug by: yaegor -minor -normal
"Find all bugs reported by user yarko except for those with minor or normal priority"
created by Same as "by"  
#issues created by: me #today
or
#today by: me
"Find all issues reported by current user today"
updater user login
me
User that updated an issue
updater: me updated: yesterday priority: major
or
updater: me #yesterday #major
"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
#XX-2 #MPS-3143
"Find two specific issues: XX-2 and MPS-3143"
state -new-
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.
#{won't fix} #critical #bug for: john
or
state: {won't fix} priority: critical #bug for:john
"Find all critical bugs assigned to user john that were closed with state won't fix"
created older
today
yesterday
last week
this week
last month
this month
Time span during which an issue was created
#my #issues created: today
or
#my created: today
"Find all issues that were created today and assigned to current user"
updated older
today
yesterday
last week
this week
last month
this month
Time span during which an issue was last updated
#mps updated: {this month} #resolved
"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
#exception assigned to: me
"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
#my #unresolved #show-stoppers
#my state: unresolved priority: show-stopper
"Find all unresolved issues with priority show-stopper assigned to me"
commented
Since YouTrack Daring
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.
#YouTrack for:me commented:{Last Week}
"Find all issues in project YouTrack assigned to the current user which were commented during the last week."
commented by
Since YouTrack Daring
username Search for issues that were commented by specified user.
created:today for:me commented by:John
"Find all issues which were created today, assigned to the current user, and commented by John."
project administrator-defined Name of a project configured in your YouTrack installation that an issue belongs to
#my #ReSharper #issues
or
#my #ReSharper
"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
subsystem: {smart ui}
"Find all issues that belong to subsystem smart ui"
in project or subsystem Specifies project or subsystem that an issue belongs to
#issues created by: kostik in: MPS
"Find all issues reported by user kostik in project MPS"
affects administrator-defined Code of version where an issue was observed
affects: EAP3 assigned to: John
or
#issues affecting: EAP3 assigned to: John
or
#issues that affect: EAP3 assigned to: John
"Find all issues assigned to user John that were observed in version EAP3"
that affect Same as "affects"
affecting Same as "affects"
fixed in administrator-defined Code of version where an issue was fixed
for: John fixed in: EAP3
"Find all issues assigned to user John that were fixed for version EAP3"
tag user-defined Tag assigned to an issue
#minor tag: myparser
or
#minor #issues tagged as: myparser
"Find all issues with priority minor that were associated with tag myparser"
tagged as Same as "tag"
saved search user-defined Name of a previously saved search query
saved search: {resharper this week}
"Re-execute search query that was saved as resharper this week"
sort by name of any other category Sort criteria
#my #fixed sort by: updated desc
"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"
asc, desc none Sort order for sort criteria specified by the "sort by" keyword
#unresolved sort by: priority asc
"Find all unresolved issues and sort the list of issues by priority in ascending order"
has attachment none Filter for issues that contain attachments
#unresolved #{has attachment}
"Find all unresolved issues with attached files"
Note that this shortcut keyword is used according to rules for attribute values - that is, it requires both a hash mark and curly braces.

Labels

 
(None)