Text Search

Syntax for Text Search

Any input that is not parsed as an attribute-based search is parsed as a text search.

Consider the following example. When you search for a value in an attribute that contains spaces, you set the value in braces. If you don't follow this rule, the first word in the value is parsed as the value for the attribute that precedes it. Any word that follows is parsed as text.

The highlighting in this search query shows that the word in has been parsed as a value for the State field, which is invalid. The word progress is not highlighted and has been parsed as text.

Follow these guidelines to search for text in a query:

• Enter a single word to find issues that contain matching forms for this word.

  If the language has been indexed, YouTrack also returns issues that contain morphological variants of the specified word or words.

• Enter multiple words to find issues that contain all of the specified words in any order.
• Set text in quotes to find issues that contain words as a phrase.

  A phrase is defined as a consecutive grouping of word forms that match the text in the search query and appear in the same order. If the phrase contains a stop word, the stop word is replaced by any word in the issue.

• Use wildcards to expand the text search to include characters that do not exactly match your search criteria.

  For more information, see Wildcards in Text Search.

If you do not specify which attribute to search in, YouTrack returns all issues that contain matching words and their morphological variants in any attribute, including custom fields.

Text Attributes

You can limit the search to find words in the issue summary, description, comments, attachment filenames, or inside code blocks. These attributes store data as strings as text.

When you specify a text attribute, the query is executed as text search. Instead of searching for an exact match for the specified value, YouTrack returns issues that contain matching word forms inside the string of text that is stored in the specified attribute.

For example, the query Subsystem: {Agile Board} returns only issues that are assigned the value Agile Board in the Subsystem field. This is an attribute-based search and returns only exact matches. The query description: "Agile Board" returns any issue that contains matches for the words "Agile Board" as a phrase in the issue description. This is a text search and returns possible matches in the specified attribute. The results include issues with descriptions that contain other variants like "agile boards".

Sorting by Relevance

When you perform a text search, the results are sorted by relevance. This sort option is applied to search results under the following conditions:

• The search query contains at least one string that is parsed text search. This includes attribute-based search queries that search for text matches in the summary, description, comments, attachment filenames, and code.

• The search query does not contain an explicit sort attribute. The explicit sort attribute overrides the default sort by relevance.

• The search query does not contain an OR expression.

Results are also sorted by relevance for saved searches that meet this criteria. However, if the saved search stores a custom order, the custom order overrides sorting by relevance.

• Issues that have been ordered manually appear in the custom order.

• Issues that have not been ordered manually are sorted by last update.

Sorting by relevance is applied to text searches by default. You cannot specify relevance as a sort attribute. The current sort order is displayed directly under the search box.

Relevance is based on the number of matching word forms that are found in each issue. Matches in the issue summary are given a slightly higher weight than matches in other issue attributes. Issues with multiple matches in the description, comments, or other issue attributes will have higher relevance than issues with a single match in the summary.

Wildcards in Text Search

You can use wildcards as a placeholder for one or more characters.

• * — matches zero or more characters in a string. You can also use this wildcard at the end of a value in an attribute-based search. For more information, see Wildcards in Attribute-based Search.

• ? — matches any single character in a string. You can only use this wildcard to search in text attributes. You cannot use this wildcard to search for values in custom fields, even when the field store values as a string type.

You can use a wildcard at the beginning, middle, or end of any word.

Stop Words

If you use English as the default language in YouTrack, there are a number of common words that are filtered out before the search query is processed. These words are removed to improve query performance. When you enter a stop word in a phrase, it is replaced by any word in the search results. Single stop words that are not set in quotes are simply ignored. Stop words are not highlighted in the search results. The following stop words are ignored by YouTrack:

Search Results

The list of issues that is displayed when you use text search highlights all of the word forms that match the words that are specified in the query.

When you search for a sequence of words set in quotes, the query returns only issues that contain forms for each word in the specified order. Word forms that match any of the specified words are highlighted in the results. At first glance, you may think that the search has returned issues that don't match your query. If you open each issue, however, you can see that the issue contains the sequence of words that match your search criteria.

If your text search returns too many issues, use additional search parameters to limit the results to a specific project, subsystem, or issue type. You can also limit the results to show issues that include the text only in the summary, description, or comments.

Stemming

If text indexing is enabled for the language that you use in YouTrack, related words are mapped to a common stem word. When you search for text, YouTrack returns issues that contain all forms of the words that you enter in a search query. For example, the search query description: {search attribute} returns not only issues that contain either the words 'search' or 'attribute' in the description, but also any issue that contains other forms of these words, including 'searches', 'searched', 'searching', 'attributes', 'attribution', and so on. This feature helps you locate issues that might otherwise be excluded if the results included only exact word matches.

Text indexing is automatically enabled for all default languages. This means that stemming is enabled for all issue attributes that store strings of text in any of the languages that are provided out-of-the-box in YouTrack. For English, text indexing cannot be disabled.

For more information, see Text Index.

Tokenization

YouTrack breaks down each word in a string of text into tokens. All contiguous strings of alphabetic or numeric characters are part of one token. When you search for multiple words, the query is interpreted as a string of tokens.

• When the words are set in braces, each token is evaluated separately. The search results include all issues that contain any words that match any token in the query.

• When the words are set in quotation marks, the tokens are evaluated as a sequence. The search results include only issues that contain words that match all tokens in the specified order.

YouTrack returns issues that contain the words that correspond to the tokens that are specified in the search. The text in an issue is broken down into words. Whitespaces and punctuation are used to determine where the words begin and end. Periods and underscores are also recognized as delimiters.

Fuzzy Search

To find words that match an approximate pattern, instead of an exact pattern, use a fuzzy search. Fuzzy search finds words that are just a few characters off from the word that is specified in the search query. This technique helps you account for misspellings, partial words, and slight differences in names.

For example, the search query comments: {michael~} returns issues that include not only the name Michael in the comments but also other spellings like Mikhail.

Fuzzy matching usually returns a large number of irrelevant matches Use this option only when you know that the word you are searching for is likely to be misspelled.