Wenn Sie einfach ein Wort oder mehrere Wörter in das Suchfeld eingeben,
durchsucht Bugzilla die Felder
Produkt,
Komponente,
Alias,
Kurzbeschreibung,
und Kommentar danach.
Wenn Sie lediglich eine Zahl in das Suchfeld eingeben,
bekommen Sie direkt den Bug mit dieser ID angezeigt.
Analog funktioniert das auch für jeden
Bugalias.
Wenn Sie mehr Begriffe hinzufügen, schränken Sie damit die Suche
weiter ein.
(Mit anderen Worten, Bugzilla sucht Bugs, die all
Ihren Kriterien entsprechen, und nicht Bugs, die
irgendeinem Ihrer Kriterien entsprechen.)
Die Suche ignoriert Groß- und Kleinschreibung.
Es spielt also keine Rolle, ob Sie nach tisch,
Tisch oder TISCH suchen.
Bugzilla sucht nicht nur nach Ihren Worten, sondern auch nach
Worten, die Ihr Wort enthalten.
Eine Suche nach „Feld“ findet beispielsweise dementsprechend auch
Bugs, in denen das Wort „Umfeld“ auftaucht.
Die Felder Kommentar und
Schlüsselwörter werden allerdings nicht nach
Wortteilen durchsucht – nur ganze Worte führen hier zu Treffern.
Ohne weitere Angaben werden nur offene Bugs
durchsucht.
Wenn Sie wissen möchten, wie Sie auch nicht-offene Bugs finden
können, schauen Sie bei den Kürzeln für
Fortgeschrittene nach.
Wenn Sie bestimmte Felder durchsuchen möchten, verwenden
Sie die Schreibweise Feld:Inhalt, wobei Feld einer
der Feldnamen der Feldnamenliste weiter unten ist,
und Inhalt der Inhalt, nach dem Sie im Feld suchen möchten.
Wenn Inhalt Kommas enthält, dann wird Ihre Angabe als Werteliste
interpretiert, und es werden Bugs gefunden, die für
irgendeinen der Werte einen Treffer aufweisen.
Der Rest dieses Dokuments ist noch nicht übersetzt.
All open Bugs where userA@company.com is in the CC list
(no need to mention open Bugs, this is the default): cc:userA@company.com
All unconfirmed Bugs in product productA (putting the
Bug status at the first position make it being automagically
considered as ein Bug status): UNCONFIRMED product:productA
All open and closed Bugs reported by userB@company.com
(we must specify ALL as the first word, else only open Bugs
are taken into account): ALL reporter:userB@company.com
All open Bugs with severity blocker or critical with the
target milestone set to 2.5: severity:blocker,critical milestone:2.5
All open Bugs in the component Research & Development
with priority P1 or P2 (we must use quotes for the component as its name
contains whitespaces): component:"Research & Development" priority:P1,P2
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_meldender can be
referred to as
meldender,
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
% erledigt
percentage_complete
Alias
alias
Anfragesteller
requestee
Anlagezeitpunkt
creation_ts
Ansprechpartner
cf_meldender
Aufwand (h)
work_time
Berichterstatter
reporter
Beschreibung des Anhangs
attachmentdesc,
attachment,
attachdesc
Betriebssystem
op_sys,
os
Blockiert
blocked
Bug-ID
bug_id
CC
cc
Comment Tag
comment_tag
Daten des Anhangs
attachmentdata,
attachdata
Ersteller eines Kommentars
commenter
Fälligkeit
deadline
Gruppe
group
Hardware
platform
Hängt ab von
dependson
Inhalt
content
Jemals bestätigt
everconfirmed
Klassifikation
classification
Kommentar
description,
longdesc,
comment
Komponente
component
Kurzbeschreibung
short_desc,
summary
Letzter Besuch
last_visit_ts
Lösung
resolution
Markierung gesetzt von
setter
Markierungen
flag
MIME-Inhaltstyp des Anhangs
attachmentmimetype,
attachmimetype
Name des Berichterstatters
reporter_realname
Name des QS-Kontakts
qa_contact_realname
Name des Zuständigen
assigned_to_realname
Persönliche Schlagwörter
tag
Priorität
priority
Produkt
product
QS-Kontakt
qa_contact
Restaufw. (h)
remaining_time
Schlüsselwörter
keywords,
kw
Schwere
severity
Siehe auch
see_also
Status
status
Statusnotiz
whiteboard,
sw
Tage seit der letzten Bugänderung
days_elapsed
Telefonnummmer Ansprechpartner
cf_telefon
URI
url
Urspr. Schätzg. (h)
estimated_time
Version
version
Zeit seit der letzten Änderung durch den Zuständigen
owner_idle_time
Ziel-Meilenstein
target_milestone,
milestone
Zuletzt geändert
delta_ts
Zuständiger
assigned_to,
assignee,
owner
Advanced Features
If you want to search for a phrase or something that
contains spaces, commas, colons or quotes, you must put it in quotes, like:
"yes, this is a phrase". You must also use quotes to search for
characters that would otherwise be interpreted specially by quicksearch.
For example, "this|that" would search for the literal string
this|that and would not be parsed as "this OR that".
Also, "-field:value" would search for the literal phrase
-field:value and would not be parsed as
"NOT field:value".
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.
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)
The default operator, colon (:), performs a substring
match of the value. The following operators are supported:
: (substring): summary:foo will search for Bugs
where the summary contains foo.
= (equals): summary=foo will search for Bugs
where the summary is exactly foo.
!= (notequals): summary!=foo will search for Bugs
where the summary is not foo.
> (greaterthan): creation_ts>-2w will search for Bugs
where that were created between two weeks ago and now, excluding Bugs exactly two weeks old.
>= (greaterthaneq): creation_ts>=-2w will search for Bugs
where that were created between two weeks ago and now, including Bugs exactly two weeks old.
< (lessthan): creation_ts<-2w will search for Bugs
where that were created more than two weeks ago, excluding Bugs exactly two weeks old.
<= (lessthaneq): creation_ts<=-2w will search for Bugs
where that were created more than two weeks ago, including Bugs exactly two weeks old.
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".
Lösung
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 .
Priorität
"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.
Zuständiger
@value
Produkt or
Komponente
:value
Markierungen
flag?requestee
Kommentar
or Kurzbeschreibung
#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.
All Bugs reported by userA@company.com or assigned to them
(the initial @ is a shortcut for the assignee, see the
Advanced Shortcuts section above): ALL @userA@company.com OR reporter:userA@company.com
All open Bugs in product productA with either severity
blocker, critical or major, or with priority P1, or with the blocker+
flag set, and which are neither assigned to userB@company.com nor to
userC@company.com (we make the assumption that there are only two users
matching userB and userC, else we would write the whole login name): :productA sev:blocker,critical,major OR pri:P1 OR flag:blocker+ -assign:userB,userC
All FIXED Bugs with the blocker+ flag set, but without
the approval+ nor approval? flags set: FIXED flag:blocker+ -flag:approval+ -flag:approval?
Bugs with That's a "unusual" issue in the
Bug summary (double quotes are escaped using \"): summary:"That's a \"unusual\" issue"
Bugzilla – Bugzilla-Schnellsuche