<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."
<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>!
<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= "docs/html/Bugzilla-Guide.html#BUG_WRITING">Read the guidelines first</a>!
<p><br><center><h3>Tips</h3></center>
<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
You don't have to fill out any field on the query page you don't need. Filling out fields will limit
...
@@ -221,9 +223,6 @@ more information appears later, please re-assign the bug, for
...
@@ -221,9 +223,6 @@ more information appears later, please re-assign the bug, for
now, file it.
now, file it.
</ul>
</ul>
Note: The LATER and REMIND resolutions are no longer used on bugzilla.mozilla.org and many
installations are phasing them out.
<a name="platform"></a>
<a name="platform"></a>
<p><b>Platform</b>
<p><b>Platform</b>
<p>The <b>platform</b> field is the hardware platform against which the bug was reported. Legal
<p>The <b>platform</b> field is the hardware platform against which the bug was reported. Legal
...
@@ -469,6 +468,8 @@ how a match will be determined.<br>
...
@@ -469,6 +468,8 @@ how a match will be determined.<br>
<h4>A description entry</h4>
<h4>A description entry</h4>
<p>This lets you search comments. Comments can be added by anybody. Comments are the largest
<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.
searchable area in most bugs. If you really want to find a lot of matches, search the comments.
<BR><B>Note:</B>Because comments can get quite extensive in bugs, doing this particular type
of query can take a long time.
<a name="url"></a>
<a name="url"></a>
<h4>Associated URL</h4>
<h4>Associated URL</h4>
...
@@ -490,6 +491,8 @@ user with the proper permissions can edit these keywords. The following is a lis
...
@@ -490,6 +491,8 @@ user with the proper permissions can edit these keywords. The following is a lis
<p>Module options are where you select what program, module and version the bugs you want to
<p>Module options are where you select what program, module and version the bugs you want to
...
@@ -738,8 +693,9 @@ print qq{
...
@@ -738,8 +693,9 @@ print qq{
<p>Choosing this section lets you search through bugs that have their target milestones set to certain
<p>Choosing this section lets you search through bugs that have their target milestones set to certain
values. Milestones are kind of like versions. They are specific tentative dates where a massive
values. Milestones are kind of like versions. They are specific tentative dates where a massive
phasing out of bugs occur and a relatively stable release is produced. Milestones used to be in the
phasing out of bugs occur and a relatively stable release is produced. For example, Mozilla.org had milestones in the
form "M18", but now are in the form of "Mozilla0.9". <a href="http://www.mozilla.org/roadmap.html">The roadmap</a>.
form of "M10" or "M18", but now are in the form of "Mozilla0.9". Bugzilla milestones are in the form of "Bugzilla 2.12",
"Bugzilla 2.14", etc.
};
};
...
@@ -1424,7 +1380,7 @@ print qq{
...
@@ -1424,7 +1380,7 @@ print qq{
<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>
<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.
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:
<P>Lots of Bugzilla use documention is available through Mozilla.org and other sites:
<a href="http://www.mozilla.org/bugs/">Bugzilla General Information</a><br>
<a href="http://www.mozilla.org/bugs/">Bugzilla General Information</a><br>
...
@@ -1444,22 +1400,7 @@ doesn't have a duplicate before submitting it, as is stated clearly in
...
@@ -1444,22 +1400,7 @@ doesn't have a duplicate before submitting it, as is stated clearly in
The people reading your bugs are busy and usually swamped with bugs. Therefore, you are doing everyone
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.
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.
};
};
...
@@ -1474,12 +1415,12 @@ print qq{
...
@@ -1474,12 +1415,12 @@ print qq{
<a name="samplequery"></a>
<a name="samplequery"></a>
<p><br><center><h3>Sample Query</h3></center>
<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">
<p>Ok. <b>So lets find a bug!</b> We'll borrow the Mozilla.org database because it's handy.
copy</a> of the query window so you can easily switch between
<BR>First, lets make a <a target="_blank" href="http://bugzilla.mozilla.org/query.cgi">
this document and the query.
copy</a> of the query window so you can easily switch between this document and the query.
<p>Do the following:
<p>Do the following:
<ul>
<ul>
<li>Go to the status field in Bug Settings and select all.
<li>Go to the "Status" field in and select all fields (or deselect all fields).
<li>In Text Search options, put Autoscroll in the summary and Panning in the description entry box
<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).
(meaning that panning is somewhere in the comments and the bug's summary has Autoscroll in it).
</ul>
</ul>
...
@@ -1488,8 +1429,6 @@ this document and the query.
...
@@ -1488,8 +1429,6 @@ this document and the query.
printqq{
printqq{
<hr>
<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!
