Univention Bugzilla – Univention Bugzilla QuickSearch
Here are some examples of how to write some simple queries. Examples for more complex queries can be found lower in this page.
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_report can be referred to as report, also. However, if this causes a conflict between the standard Univention Bugzilla field names and the custom field names, the standard field names always take precedence.
|Field||Field Name(s) For Search|
|Assignee||assigned_to, assignee, owner|
|Assignee Real Name||assigned_to_realname|
|Attachment data||attachmentdata, attachdata|
|Attachment description||attachmentdesc, attachment, attachdesc|
|Attachment mime type||attachmentmimetype, attachmimetype|
|Bug group (optional)||cf_bug_group|
|Comment||description, longdesc, comment|
|Days since bug changed||days_elapsed|
|Enterprise Customer affected?||cf_enterprise_customer_affected|
|Flags outvoted (downgraded) after PO Review||cf_outvoted_by_po|
|How will those affected feel about the bug?||cf_priority|
|Max CVSS v3 score||cf_cvss_v3|
|QA Contact Real Name||qa_contact_realname|
|Reporter Real Name||reporter_realname|
|School Customer affected?||cf_school_customers_affected|
|Target Milestone||target_milestone, milestone|
|Time Since Assignee Touched||owner_idle_time|
|What kind of report is it?||cf_report|
|What type of bug is this?||cf_type|
|Who will be affected by this bug?||cf_likelihood|
You cannot use | nor OR to enumerate possible values for a given field. You must use commas instead. So field:value1,value2 does what you expect, but field:value1|value2 would be treated as field:value1 OR value2, which means value2 is not bound to the given field.
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)
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:
|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.
|Product or Component||:value|
|Comment or Summary||#value|
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.