All keywords 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 mark. In the YouTrack [Search Query Grammar] these keywords corresponds to {{<SingleValue>}}. {note}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>}}.{note}
|| Keyword || Keyword meaning || Sample query || Sample query meaning ||
| me | Issues assigned to, reported by, or commented by the current user | {code}#issues assigned to: me or reported by: me{code} is equal to {code}#me{code}| "Find all issues that were assigned to, or reported by, or commented by the current user" |
| {{my}} | Issues assigned to or reported by current user | {code}#my #unresolved{code} or {code}#my #unresolved #issues{code}|"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 | {code}#john updated: Yesterday{code} | "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 | {code}#jt-4232{code} | 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. | {code}for:me #task created:yesterday #read"{code} | "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. | {code}for:me #{Usability Problem} #{this week} #unread"{code} | "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 | {code}project: ReSharper #unassigned{code} | "Find unassigned issues (with empty assignee) in project _ReSharper_"|
| asc, desc | Sort order for sort criteria specified by the "sort by" keyword |{code}#unresolved sort by: priority asc{code} | "Find all unresolved issues and sort the list of issues by priority in ascending order"|
| \{has attachment\} | Filter for issues that contain attachments|{code}#unresolved #{has attachment}{code} | "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.|
h2. 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.
|| Keyword || Values || Keyword meaning || Sample query || Sample query meaning ||
| commented | 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. | {code}#YouTrack for:me commented:{Last Week}{code} | "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. | {code}created:today for:me commented by:John{code} | "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. {note}In the table only default link types are listed. You can use any existing link name in the your YouTrack instance.{note} | {code}for:me #task relates to: JT-5072 or duplicates: JT-4367"{code} | "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. | {code}in: TEST links: ABC-4532{code} | "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 |{code}priority: show-stopper for: John{code}|"Find all issues with priority _show-stopper_ that were assigned to user _John_"|
| by \\ created by | user login \\ me | User that created an issue | {code}#bug by: yaegor -minor -normal{code} or {code}#bug created by: yaegor -minor -normal{code} | "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 | {code}updater: me updated: yesterday priority: major{code} or {code}updater: me #yesterday #major{code} | "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 | {code}issue id: XX-2, MPS-3143{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. | {code}#{won't fix} #critical #bug for: john{code} or {code}state: {won't fix} priority: critical #bug for:john{code} | "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 | {code}#my #issues created: today{code} or {code}#my created: today{code} | "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 | {code}#mps updated: {this month} #resolved{code} | "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 | {code}#exception assigned to: me{code} | "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 | {code}#my #unresolved #show-stoppers{code}{code}#my state: unresolved priority: show-stopper{code} | "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 | {code}#my #ReSharper #issues{code} or {code}#my #ReSharper{code} | "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 | {code}subsystem: {smart ui}{code} | "Find all issues that belong to subsystem _smart ui_"|
| <custom field> | administrator-defined | Specifies any existing custom field of an issue. | {code}for: me Deadline: Today{code} | "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 | {code}#issues created by: kostik in: MPS{code} | "Find all issues reported by user _kostik_ in project MPS"|
| affects \\ that affect \\ affecting | administrator-defined | Code of version where an issue was observed | {code}affects: EAP3 assigned to: John{code} or {code}#issues affecting: EAP3 assigned to: John{code} or {code}#issues that affect: EAP3 assigned to: John{code} | "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. | {code}in: Test for: John fix for: 1.0.2{code} | "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 | {code}for: John fixed in: EAP3{code} | "Find all issues assigned to user _John_ that were fixed for version _EAP3_"|
| tag \\ tagged as | user-defined | Tag assigned to an issue | {code}#minor tag: myparser{code} or {code}#minor #issues tagged as: myparser{code} | "Find all issues with priority _minor_ that were associated with tag _myparser_"|
| saved search | user-defined | Name of a previously saved search query | {code}saved search: {resharper this week}{code} | "Re-execute search query that was saved as _resharper this week_"|
| sort by \\ order by | name of any other category | Sort criteria |{code}#my #fixed sort by: updated desc{code} | "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"|
h2. 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.
{section}
{column}
- 'updated'
- 'updater'
- 'created'
- 'resolved date'
- 'state'
- 'commented'
- 'custom field'
{column}
{column}
- 'commenter'
- 'priority'
- 'type'
- 'project'
- 'subsystem'
- 'affected version'
{column}
{column}
- 'fix version'
- 'assignee'
- 'reporter'
- 'issue id'
- 'votes'
- 'summary'
{column}
{section}
...