Attribute-based Search

Syntax for Attribute-based Search

Each issue has a number of attributes, such as project, state, issue ID, and assignee. In turn, each attribute has a value. When you search, you specify the attribute that you want to check and the value currently assigned to the issues that you want to find.

Use the following guidelines to compose an attribute-based search query:

The key to mastering attribute-based search is knowing which attributes contain the values that are relevant to the issues you want to find. For a complete list of issue attributes that are supported in search queries, see Search Query Reference.

Smart Search Suggestions

When you search for a value that is only used in a specific set of projects, the values suggested for subsequent attributes are restricted to the sets of values used in these projects as well. Values that would be inappropriate to suggest in this context are still available but appear lower in the list.

For example, if you search for items that are assigned the State: On hold, suggestions for additional attributes in the query will prioritize values for fields in projects that also use the On hold state. In this case, the suggested values for the Assignee attribute will de-prioritize users who are not in the list of possible assignees for projects that use the On hold state. You can still choose an assignee who doesn't belong to the suggested set, but the query won't return any matches.

Search Suggestions for User Accounts

Search attributes that reference users display usernames in the auto-completion list. The following example shows how user data is displayed in auto-completion dialogs.

These suggestions are only offered when you are granted the Read User Basic permission in at least one project. If you have not been granted this permission, the only user suggested is your own account.

Wildcards in Attribute-based Search

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, build, or string. You can also use this wildcard for sprint names, project names, and tags.

• 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.

Single Value Search

You can search for specific values without referencing the attribute that stores the value. YouTrack returns issues that contain the specified value in any issue attribute that does not store text.

• To search for single values, substitute the attribute with a number sign and enter the value directly. Use the minus sign to exclude a value.

  To find issues that are in progress that are not support requests, enter:

  #{In Progress} -{Support Request}

• Use keywords to reference specific issue properties. For a complete list of keywords, see Keywords.

  To find a list of issues that you reported, are assigned, or added a comment to that are unresolved, enter:

  #me -Resolved

Searching for a Range of Values

You can search for issues that contain a value inside a range of values for a specified attribute.

YouTrack applies the following logic to search queries that specify a range of values:

• The search results are always inclusive. This means that the query returns issues that contain the values that define the upper and lower bounds and every value in between. To exclude specific values, use the format -<value>.

• For attributes that store simple data types, YouTrack uses a basic mathematical comparison to exclude values that are less than the lower bound and greater than the upper bound. This logic applies to attributes that store a date, date and time, period, integer, and float type. Range search is not supported for attributes that store data as a string type.

• For attributes that store enumerated types, each value in the set is assigned an index number. Values with index numbers less than the lower bound and greater than the upper bound are excluded from the search results.

  These index numbers are assigned to each value based on the sort order that is applied to the set of values. Values can be sorted manually, by name, version, build, or by an additional property like release date or assemble date. This sort order can vary on a per-project basis. To get predictable results when you use a range of values to find issues in multiple projects, each project should use the same sort order for values in the specified field. For more information, see Sort Values in a Set.

  This logic applies to attributes that store enum, ownedField, state, version, and build types. Range search is not supported for projects or attributes that store an enumerated type as a user or group.

The following examples show how to search for ranges of values in attributes that store different types of data. These examples show different formulations for queries that use open and closed ranges.

Searching in Attributes that Store Text

For attributes like the issue summary, description, or comments, the values are stored as text. When you specify one of these attributes in your search query, YouTrack understands that you want to check the specified attribute for one or more words. Instead of attempting to match the value of the attribute exactly, YouTrack searches inside the attribute for matches to the specified text.

The syntax for text search is slightly different from the standard used for an attribute-based search. Instead of setting multiple words in braces, you can enter as many words as you want, in any order. For example, project: IDEADEV commenter: John Davis description: customer support returns all issues in the IDEADEV project that include comments from John Davis and contain forms of the words "customer" and "support" in the description.

You can also search for multiple words as a phrase by setting the words in quotation marks. that contain one or more words in the summary, description, or comments. For example, project: IDEADEV commenter: John Davis description: "customer support" returns all issues in the IDEADEV project that include comments from John Davis and contain forms of the words "customer" and "support" in the description as a phrase. For a complete description, see Text Search.

Query Completion

The Search box supports query completion. Query completion suggests possible attributes and values that are based on your current input. When you start typing an empty search query, YouTrack suggests attributes and values for keywords that match the current input. You can select an item from the list using your mouse or keyboard.

• If you select an attribute, the query completion suggests possible values for the selected attribute.

• If you select a single value, the value is added to the query.

Suggestions for query completion are displayed automatically as you type.

To display query completion at the current position in the search box, press Ctrl + Spacebar or Alt + Down Arrow.

Visual Indicators

When you enter a query in the search box, YouTrack applies visual indicators to the query. This formatting tells you that your query has been parsed as a structured search.

• Issue attributes are shown as normal text without formatting.

• Attribute values are shown in blue text.

• Words that are parsed as text search are shown in gold.

• Invalid parameters are underlined in red.