Search Query Reference

attachment text

Returns issues that include image attachments with the specified text.

attachments

Returns issues that include attachments with the specified filename.

Board

Returns issues that are assigned to the specified sprint on the specified agile board. To find issues that are assigned to agile boards with sprints disabled, use has: <board name>.

cc recipients

Returns tickets where the specified users are added as CCs.

code

Returns issues that contain word forms that match the specified word or words that are formatted as code in the issue description or comments. This includes matches that are formatted as inline code spans, indented and fenced code blocks, and stack traces.

commented

Returns issues to which comments were added on the specified date or within the specified period.

commenter

Returns issues that were commented by the specified user or by a member of the specified group.

comments

Returns issues that contain word forms that match the specified word or words in a comment.

created

Returns issues that were created on a specific date or within a specified time frame.

description

Returns issues that contain word forms that match the specified word or words in the issue description.

document type

Returns either issue or ticket type documents.

Gantt

Returns issues that are assigned to the specified Gantt chart.

has

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:

issue ID

Returns an issue that matches the specified issue ID. This attribute can also be referenced as a single value with the syntax #<issue ID> or -<issue ID>. When the search returns a single issue, the result is displayed in single issue view.

• If you don't use the syntax for an attribute-based search (issue ID: <value> or #<value>), the input is also parsed as a text search. In addition to any issue that matches the specified issue ID, the search results include any issue that contains the specified ID in any text attribute.

• If you set the issue ID in quotes, the input is only parsed as a text search. The search results only include issues that contain the specified ID in a text attribute.

Note that even when an issue ID is parsed as a text search, the results do not include issue links. To find issues based on issue links, use the links attribute or reference a specific link type.

links

Returns all issues that contain links to the specified issue.

looks like

Returns issues in which the issue summary or description contains words that are found in the issue summary or description in the specified issue. Issues that contain matching words in the issue summary are given higher weight when the search results are sorted by relevance.

mentions

Returns issues that contain @mention references for the specified user in the description or a comment. User mentions in supplemental text fields are not included in the search results.

organization

Returns issues that belong to the specified organization. This attribute can also be referenced as a single value.

project

Returns issues that belong to the specified project. This attribute can also be referenced as a single value.

reporter

Returns issues and tickets that were created by the specified user or a member of the specified group, including tickets created on behalf of the specified user. Use me to return issues that were created by the current user.

resolved date

Returns issues that were resolved on a specific date or within a specified time frame.

saved search

Returns issues that match the search criteria of a saved search. This attribute can also be referenced as a single value with the syntax #<saved search name> or -<saved search name>.

submitter

Returns issues that were submitted by the specified user or a member of the specified group on behalf of another user. Use me to return issues that were submitted by the current user.

summary

Returns issues that contain word forms that match the specified word or words in the issue summary.

tag

Returns issues that match a specified tag. This attribute can also be referenced as a single value with the syntax #<tag name> or -<tag name>

updated

Returns issues where the most recent change occurred on a specific date or within a specified time frame.

updater

Returns issues that were last updated by the specified user or a member of the specified group. Use me to return issues to which you applied the last update.

vcs changes

Returns issues that contain vcs changes that were applied in the commit object that is identified by the specified SHA-1 commit hash.

visible to

Returns issues that are visible to the specified user or a member of the specified group.

voter

Returns issues that have votes from the specified user or a member of the specified group.

Affected versions

Returns issues that were detected in a specific version of the product.

Assignee

Returns all issues that are assigned to the specified user or a member of the specified group.

Fix versions

Returns issues that were fixed in a specific version of the product.

Fixed in build

Returns issues that were fixed in the specified build.

Priority

Returns issues that match the specified priority level.

State

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.

Subsystem

Returns issues that are assigned to a specific subsystem within a project.

Type

Returns issues that match the specified issue type.

links

Returns issues that are linked to a target issue.

aggregate

Returns issues that are indirectly linked to a target issue. Use this search term to find, for example, issues that are parent issues for a parent issue or subtasks of issues that are also subtasks of a target issue. The results include any issue that is linked to the target issue using the specified link type, whether directly or indirectly.

This search argument is only compatible with aggregation link types.

Depends on

Returns issues that have depends on links to a target issue or any issue that matches the specified sub-query.

Duplicates

Returns issues that have duplicates links to a target issue or any issue that matches the specified sub-query.

Is duplicated by

Returns issues that have is duplicated by links to a target issue or any issue that matches the specified sub-query.

Is required for

Returns issues that have is required for links to a target issue or any issue that matches the specified sub-query.

Parent for

Returns issues that have parent for links to a target issue or any issue that matches the specified sub-query.

Relates to

Returns issues that have relates to links to a target issue or any issue that matches the specified sub-query.

Subtask of

Returns issues that have subtask of links to a target issue or any issue that matches the specified sub-query.

work

Returns issues that contain word forms that match the specified word or phrase in a work item.

work author

Returns issues that have work items that were added by the specified user.

work type

Returns issues that have work items that are assigned the specified work type. The query work type: {No type} returns issues that have work items that are not assigned a work item type.

work date

Returns issues that have work items that are recorded for the specified date or within the specified time frame.

custom work item attributes

Returns issues that have work items that are assigned the specified value for a specific work item attribute.

sort by

Sorts issues that are returned by the query in the specified order.

When you perform a text search, the results can be sorted by relevance. You cannot specify relevance as a sort attribute. For more information, see Sorting by Relevance.

me

References the current user. This keyword can be used as a value for any attribute that accepts a user.

When used as a single value (#me) the search returns issues that are assigned to, reported by, or commented by the current user.

For example, to find unresolved issues that are assigned to, reported by, or contain comments from the current user, enter #me -Resolved.

The results also include issues that contain references to the current user in any custom field that stores values as users. For example, you have a custom field Reviewed by that stores a user type. The search query #me -Resolved also includes issues that reference the current user in this custom field.

my

An alias for me.

Resolved

This keyword references the Resolved issue property. This property is set based on the current value or combination of values for any custom field that stores a state type. In the default State field, the Resolved property is enabled for the values Fixed, Won't fix, Duplicate, Incomplete, Obsolete, and Can't reproduce.

For projects that use multiple state-type fields, the Resolved property is only true when all the state-type fields are assigned values that are considered to be resolved.

For example, to find all resolved issues that were updated today, enter #Resolved updated: Today.

Unresolved

This keyword references the Unresolved issue property. This property is set based on the current value or combination of values for any custom field that stores a state type. In the default State field, the Resolved property is disabled for the values Submitted, Open, In Progress, Reopened, and To be discussed.

For projects that use multiple state-type fields, the Unresolved property is true when any state-type field is assigned a value that is not considered to be resolved.

For example, to find all unresolved issues that are assigned to the user john.doe in the Test project, enter #Unresolved project: Test for: john.doe.

Released

This keyword references the Released property for values in a field that stores a version type. It can only be used together with the attribute name or alias for a version field. This means that it cannot be referenced as a single value.

With fields that store multiple values, the search query returns issues for which at least one of the versions that are stored in the field is marked as released.

For example, to find all issues in the Test project that are fixed in a version that has not yet been released, enter in: Test fixed in: -Released.

Archived

This keyword references the Archived property for values in a field that stores a version type. It can only be used together with the attribute name or alias for a version field. This means that it cannot be referenced as a single value.

With fields that store multiple values, the search query only returns issues for which all the versions that are stored in the field are marked as archived.

For example, to find all issues in the Test project that are fixed in a version that has been archived, enter in: Test fixed in: Archived.

and

The AND operator combines matches for multiple search attributes to narrow down the search results. When you join search arguments with the AND operator, the resulting issues must contain matches for all the specified attributes. Use this operator for issue fields that store enum[*] types and tags.

Search arguments that are joined with an AND operator are always processed as a group and have a higher priority than other arguments that are joined with an OR operator in the query.

Here are a few examples of search queries that contain AND operators:

• To find issues in the Ktor project that are tagged as both Next build and to be tested, enter:

  in: Ktor and tag: {Next build} and tag: {to be tested}

  The AND operator between the two tags ensures that the results only contain issues that have both tags.

• To find all issues that are set as Critical priority in the Ktor project or are set as Major priority and are assigned to you in the Kotlin project, enter:

  in: Ktor #Critical or in: Kotlin #Major and for: me

  If you were to remove the operators in this query, the references to the project and priority are parsed as disjunctive (OR) statements. The reference to the assignee (me) is then joined with a conjunctive (AND) statement. Instead of getting critical issues in the Ktor project plus a list of major-priority issues that you are assigned in Kotlin, you would only issues that are assigned to you that are either major or critical in either Ktor or Kotlin.

or

The OR operator combines matches for multiple search attribute to broaden the search results.

This is very useful when searching for a term which has a synonym that might be used in an issue instead. For example, a search for lesson OR tutorial returns issues that contain matching forms for either "lesson" or "tutorial". If you remove the OR operator from the query, the search is performed conjunctively, which means the result would only include issues that contain matching forms for both words.

Here's another example of a search query that contains an OR operator:

• To find all issues in the Ktor project that are assigned to you or are tagged as to be tested in any project, enter:

  in: Ktor for: me or tag: {to be tested}

Parentheses

Using parentheses ( and ) combines various search arguments to change the order in which the attributes and operators are processed. The part of a search query inside the parentheses has priority and is always processed as a single unit.

The most common use of parentheses is to enclose two search arguments that are separated by an OR operator and further restrict the search results by joining additional search arguments with AND operators.

Any time you use parentheses in a search query, you need to provide all the operators that join the parenthetical statement to neighboring search arguments. For example, the search query in: Kotlin #Critical (in: Ktor and for:me) cannot be processed. It must be written as in: Kotlin #Critical or (in: Ktor and for:me) instead.

Here's an example of a search query that uses parentheses:

• To find all issues that are assigned to you and are either assigned Critical priority in the Kotlin project or are assigned Major priority in the Ktor project, enter:

  (in: Kotlin #Critical or in: Ktor #Major) and for: me

Predefined Relative Date Parameters

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.

The following relative date parameters are supported:

Custom Date Parameters

If the predefined date parameters don't help you find issues that matter most to you, define your own date range in your search query. Here are a few examples of the queries you can write with custom date parameters:

• Find issues that have new comments added in the last seven days:

  commented: {minus 7d} .. Today

• Find issues that were updated in the last two hours:

  updated: {minus 2h} .. *

• Find unresolved issues that are at least one and a half years old:

  created: * .. {minus 1y 6M} #Unresolved

• Find issues that are due in five days:

  Due Date: {plus 5d}

To define a custom time frame in your search queries, use the following syntax:

• To specify dates or times in the past, use minus.

• To specify dates or times in the future, use plus.

• Specify the time frame as a series of whole numbers followed by a letter that represents the unit of time. Separate each unit of time with a space character. For example:

  2y 3M 1w 2d 12h

Queries that specify hours will filter for events that took place during the specified hour. For example, if it is currently 15:35, a query that is written as created: {minus 48h} returns issues that were created two days ago, at any time between 3 and 4 PM. Meanwhile, a query that is written as created: {minus 2d} returns all issues that were created two days ago at any time between midnight and 23:59.

This level of precision only applies to hours. A query that references the unit of time as 14d returns exactly the same results as 2w.

Search queries that specify units of time shorter than one hour (minutes, seconds) are not supported.