Bugzilla QuickSearch

Type in one or more words (or pieces of words) to search for:

The Basics

If you just put a word or series of words in the search box, Bugzilla will search the Product, Component, Keywords, Summary, and Comment fields for your word or words.
Typing just a number in the search box will take you directly to the bug with that ID.
Adding more terms narrows down the search, it does not expand it. (In other words, Bugzilla searches for bugs that match all your criteria, not bugs that match any of your criteria.)
Searching is case-insensitive. So table, Table, and TABLE are all the same.
Bugzilla does not just search for the exact word you put in, but also for any word that contains that word. So, for example, searching for "cat" would also find bugs that contain it as part of other words—for example, a bug mentioning "catch" or "certificate". It will not find partial words in the Comment or Keywords fields, though—only full words are matched, there.
By default, only open bugs are searched. If you want to know how to also search closed bugs, see the Advanced Shortcuts section.
If you want to search specific fields, you do it like field:value, where field is one of the field names lower down in this document, and value is the value you want to search for in that field. If put commas in the value, then it is interpreted as a list of values, and bugs that match any of those values will be searched for.

You may also want to read up on the Advanced Features.

Fields You Can Search On

You can specify any of these fields like field:value in the search box, to search on them. You can also abbreviate the field name, as long as your abbreviation matches only one field name. So, for example, searching on stat:NEW will find all bugs in the NEW status. Some fields have multiple names, and you can use any of those names to search for them.

For custom fields, they can be used and abbreviated based on the part of their name after the cf_ if you'd like, in addition to their standard name starting with cf_. So for example, can be referred to as , also. However, if this causes a conflict between the standard Bugzilla field names and the custom field names, the standard field names always take precedence.

Field	Field Name(s) For Search
%Complete	`percentage_complete`
Alias	`alias`
Assignee	`assigned_to`, `assignee`
Attachment data	`attachmentdata`, `attachdata`
Attachment description	`attachmentdesc`, `attachment`, `attachdesc`
Attachment mime type	`attachmentmimetype`, `attachmimetype`
Backplane ID	`backplane_id`
Blocks	`blocked`
Bug ID	`bug_id`
CC	`cc`
Changed	`delta_ts`
Classification	`classification`
Comment	`description`, `longdesc`, `comment`
Commenter	`commenter`
Component	`component`
Content	`content`
Creation date	`creation_ts`
Days since bug changed	`days_elapsed`
Deadline	`deadline`
Depends on	`dependson`
Ever confirmed	`everconfirmed`
Firmware version	`cf_firmwareversion`
Firmware Version	`firmware`
Flag Requestee	`requestee`
Flag Setter	`setter`
Flags	`flag`
Group	`group`
Hardware	`platform`
Hours Left	`remaining_time`
Hours Worked	`work_time`
Keywords	`keywords`, `kw`
Orig. Est.	`estimated_time`
OS	`op_sys`, `os`
Priority	`priority`
Product	`product`
QA Contact	`qa_contact`
Reporter	`reporter`
Resolution	`resolution`
See Also	`see_also`
Severity	`severity`
Status	`status`
Summary	`short_desc`, `summary`
Target Milestone	`target_milestone`, `milestone`
Time Since Assignee Touched	`owner_idle_time`
URL	`url`
Version	`version`
Votes	`votes`
Whiteboard	`whiteboard`, `sw`

Advanced Features

If you want to search for a phrase or something that contains spaces, you can put it in quotes, like: "this is a phrase". You can also use quotes to search for characters that would otherwise be interpreted specially by quicksearch. For example, "this|thing" would search for the literal phrase this|thing.
You can use AND, NOT, and OR in searches. You can also use - to mean "NOT", and | to mean "OR". There is no special character for "AND", because by default any search terms that are separated by a space are joined by an "AND". Examples:
- NOT:
  Use -summary:foo to exclude bugs with foo in the summary.
  NOT summary:foo would have the same effect.
- AND:
  foo bar searches for bugs that contains both foo and bar.
  foo AND bar would have the same effect.
- OR:
  foo|bar would search for bugs that contain foo OR bar.
  foo OR bar would have the same effect.
OR has higher precedence than AND; AND is the top level operation. For example:

Searching for url|location bar|field -focus means (url OR location) AND (bar OR field) AND (NOT focus)

Advanced Shortcuts

In addition to using field names to search specific fields, there are certain characters or words that you can use as a "shortcut" for searching certain fields:

Field	Shortcut(s)
Status	Make the first word of your search the name of any status, or even an abbreviation of any status, and bugs in that status will be searched. `ALL` is a special shortcut that means "all statuses". `OPEN` is a special shortcut that means "all open statuses".
Resolution	Make the first word of your search the name of any resolution, or even an abbreviation of any resolution, and bugs with that resolution will be searched. For example, making `FIX` the first word of your search will find all bugs with a resolution of `FIXED` .
Priority	"P1" (as a word anywhere in the search) means "find bugs with the highest priority. "P2" means the second-highest priority, and so on. Searching for "P1-P3" will find bugs in any of the three highest priorities, and so on.
Assignee	@value
Product or Component	:value
Keywords	!value
Flags	flag?requestee
Comment or Summary	#value