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 tickets 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_site can be referred to as site, 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
Alineos Sites cf_alineos_sites
Assignee assigned_toassigneeowner
Assignee Real Name assigned_to_realname
Atos/Eviden Sites cf_bull_sites
Attachment data attachmentdataattachdata
Attachment description attachmentdescattachmentattachdesc
Attachment mime type attachmentmimetypeattachmimetype
Blocks blocked
CC cc
Changed delta_ts
Classification classification
CLE Version cf_cle_version
Comment descriptionlongdesccomment
Comment Tag comment_tag
Commenter commenter
Component component
Confidential Site cf_confidential_site
Content content
Coreweave sites cf_coreweave_sites
Cray Sites cf_cray_site
Creation date creation_ts
Days since ticket changed days_elapsed
Deadline deadline
Depends on dependson
DevPrio cf_devprio
DS9 clusters cf_ds9_clusters
Emory-Cloud Sites cf_emory_cloud_sites
Ever confirmed everconfirmed
Flag Requestee requestee
Flag Setter setter
Flags flag
Group group
Hardware platform
Hours Left remaining_time
Hours Worked work_time
HPCnow Sites cf_hpcnow_site
HPE Sites cf_hpe_site
IBM Sites cf_ibmfr_sites
Keywords keywordskw
Last Visit last_visit_ts
Linux Distro cf_linux_version
Machine Name cf_mach_name
NOAA SIte cf_noaa_site
OCF Sites cf_ocf_sites
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
Recursion Pharma Sites cf_recursion_pharma_sites
Reporter reporter
Reporter Real Name reporter_realname
Resolution resolution
See Also see_also
Severity severity
SFW Sites cf_sfw_sites
Site cf_site
SNIC sites cf_snic_site
Status status
Summary short_descsummary
Target Milestone target_milestonemilestone
Target Release cf_target
Ticket ID bug_id
Time Since Assignee Touched owner_idle_time
URL url
Version version
Version Fixed cf_verision_fixed
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 tickets 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 tickets with that resolution will be searched. For example, making FIX the first word of your search will find all tickets with a resolution of FIXED .
Priority "P1" (as a word anywhere in the search) means "find tickets with the highest priority. "P2" means the second-highest priority, and so on.

Searching for "P1-3" will find tickets 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.