From beb95bd9100a6628e2c9a46b769994997a047701 Mon Sep 17 00:00:00 2001 From: "tara%tequilarista.org" <> Date: Sat, 21 Apr 2001 05:08:09 +0000 Subject: Checking in massive changes to make this document more generic to all bugzilla installations --- queryhelp.cgi | 97 +++++++++++------------------------------------------------ 1 file changed, 18 insertions(+), 79 deletions(-) diff --git a/queryhelp.cgi b/queryhelp.cgi index 900959939..a2069aa84 100755 --- a/queryhelp.cgi +++ b/queryhelp.cgi @@ -50,7 +50,9 @@ print qq{ -
"I already know how to use Bugzilla, but would like information about Bugzilla and the author of this document."
-
"Ok, I am almost certain the bug I discovered isn't in Bugzilla, how do I submit the bug?" - Read the guidelines first!
+
"Ok, I am almost certain the bug I discovered isn't in Bugzilla, how do I submit the bug?" - Read the guidelines first!
Platform
The platform field is the hardware platform against which the bug was reported. Legal
@@ -469,6 +468,8 @@ how a match will be determined.
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.
+
Note:Because comments can get quite extensive in bugs, doing this particular type
+of query can take a long time.
-
|
-
Module options are where you select what program, module and version the bugs you want to @@ -738,8 +693,9 @@ print qq{
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 -phasing out of bugs occur and a relatively stable release is produced. Milestones used to be in the -form "M18", but now are in the form of "Mozilla0.9". The roadmap. +phasing out of bugs occur and a relatively stable release is produced. For example, Mozilla.org had milestones in the +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{
Written and adapted from some older Bugzilla documents (by Terry Weissman, Tara Hernandez and others) by Brian Bober You can talk to me on irc.mozilla.org - #mozilla, #mozwebtools, #mozillazine, I go by the name netdemon. -
For more information than you can find in this document: +
Lots of Bugzilla use documention is available through Mozilla.org and other sites:
How To Find Previously Reported Bugs
Bugzilla General Information
@@ -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
a huge favor to search for a duplicate.
-
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{
Ok. So lets find a bug! First, lets make a -copy of the query window so you can easily switch between -this document and the query. +
Ok. So lets find a bug! We'll borrow the Mozilla.org database because it's handy.
+
First, lets make a
+copy of the query window so you can easily switch between this document and the query.
Do the following: