<p><b>Notice:</b> This was written for the new query page that will probably be added in a version later than Bugzilla 2.12 in order to fix some regressions. Therefore, the layout of the forms shown in captions might not be exactly as they appear on the query page. The number of fields, though, is the same and you should be able to locate the fields on the current query.cgi without much problem.
<p><br><center><h3>The Sections</h3></center>
<p>The query page is broken down into the following sections:
<p>"I already know how to use <a href="http://www.mozilla.org/bugs/">Bugzilla</a>, but would like <a href="#info">information</a> about Bugzilla and the author of this document."
<br>"Ok, I am almost certain the bug I discovered isn't in Bugzilla, how do I <a href="enter_bug.cgi">submit</a> the bug?" - <a href= "http://www.mozilla.org/quality/bug-writing-guidelines.html">Read the guidelines first</a>!
<p><br><center><h3>Tips</h3></center>
You don't have to fill out any field on the query page you don't need. Filling out fields will limit
your search. On the list boxes, such as Status, you can Ctrl-Click to unselect an option.
Until you get better, you can use the "brute force" method where you enter a very simple query and search through
the long list of bugs manually. Just try not to overuse this method if you don't have to as you might be slowing down
the search for other people if there are many people searching at the same time. Finally, I would recommend learning the Boolean Chart immediately because it is extremely
powerful. Also, there is a navigation bar at the <a href="#bottom">bottom</a> of
most Bugzilla pages, and important links at the <a href="index.html">front page</a>.
<p>Back to the <a href="query.cgi">Query</a>. If you typed anything in the forms already, you might want to hit back on the
browser. When you are all done reading, do a <a href="#samplequery">sample query</a>!
<SELECT NAME="keywords_type"><OPTION VALUE="anywords">Any of the listed keywords set
<OPTION VALUE="allwords">All of the listed keywords set
<OPTION VALUE="nowords">None of the listed keywords set
</SELECT></TD></TR>
</table>
</td></tr>
</table>
</center>
<br>
<p>In this section, you can enter values that are searched for in all the bugs (or whatever you
limit the bugs to in other fields).
You might want to look at <a href="http://www.mozilla.org/bugs/text-searching.html">Bugzilla Text Searching</a>
to see info on <a href="http://www.mozilla.org/bugs/text-searching.html">Regular Expressions</a> and text searching. The box next to these fields decides
how a match will be determined.<br>
<a name="summaries"></a>
<h4>Bug summary</h4>
<p>This lets you search the summaries. The summary is one line that attempts to sum up the bug.
<a name="descriptions"></a>
<h4>A description entry</h4>
<p>This lets you search comments. Comments can be added by anybody. Comments are the largest
searchable area in most bugs. If you really want to find a lot of matches, search the comments.
<a name="url"></a>
<h4>Associated URL</h4>
<p>This lets you search the url field. This contains the url of the web page the bug is
about.
<a name="statuswhiteboard"></a>
<h4>Status Whiteboard</h4>
<p>This lets you search the bug's status whiteboard. The status whiteboard contains general
information that engineers add.
};
printqq{
<a name="keywords"></a>
<h4>Keywords</h4>
<br><br>Each bug can have keywords specified. The bug reporter or a
user with the proper permissions can edit these keywords. The following is a list of the keywords that are
<INPUT TYPE="radio" NAME="cmdtype" VALUE="editnamed"> Load the remembered query:
<select name="namedcmd"><OPTION VALUE="Assigned to me">Assigned to me</select><br>
<INPUT TYPE="radio" NAME="cmdtype" VALUE="runnamed"> Run the remembered query:<br>
<INPUT TYPE="radio" NAME="cmdtype" VALUE="forgetnamed"> Forget the remembered query:<br>
<INPUT TYPE="radio" NAME="cmdtype" VALUE="asdefault"> Remember this as the default query<br>
<INPUT TYPE="radio" NAME="cmdtype" VALUE="asnamed"> Remember this query, and name it:
<INPUT TYPE="text" NAME="newqueryname"><br>
<B>Sort By:</B>
<SELECT NAME="order">
<OPTION VALUE="Reuse same sort as last time">Reuse same sort as last time<OPTION VALUE="Bug Number">Bug Number<OPTION VALUE="'Importance'">'Importance'<OPTION VALUE="Assignee">Assignee</SELECT>
</td>
</tr>
</table>
<table>
<tr>
<td>
<INPUT TYPE="button" VALUE="Reset back to the default query">
</td>
<td>
<INPUT TYPE="button" VALUE="Submit query">
</td>
</tr>
</table>
</td>
</tr>
</table>
</center>
<br>
<p>So you have gotten all that down, but "What is this junk at the bottom of the form?"
You can remember the current query as the default query page that is pulled up whenever you are
logged on. There is also an ability to choose how you want your results sorted. When finished,
click "Submit".
};
printqq{
<a name="info"></a>
<br><center><h3>About This Document</h3></center>
<p>Written and adapted from some older Bugzilla documents (by Terry Weissman, Tara Hernandez and others) by <a href="mailto:netdemonz\@yahoo.com">Brian Bober</a>
You can talk to me on irc.mozilla.org - #mozilla, #mozwebtools, #mozillazine, I go by the name netdemon.
<P>For more information than you can find in this document:
The people reading your bugs are busy and usually swamped with bugs. Therefore, you are doing everyone
a huge favor to search for a duplicate.
<p><br><center><h3>About Bugzilla</h3></center>
Bugzilla has been around for quite a while. It is a way for bug testers and users of Mozilla to interact with
engineers. It has been a very important part of the <a href="http://www.mozilla.org/">Mozilla Project</a> and will be for a long time to come. Bugzilla is
meaning that other people can use it and modify it if they follow Mozilla's
license. A good example of is <a href="http://bugzilla.redhat.com/bugzilla/">
Redhat Linux</a>, although they have altered the utility more than most. This will first appear on Bugzilla version 2.12, which is being finalized as
I write this. Ian Hickson is working on Bugzilla version 3.0 - a total rewrite with a much better structure and more functionality.
<p><br><center><h3>The Database</h3></center>
<p>The blood and guts of Bugzilla are the over 50,000 bugs (and growing in number quickly)
that exist in the Bugzilla Database. That is why the form is so complicated. If there were only 500 bugs, then a simple text search would probably be enough. This
form will help you sift through all these bugs to find the one you are looking for.
};
printqq{
<a name="samplequery"></a>
<p><br><center><h3>Sample Query</h3></center>
<p>Ok. <b>So lets find a bug!</b> First, lets make a <a target="_blank" href="query.cgi">
copy</a> of the query window so you can easily switch between
this document and the query.
<p>Do the following:
<ul>
<li>Go to the status field in Bug Settings and select all.
<li>In Text Search options, put Autoscroll in the summary and Panning in the description entry box
(meaning that panning is somewhere in the comments and the bug's summary has Autoscroll in it).
</ul>
<p>One of the results should have been <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=22775">bug 22775 - [RFE] AutoScroll/Panning support...</a>
};
printqq{
<hr>
If you like this document, then please buy my book: <b>Bugzilla: Mozilla's Flu Shot</b>
<br>It's 1521 pages of Bugzilla excitement! You will not regret it. At your local bookstore now!
