Basic issue search
In most cases you can find the issues that you want to work with very easily by using the issue list headers or by entering a few simple keywords into the main search field.
Whenever you visit the "issue list" in your project, you are presented with a table of all open issues, or the default query set up by the project owners. If you see too many results, you can quickly filter your results by clicking on the table headers and choosing a specific value from the "Show only:" submenu.
The main search field consists of two parts:
- A drop-down selection of search scopes, e.g, "All issues" or just "Open issues".
- A search text field where you can enter search terms.
In the text field, you may enter simple search terms, or add any of the search operators described below.
You can also use the search text field to jump directly to any issue by entering its issue number. If you wish to search for issues that contain a number, rather than jumping to that issue, enclose the number in quotation marks.
Behind the scenes, the search scope is simply an additional set of search terms that is automatically combined with the user's search terms to make a complete query. To see what search terms will be used for each scope, hover your mouse over the scope item.
Advanced issue search
The Advanced Search page helps you compose a complex query. The advanced search form breaks the search down into several popular criteria and allows you to specify each one easily. The search criteria boil down to the same thing as the search operators described below, but you don't need to remember the operator names.
Full-text search
As with Google web search, you can search for issues by simply entering a few words. However, you may get a few more results than you expected. When you need to search more precisely, you can use search operators for more power.
Full-text search terms can include quoted phrases, and words or phrases can be negated by using a leading minus sign. Please note that negated full-text terms are likely to give large result sets, so it is best to use structured search operators when possible.
Search operators
Normal search terms will match words found in any field of an issue. You can narrow the search to a specific field by using the name of the field. The built-in field operators are summary, description, comment, status, reporter, owner, cc, component, commentby, hotlist, ID, project, and label.
Field names can be compared to a list of values using:
- a colon (:) for word matching,
- an equals sign (=) for full string matching,
- a not equals sign (!=) or leading minus sign to negate, or
- inequality operators (<, >, <=, >=) for numeric comparison.
You can limit your search to just open issues by using is:open, or to just closed issues by using a minus sign to negate it: -is:open.
For example, here's how to search for issues with the word "calculation" in the summary field.
When searching for issues owned by a specific user, you can use their email address, or part of it. When referring to yourself, you can also use the special term me. For example, this restricts the search to issues that are owned by you.
Rather than have a large number of predefined fields, our issue tracker stores many issue details as labels.
For example, if you labeled security-related issues with the label Security, here's how to search for them.
In addition to simple one-word labels, you can use two part labels that specify an attribute and a value, like Priority-High, Priority-Medium, and Priority-Low. You can search for these with the label operator, or you can use the first part of the label name like an operator.
For example, if you labeled high priority issues with Priority-High, here's one way to search for them.
And, here is a more compact way to do the same search.
For the components operator, the default search will find issues in that component and all of its subcomponents.
And of course, you can combine any of these field operators.
You can search for issues in the current project that are also on a user's hotlist.
Empty (or non-empty) field search
For each built-in field operator, you can use the has operator to search for issues with empty or non-empty fields. The has operator can be used with status, owner, cc, component, attachments, blocking, blockedon, mergedinto, any key-value label prefix, or any custom field name.
For example, here's how to search for issues that have one or more components.
Or, you can use the -has operator for negation, to search for issues with empty fields.
For example, here's how to search for issues that are not associated with any component.
Multiple values in search terms
You can search for two values for one field, or two labels with the same prefix by using.
You can combine two separate queries into one using the OR operator.
You can create more complex OR queries using parentheses nesting to distribute search terms across OR clauses. A search query may contain as many sets of parentheses and levels of parentheses nesting as needed.
Exact value search
You can search for issues that exactly match the given term by using the search operator =.
For example, searching for Milestone=2009 only matches issues with the label Milestone-2009, while searching for Milestone:2009 matches issues with the labels Milestone-2009, Milestone-2009-Q1, Milestone-2009-Q3, etc.
Similarly, using exact matching on components will get you only those issues that are in that component, not including any of its descendants.
Star search
Any logged in user can mark any issue with a star. The star indicates interest in the issue.
For example, to quickly see all the issues in this project that you have starred, you could use the following:
And, to see the issues that more than ten users have starred, use the following:
Jump to issue and numeric search
You can jump directly to a specific issue by entering its ID in the search field.
For example, to jump to issue 1, just search for 1. If there is no existing issue with that ID, the system will search for issues that contain that number anywhere in the issue.
If you just want to search for issues that contain the number 1, without jumping to issue 1, enclose the number in quotation marks.
Searching for a list of specific issue IDs is one way to communicate a set of issues to someone that you are working with. Be sure to set the search scope to "All issues" if the issues might be closed.
Attachment search
Users can attach files to any issues, either when issues are created or as part of issue comments.
To quickly see all the issues that have attachments, use the following:
Or, you can search for a specific filename of the attachment.
You can also search for the file extension of the attachment.
You can also search for issues with a certain number of attachments.
Date range search
You can perform searches based on date ranges.
This search syntax is divided into two parts, the action and the date, [action]:[date]
Built-in date operators include opened, modified, and closed. Each can be paired with an inequality operator < or >. The date must to be specified as YYYY-MM-DD, YYYY/MM/DD or today-N.
For example, if you want to search for issues opened after 2009/4/1, you could do the following:
Or, if you want to search for issues modified 20 days before today's date, you could do the following:
You can search for issues that had specific fields modified recently by using ownermodified:, statusmodified:, componentmodified:. For example: