The Basics

Examples of Simple Queries

Here are some examples of how to write some simple queries. Examples for more complex queries can be found lower in this page.

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:VERIFIED will find all bugs in the VERIFIED 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, cf_test_ble_versoin can be referred to as test_ble_versoin, 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
Agency cf_rma_agency
Alias alias
APK Version cf_a22_apk_version
Assignee assigned_toassigneeowner
Assignee Real Name assigned_to_realname
Attachment data attachmentdataattachdata
Attachment description attachmentdescattachdescattachment
Attachment mime type attachmentmimetypeattachmimetype
BLE Versoin cf_a22_ble_versoin
Blocks blocked
Bug ID bug_id
CC cc
Changed delta_ts
Classification classification
Client cf_rma_company
CO. cf_lorawan_company
Comment descriptionlongdesccomment
Comment Tag comment_tag
Commenter commenter
Company cf_7688_company
Component component
Content content
Creation date creation_ts
Date Code cf_rma_module_datecode_text
Days since bug changed days_elapsed
Deadline deadline
Defect Quantity cf_rma_bad_amount
Depends on dependson
Ever confirmed everconfirmed
Flag Requestee requestee
Flag Setter setter
Flags flag
GPS Version cf_a22_gps_versoin
GPS Versoin cf_test_gps_version
Group group
Hardware platform
HDK/Module cf_76x7_hw_platform
Hours Left remaining_time
Hours Worked work_time
HW cf_a22_hw_name
HW Ver. cf_a22_hw_version
HWplatform cf_7688_hw_platform
Keywords keywordskw
Last Visit last_visit_ts
Orig. Est. estimated_time
OS op_sysos
Personal Tags tag
Priority priority
Product product
QA Contact qa_contact
QA Contact Real Name qa_contact_realname
Reporter reporter
Reporter Real Name reporter_realname
Resolution resolution
Return Quantity cf_rma_return_amount
See Also see_also
Severity severity
Shipped Quantity cf_rma_total_amount
Status status
Summary short_descsummary
SW Version version
Target Milestone target_milestonemilestone
The RMA Result cf_rma_result
Time Since Assignee Touched owner_idle_time
URL url
Whiteboard whiteboardsw

Advanced Features

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-3" will find bugs in any of the three highest priorities, and so on.

Assignee @value
Product or Component :value
Flags flag?requestee
Comment or Summary #value

Examples of Complex Queries

It is pretty easy to write rather complex queries without too much effort. For very complex queries, you have to use the Advanced Search form.