The type of summary search you would like

The bug summary is a short sentence which succinctly describes
what the bug is about.

Bugs are categorised into Classifications, Products and Components. classifications is the
top-level categorisation.

Bugs are categorised into Products and Components. Product is the
top-level categorisation.

Components are second-level categories; each belongs to a
particular Product. Select a Product to narrow down this list.

The version field defines the version of the software the bug
was found in.

The target_milestone field is used to define when the engineer
the bug is assigned to expects to fix it.

Bugs have comments added to them by Bugzilla users. You can
search for some text in those comments.

The type of comment search you would like

Bugs can have a URL associated with them - for example, a pointer
to a web site where the problem is seen.

The type of URL search you would like

Each bug has a free-form single line text entry box for adding
tags and status information.

The type of whiteboard search you would like

You can add keywords from a defined list to bugs, in order to
tag and group them.

The type of keyword search you would like

A bug may be in any of a number of states.

If a bug is in a resolved state, then one of these reasons will
be given for its resolution.

How severe the bug is, or whether it's an enhancement.

Engineers prioritise their bugs using this field.

The hardware platform the bug was observed on.

The operating system the bug was observed on.

Every bug has people associated with it in different roles.
Here, you can search on what people are in what role.

Every bug has people associated with it in different roles.
Here, you can search on what people are in what role.

You can limit your search to a specific set of bugs .

Some bugs can be voted for, and you can limit your search to bugs
with more than a certain number of votes.

You can search for specific types of change - this field define
which field you are interested in changes for.

Specify the start and end dates either in YYYY-MM-DD format
(optionally followed by HH:mm, in 24 hour clock), or in relative
dates such as 1d, 2w, 3m, 4y, which respectively mean one day,
two weeks, three months, or four years ago. 0d is last midnight,
and 0w, 0m, 0y is the beginning of this week, month, or year.

Specify the start and end dates either in YYYY-MM-DD format
(optionally followed by HH:mm, in 24 hour clock), or in relative
dates such as 1d, 2w, 3m, 4y, which respectively mean one day,
two weeks, three months, or four years ago. 0d is last midnight,
and 0w, 0m, 0y is the beginning of this week, month, or year.

The value the field defined above changed to during that time.