></DT
><DT
>1.6. <A
-HREF="contributors.html"
->Contributors</A
-></DT
-><DT
->1.7. <A
-HREF="feedback.html"
->Feedback</A
-></DT
-><DT
->1.8. <A
HREF="translations.html"
>Translations</A
></DT
><DT
HREF="conventions.html"
>Document Conventions</A
></DT
><A
NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
><P
-> This document was started on September 17, 2000 by Matthew P.
- Barnson after a great deal of procrastination updating the
- Bugzilla FAQ, which I left untouched for nearly half a year.
- After numerous complete rewrites and reformatting, it is the
- document you see today.
- </P
-><P
> Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
><P
> This release of the Bugzilla Guide is the
<EM
->2.14</EM
+>2.16</EM
> release. It is so named that it
may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects,
>http://www.bugzilla.org/</A
>. Intermediate releases will have
a minor revision number following a period. The current version
- of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
+ of Bugzilla, as of this writing (April 2nd, 2002) is 2.16; if
something were seriously wrong with that edition of the Guide,
subsequent releases would receive an additional dotted-decimal
- digit to indicate the update (2.14.1, 2.14.2, etc.).
+ digit to indicate the update (2.16.1, 2.16.2, etc.).
Got it? Good.
</P
-><P
-> I wrote this in response to the enormous demand for decent
- Bugzilla documentation. I have incorporated instructions from
- the Bugzilla README, Frequently Asked Questions, Database Schema
- Document, and various mailing lists to create it. Chances are,
- there are glaring errors in this documentation; please contact
- <TT
-CLASS="email"
-><<A
-HREF="mailto:barnboy@trilobyte.net"
->barnboy@trilobyte.net</A
->></TT
-> to correct them.
- </P
></DIV
><DIV
CLASS="NAVFOOTER"
><H2
CLASS="section"
><A
-NAME="AEN2517">D.5.1. Things that have caused problems and should be avoided</H2
+NAME="AEN2436">D.5.1. Things that have caused problems and should be avoided</H2
><P
></P
><OL
><H2
CLASS="section"
><A
-NAME="AEN2531">D.5.2. Coding Style for Bugzilla</H2
+NAME="AEN2450">D.5.2. Coding Style for Bugzilla</H2
><P
> While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore,
><H1
CLASS="section"
><A
-NAME="conventions">1.9. Document Conventions</H1
+NAME="conventions">1.7. Document Conventions</H1
><P
> This document uses the following conventions
</P
><DIV
CLASS="informaltable"
><A
></P
><TABLE
BORDER="0"
ALIGN="LEFT"
VALIGN="TOP"
><P
->Warnings.</P
+>Don't run with scissors!</P
></TD
></TR
></TABLE
ALIGN="LEFT"
VALIGN="TOP"
><P
->Hint.</P
+>Warm jar lids under the hot tap to loosen them.</P
></TD
></TR
></TABLE
ALIGN="LEFT"
VALIGN="TOP"
><P
->Note.</P
+>Dear John...</P
></TD
></TR
></TABLE
ALIGN="LEFT"
VALIGN="TOP"
><P
->Warning.</P
+>Read this or the cat gets it.</P
></TD
></TR
></TABLE
><A
NAME="copyright">1.2. Copyright Information</H1
><A
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
the license is included in the section entitled "GNU Free
- Documentation LIcense".
+ Documentation License".
</P
></TD
><TD
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
->Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
+>Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
></TD
><TD
WIDTH="10%"
><P
> If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
- please contact Matthew P. Barnson.
+ please contact The Bugzilla Team.
</P
></DIV
><DIV
TITLE="New Versions"
HREF="newversions.html"><LINK
REL="NEXT"
-TITLE="Contributors"
-HREF="contributors.html"></HEAD
+TITLE="Translations"
+HREF="translations.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="contributors.html"
+HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
</P
><P
> <A
+HREF="mailto://mbarnson@sisna.com"
+TARGET="_top"
+>Matthew P. Barnson</A
+>
+ for pulling together the Bugzilla Guide and shepherding it to 2.14.
+ </P
+><P
+> <A
HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
> netscape.public.mozilla.webtools</A
> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</P
+><P
+> Thanks also go to the following people for significant contributions
+ to this documentation (in no particular order):
+ </P
+><P
+> Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
+ Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"
ALIGN="right"
VALIGN="top"
><A
-HREF="contributors.html"
+HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Contributors</TD
+>Translations</TD
></TR
></TABLE
></DIV
><H2
CLASS="section"
><A
-NAME="AEN2353">C.2.1. Bugzilla Database Basics</H2
+NAME="AEN2272">C.2.1. Bugzilla Database Basics</H2
><P
> If you were like me, at this point you're totally clueless
about the internals of MySQL, and if it weren't for this
><H3
CLASS="section"
><A
-NAME="AEN2382">C.2.1.1. Bugzilla Database Tables</H3
+NAME="AEN2301">C.2.1.1. Bugzilla Database Tables</H3
><P
> Imagine your MySQL database as a series of
spreadsheets, and you won't be too far off. If you use this
</P
><P
> Naming of particular products or brands should not be seen as
- endorsements, with the exception of the term "GNU/Linux". I
+ endorsements, with the exception of the term "GNU/Linux". We
wholeheartedly endorse the use of GNU/Linux in every situation
where it is appropriate. It is an extremely versatile, stable,
and robust operating system that offers an ideal operating
><P
> You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
- Heaven knows it's saved my bacon time after time; if you
- implement any suggestion in this Guide, implement this one!
+ If you implement any suggestion in this Guide, implement this one!
</P
><P
> Although the Bugzilla development team has taken great care to
></TR
><TR
><TD
-> Release Notes for Bugzilla 2.14 are available at
+> Release Notes for Bugzilla 2.16 are available at
<TT
CLASS="filename"
>docs/rel_notes.txt</TT
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1735"
+HREF="faq.html#AEN1654"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1741"
+HREF="faq.html#AEN1660"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1747"
+HREF="faq.html#AEN1666"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1754"
+HREF="faq.html#AEN1673"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1779"
+HREF="faq.html#AEN1698"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1785"
+HREF="faq.html#AEN1704"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1792"
+HREF="faq.html#AEN1711"
> How do I change my user name in Bugzilla?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1797"
+HREF="faq.html#AEN1716"
> Why doesn't Bugzilla offer this or that feature or compatability
with this other tracking software?
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1804"
+HREF="faq.html#AEN1723"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1822"
+HREF="faq.html#AEN1741"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1839"
+HREF="faq.html#AEN1758"
> What about Red Hat Bugzilla?
</A
></DT
><DT
>A.2.2. <A
-HREF="faq.html#AEN1847"
+HREF="faq.html#AEN1766"
> What are the primary benefits of Red Hat Bugzilla?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1875"
+HREF="faq.html#AEN1794"
> What's the current status of Red Hat Bugzilla?
</A
></DT
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1888"
+HREF="faq.html#AEN1807"
> What is Loki Bugzilla (Fenris)?
</A
></DT
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1899"
+HREF="faq.html#AEN1818"
> Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
</A
></DT
><DT
>A.4.2. <A
-HREF="faq.html#AEN1904"
+HREF="faq.html#AEN1823"
> Has anyone you know of already done any Bugzilla integration with
Perforce (SCM software)?
</A
></DT
><DT
>A.4.3. <A
-HREF="faq.html#AEN1909"
+HREF="faq.html#AEN1828"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1914"
+HREF="faq.html#AEN1833"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.4.5. <A
-HREF="faq.html#AEN1919"
+HREF="faq.html#AEN1838"
> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1924"
+HREF="faq.html#AEN1843"
> Does Bugzilla allow us to define our own priorities and levels? Do we
have complete freedom to change the labels of fields and format of them, and
the choice of acceptable values?
></DT
><DT
>A.4.7. <A
-HREF="faq.html#AEN1931"
+HREF="faq.html#AEN1850"
> The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link. How do I get a footer
on static HTML pages?
></DT
><DT
>A.4.8. <A
-HREF="faq.html#AEN1953"
+HREF="faq.html#AEN1872"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.4.9. <A
-HREF="faq.html#AEN1961"
+HREF="faq.html#AEN1880"
> Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
</A
></DT
><DT
>A.4.10. <A
-HREF="faq.html#AEN1966"
+HREF="faq.html#AEN1885"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.4.11. <A
-HREF="faq.html#AEN1971"
+HREF="faq.html#AEN1890"
> If there is email notification, do users have to have any particular
type of email application?
</A
></DT
><DT
>A.4.12. <A
-HREF="faq.html#AEN1978"
+HREF="faq.html#AEN1897"
> If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
></DT
><DT
>A.4.13. <A
-HREF="faq.html#AEN1983"
+HREF="faq.html#AEN1902"
> Does Bugzilla allow data to be imported and exported? If I had outsiders
write up a bug report using a MS Word bug template, could that template be
imported into "matching" fields? If I wanted to take the results of a query
></DT
><DT
>A.4.14. <A
-HREF="faq.html#AEN1991"
+HREF="faq.html#AEN1910"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.4.15. <A
-HREF="faq.html#AEN1996"
+HREF="faq.html#AEN1915"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.4.16. <A
-HREF="faq.html#AEN2001"
+HREF="faq.html#AEN1920"
> Can a user re-run a report with a new project, same query?
</A
></DT
><DT
>A.4.17. <A
-HREF="faq.html#AEN2006"
+HREF="faq.html#AEN1925"
> Can a user modify an existing report and then save it into another name?
</A
></DT
><DT
>A.4.18. <A
-HREF="faq.html#AEN2011"
+HREF="faq.html#AEN1930"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.4.19. <A
-HREF="faq.html#AEN2016"
+HREF="faq.html#AEN1935"
> Can the admin person establish separate group and individual user
privileges?
</A
></DT
><DT
>A.4.20. <A
-HREF="faq.html#AEN2021"
+HREF="faq.html#AEN1940"
> Does Bugzilla provide record locking when there is simultaneous access
to the same bug? Does the second person get a notice that the bug is in use
or how are they notified?
></DT
><DT
>A.4.21. <A
-HREF="faq.html#AEN2026"
+HREF="faq.html#AEN1945"
> Are there any backup features provided?
</A
></DT
><DT
>A.4.22. <A
-HREF="faq.html#AEN2032"
+HREF="faq.html#AEN1951"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.4.23. <A
-HREF="faq.html#AEN2037"
+HREF="faq.html#AEN1956"
> What type of human resources are needed to be on staff to install and
maintain Bugzilla? Specifically, what type of skills does the person need to
have? I need to find out if we were to go with Bugzilla, what types of
></DT
><DT
>A.4.24. <A
-HREF="faq.html#AEN2044"
+HREF="faq.html#AEN1963"
> What time frame are we looking at if we decide to hire people to install
and maintain the Bugzilla? Is this something that takes hours or weeks to
install and a couple of hours per week to maintain and customize or is this
></DT
><DT
>A.4.25. <A
-HREF="faq.html#AEN2049"
+HREF="faq.html#AEN1968"
> Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
</A
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN2056"
+HREF="faq.html#AEN1975"
> How do I download and install Bugzilla?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN2062"
+HREF="faq.html#AEN1981"
> How do I install Bugzilla on Windows NT?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN2067"
+HREF="faq.html#AEN1986"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN2074"
+HREF="faq.html#AEN1993"
> How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide!)?
</A
></DT
><DT
>A.6.2. <A
-HREF="faq.html#AEN2080"
+HREF="faq.html#AEN1999"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN2085"
+HREF="faq.html#AEN2004"
> I've implemented the security fixes mentioned in Chris Yeh's security
advisory of 5/10/2000 advising not to run MySQL as root, and am running into
problems with MySQL no longer working correctly.
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN2092"
+HREF="faq.html#AEN2011"
> I have a user who doesn't want to receive any more email from Bugzilla.
How do I stop it entirely for this user?
</A
></DT
><DT
>A.7.2. <A
-HREF="faq.html#AEN2097"
+HREF="faq.html#AEN2016"
> I'm evaluating/testing Bugzilla, and don't want it to send email to
anyone but me. How do I do it?
</A
></DT
><DT
>A.7.3. <A
-HREF="faq.html#AEN2102"
+HREF="faq.html#AEN2021"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.7.4. <A
-HREF="faq.html#AEN2108"
+HREF="faq.html#AEN2027"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.7.5. <A
-HREF="faq.html#AEN2115"
+HREF="faq.html#AEN2034"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.7.6. <A
-HREF="faq.html#AEN2120"
+HREF="faq.html#AEN2039"
> Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.7.7. <A
-HREF="faq.html#AEN2127"
+HREF="faq.html#AEN2046"
> How come email never reaches me from bugzilla changes?
</A
></DT
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN2135"
+HREF="faq.html#AEN2054"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN2140"
+HREF="faq.html#AEN2059"
> Bugs are missing from queries, but exist in the database (and I can pull
them up by specifying the bug ID). What's wrong?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN2145"
+HREF="faq.html#AEN2064"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.8.4. <A
-HREF="faq.html#AEN2153"
+HREF="faq.html#AEN2072"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.8.5. <A
-HREF="faq.html#AEN2158"
+HREF="faq.html#AEN2077"
> I try to add myself as a user, but Bugzilla always tells me my password is wrong.
</A
></DT
><DT
>A.8.6. <A
-HREF="faq.html#AEN2163"
+HREF="faq.html#AEN2082"
> I think I've set up MySQL permissions correctly, but bugzilla still can't
connect.
</A
></DT
><DT
>A.8.7. <A
-HREF="faq.html#AEN2168"
+HREF="faq.html#AEN2087"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
></DT
><DT
>A.8.8. <A
-HREF="faq.html#AEN2175"
+HREF="faq.html#AEN2094"
> Why do I get bizarre errors when trying to submit data, particularly problems
with "groupset"?
</A
></DT
><DT
>A.8.9. <A
-HREF="faq.html#AEN2180"
+HREF="faq.html#AEN2099"
> How come even after I delete bugs, the long descriptions show up?
</A
></DT
><DL
><DT
>A.9.1. <A
-HREF="faq.html#AEN2190"
+HREF="faq.html#AEN2109"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.9.2. <A
-HREF="faq.html#AEN2195"
+HREF="faq.html#AEN2114"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.9.3. <A
-HREF="faq.html#AEN2200"
+HREF="faq.html#AEN2119"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.9.4. <A
-HREF="faq.html#AEN2208"
+HREF="faq.html#AEN2127"
> Can I have some general instructions on how to make Bugzilla on Win32 work?
</A
></DT
><DT
>A.9.5. <A
-HREF="faq.html#AEN2214"
+HREF="faq.html#AEN2133"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
><DL
><DT
>A.10.1. <A
-HREF="faq.html#AEN2235"
+HREF="faq.html#AEN2154"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.10.2. <A
-HREF="faq.html#AEN2241"
+HREF="faq.html#AEN2160"
> I'm confused by the behavior of the "accept" button in the Show Bug form.
Why doesn't it assign the bug to me when I accept it?
</A
></DT
><DT
>A.10.3. <A
-HREF="faq.html#AEN2251"
+HREF="faq.html#AEN2170"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.10.4. <A
-HREF="faq.html#AEN2256"
+HREF="faq.html#AEN2175"
> Email submissions to Bugzilla that have attachments end up asking me to
save it as a "cgi" file.
</A
></DT
><DT
>A.10.5. <A
-HREF="faq.html#AEN2261"
+HREF="faq.html#AEN2180"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DL
><DT
>A.11.1. <A
-HREF="faq.html#AEN2268"
+HREF="faq.html#AEN2187"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.11.2. <A
-HREF="faq.html#AEN2277"
+HREF="faq.html#AEN2196"
> How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</A
></DT
><DT
>A.11.3. <A
-HREF="faq.html#AEN2283"
+HREF="faq.html#AEN2202"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
CLASS="question"
><P
><A
-NAME="AEN1735"><B
+NAME="AEN1654"><B
>A.1.1. </B
>
Where can I find information about Bugzilla?</P
CLASS="question"
><P
><A
-NAME="AEN1741"><B
+NAME="AEN1660"><B
>A.1.2. </B
>
What license is Bugzilla distributed under?
CLASS="question"
><P
><A
-NAME="AEN1747"><B
+NAME="AEN1666"><B
>A.1.3. </B
>
How do I get commercial support for Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1754"><B
+NAME="AEN1673"><B
>A.1.4. </B
>
What major companies or projects are currently using Bugzilla
CLASS="question"
><P
><A
-NAME="AEN1779"><B
+NAME="AEN1698"><B
>A.1.5. </B
>
Who maintains Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1785"><B
+NAME="AEN1704"><B
>A.1.6. </B
>
How does Bugzilla stack up against other bug-tracking databases?
CLASS="question"
><P
><A
-NAME="AEN1792"><B
+NAME="AEN1711"><B
>A.1.7. </B
>
How do I change my user name in Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN1797"><B
+NAME="AEN1716"><B
>A.1.8. </B
>
Why doesn't Bugzilla offer this or that feature or compatability
CLASS="question"
><P
><A
-NAME="AEN1804"><B
+NAME="AEN1723"><B
>A.1.9. </B
>
Why MySQL? I'm interested in seeing Bugzilla run on
> </B
>Terry Weissman answers,
<A
-NAME="AEN1
808"><BLOCKQUOTE
+NAME="AEN1
727"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> You're not the only one. But <EM
CLASS="question"
><P
><A
-NAME="AEN1822"><B
+NAME="AEN1741"><B
>A.1.10. </B
>
Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
><P
> Here's Terry Weissman's comment, for some historical context:
<A
-NAME="AEN1
827"><BLOCKQUOTE
+NAME="AEN1
746"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> [This was] purely my own convention. I wanted a place to put a version of
CLASS="question"
><P
><A
-NAME="AEN1839"><B
+NAME="AEN1758"><B
>A.2.1. </B
>
What about Red Hat Bugzilla?
><P
> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
<A
-NAME="AEN1
844"><BLOCKQUOTE
+NAME="AEN1
763"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Somebody needs to take the ball and run with it. I'm the only
CLASS="question"
><P
><A
-NAME="AEN1847"><B
+NAME="AEN1766"><B
>A.2.2. </B
>
What are the primary benefits of Red Hat Bugzilla?
>Dave Lawrence</EM
>:
<A
-NAME="AEN1
852"><BLOCKQUOTE
+NAME="AEN1
771"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> For the record, we are not using any template type implementation for
CLASS="question"
><P
><A
-NAME="AEN1875"><B
+NAME="AEN1794"><B
>A.2.3. </B
>
What's the current status of Red Hat Bugzilla?
>Dave Lawrence</EM
>:
<A
-NAME="AEN18
82"><BLOCKQUOTE
+NAME="AEN18
01"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> I suppose the current thread warrants an update on the status of
CLASS="question"
><P
><A
-NAME="AEN1888"><B
+NAME="AEN1807"><B
>A.3.1. </B
>
What is Loki Bugzilla (Fenris)?
HREF="http://fenris.lokigames.com/"
TARGET="_top"
>http://fenris.lokigames.com</A
->. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.14 rather than using a fork, but it's up to you.
+>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.16 rather than using a fork, but it's up to you.
</P
></DIV
></DIV
CLASS="question"
><P
><A
-NAME="AEN1899"><B
+NAME="AEN1818"><B
>A.4.1. </B
>
Is Bugzilla web-based or do you have to have specific software or
CLASS="question"
><P
><A
-NAME="AEN1904"><B
+NAME="AEN1823"><B
>A.4.2. </B
>
Has anyone you know of already done any Bugzilla integration with
CLASS="question"
><P
><A
-NAME="AEN1909"><B
+NAME="AEN1828"><B
>A.4.3. </B
>
Does Bugzilla allow the user to track multiple projects?
CLASS="question"
><P
><A
-NAME="AEN1914"><B
+NAME="AEN1833"><B
>A.4.4. </B
>
If I am on many projects, and search for all bugs assigned to me, will
CLASS="question"
><P
><A
-NAME="AEN1919"><B
+NAME="AEN1838"><B
>A.4.5. </B
>
Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
CLASS="question"
><P
><A
-NAME="AEN1924"><B
+NAME="AEN1843"><B
>A.4.6. </B
>
Does Bugzilla allow us to define our own priorities and levels? Do we
CLASS="question"
><P
><A
-NAME="AEN1931"><B
+NAME="AEN1850"><B
>A.4.7. </B
>
The index.html page doesn't show the footer. It's really annoying to have
CLASS="question"
><P
><A
-NAME="AEN1953"><B
+NAME="AEN1872"><B
>A.4.8. </B
>
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
CLASS="question"
><P
><A
-NAME="AEN1961"><B
+NAME="AEN1880"><B
>A.4.9. </B
>
Is there email notification and if so, what do you see when you get an
CLASS="question"
><P
><A
-NAME="AEN1966"><B
+NAME="AEN1885"><B
>A.4.10. </B
>
Can email notification be set up to send to multiple
CLASS="question"
><P
><A
-NAME="AEN1971"><B
+NAME="AEN1890"><B
>A.4.11. </B
>
If there is email notification, do users have to have any particular
CLASS="question"
><P
><A
-NAME="AEN1978"><B
+NAME="AEN1897"><B
>A.4.12. </B
>
If I just wanted to track certain bugs, as they go through life, can I
CLASS="question"
><P
><A
-NAME="AEN1983"><B
+NAME="AEN1902"><B
>A.4.13. </B
>
Does Bugzilla allow data to be imported and exported? If I had outsiders
CLASS="question"
><P
><A
-NAME="AEN1991"><B
+NAME="AEN1910"><B
>A.4.14. </B
>
Has anyone converted Bugzilla to another language to be used in other
CLASS="question"
><P
><A
-NAME="AEN1996"><B
+NAME="AEN1915"><B
>A.4.15. </B
>
Can a user create and save reports? Can they do this in Word format?
CLASS="question"
><P
><A
-NAME="AEN2001"><B
+NAME="AEN1920"><B
>A.4.16. </B
>
Can a user re-run a report with a new project, same query?
CLASS="question"
><P
><A
-NAME="AEN2006"><B
+NAME="AEN1925"><B
>A.4.17. </B
>
Can a user modify an existing report and then save it into another name?
CLASS="question"
><P
><A
-NAME="AEN2011"><B
+NAME="AEN1930"><B
>A.4.18. </B
>
Does Bugzilla have the ability to search by word, phrase, compound
CLASS="question"
><P
><A
-NAME="AEN2016"><B
+NAME="AEN1935"><B
>A.4.19. </B
>
Can the admin person establish separate group and individual user
CLASS="question"
><P
><A
-NAME="AEN2021"><B
+NAME="AEN1940"><B
>A.4.20. </B
>
Does Bugzilla provide record locking when there is simultaneous access
CLASS="question"
><P
><A
-NAME="AEN2026"><B
+NAME="AEN1945"><B
>A.4.21. </B
>
Are there any backup features provided?
CLASS="question"
><P
><A
-NAME="AEN2032"><B
+NAME="AEN1951"><B
>A.4.22. </B
>
Can users be on the system while a backup is in progress?
CLASS="question"
><P
><A
-NAME="AEN2037"><B
+NAME="AEN1956"><B
>A.4.23. </B
>
What type of human resources are needed to be on staff to install and
CLASS="question"
><P
><A
-NAME="AEN2044"><B
+NAME="AEN1963"><B
>A.4.24. </B
>
What time frame are we looking at if we decide to hire people to install
CLASS="question"
><P
><A
-NAME="AEN2049"><B
+NAME="AEN1968"><B
>A.4.25. </B
>
Is there any licensing fee or other fees for using Bugzilla? Any
CLASS="question"
><P
><A
-NAME="AEN2056"><B
+NAME="AEN1975"><B
>A.5.1. </B
>
How do I download and install Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN2062"><B
+NAME="AEN1981"><B
>A.5.2. </B
>
How do I install Bugzilla on Windows NT?
CLASS="question"
><P
><A
-NAME="AEN2067"><B
+NAME="AEN1986"><B
>A.5.3. </B
>
Is there an easy way to change the Bugzilla cookie name?
CLASS="question"
><P
><A
-NAME="AEN2074"><B
+NAME="AEN1993"><B
>A.6.1. </B
>
How do I completely disable MySQL security if it's giving me problems
CLASS="question"
><P
><A
-NAME="AEN2080"><B
+NAME="AEN1999"><B
>A.6.2. </B
>
Are there any security problems with Bugzilla?
CLASS="question"
><P
><A
-NAME="AEN2085"><B
+NAME="AEN2004"><B
>A.6.3. </B
>
I've implemented the security fixes mentioned in Chris Yeh's security
CLASS="question"
><P
><A
-NAME="AEN2092"><B
+NAME="AEN2011"><B
>A.7.1. </B
>
I have a user who doesn't want to receive any more email from Bugzilla.
CLASS="question"
><P
><A
-NAME="AEN2097"><B
+NAME="AEN2016"><B
>A.7.2. </B
>
I'm evaluating/testing Bugzilla, and don't want it to send email to
CLASS="question"
><P
><A
-NAME="AEN2102"><B
+NAME="AEN2021"><B
>A.7.3. </B
>
I want whineatnews.pl to whine at something more, or other than, only new
CLASS="question"
><P
><A
-NAME="AEN2108"><B
+NAME="AEN2027"><B
>A.7.4. </B
>
I don't like/want to use Procmail to hand mail off to bug_email.pl.
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN2
112"><BLOCKQUOTE
+NAME="AEN2
031"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
CLASS="question"
><P
><A
-NAME="AEN2115"><B
+NAME="AEN2034"><B
>A.7.5. </B
>
How do I set up the email interface to submit/change bugs via email?
CLASS="question"
><P
><A
-NAME="AEN2120"><B
+NAME="AEN2039"><B
>A.7.6. </B
>
Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
CLASS="question"
><P
><A
-NAME="AEN2127"><B
+NAME="AEN2046"><B
>A.7.7. </B
>
How come email never reaches me from bugzilla changes?
CLASS="question"
><P
><A
-NAME="AEN2135"><B
+NAME="AEN2054"><B
>A.8.1. </B
>
I've heard Bugzilla can be used with Oracle?
CLASS="question"
><P
><A
-NAME="AEN2140"><B
+NAME="AEN2059"><B
>A.8.2. </B
>
Bugs are missing from queries, but exist in the database (and I can pull
CLASS="question"
><P
><A
-NAME="AEN2145"><B
+NAME="AEN2064"><B
>A.8.3. </B
>
I think my database might be corrupted, or contain invalid entries. What
CLASS="question"
><P
><A
-NAME="AEN2153"><B
+NAME="AEN2072"><B
>A.8.4. </B
>
I want to manually edit some entries in my database. How?
CLASS="question"
><P
><A
-NAME="AEN2158"><B
+NAME="AEN2077"><B
>A.8.5. </B
>
I try to add myself as a user, but Bugzilla always tells me my password is wrong.
CLASS="question"
><P
><A
-NAME="AEN2163"><B
+NAME="AEN2082"><B
>A.8.6. </B
>
I think I've set up MySQL permissions correctly, but bugzilla still can't
CLASS="question"
><P
><A
-NAME="AEN2168"><B
+NAME="AEN2087"><B
>A.8.7. </B
>
How do I synchronize bug information among multiple different Bugzilla
CLASS="question"
><P
><A
-NAME="AEN2175"><B
+NAME="AEN2094"><B
>A.8.8. </B
>
Why do I get bizarre errors when trying to submit data, particularly problems
CLASS="question"
><P
><A
-NAME="AEN2180"><B
+NAME="AEN2099"><B
>A.8.9. </B
>
How come even after I delete bugs, the long descriptions show up?
><B
> </B
>
- This should only happen with Bugzilla 2.14 if you are
+ This should only happen with Bugzilla 2.16 if you are
using the <SPAN
CLASS="QUOTE"
>"shadow database"</SPAN
CLASS="question"
><P
><A
-NAME="AEN2190"><B
+NAME="AEN2109"><B
>A.9.1. </B
>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
CLASS="question"
><P
><A
-NAME="AEN2195"><B
+NAME="AEN2114"><B
>A.9.2. </B
>
Is there a "Bundle::Bugzilla" equivalent for Win32?
CLASS="question"
><P
><A
-NAME="AEN2200"><B
+NAME="AEN2119"><B
>A.9.3. </B
>
CGI's are failing with a "something.cgi is not a valid Windows NT
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN2
205"><BLOCKQUOTE
+NAME="AEN2
124"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> "Set application mappings. In the ISM, map the extension for the script
CLASS="question"
><P
><A
-NAME="AEN2208"><B
+NAME="AEN2127"><B
>A.9.4. </B
>
Can I have some general instructions on how to make Bugzilla on Win32 work?
CLASS="question"
><P
><A
-NAME="AEN2214"><B
+NAME="AEN2133"><B
>A.9.5. </B
>
I'm having trouble with the perl modules for NT not being able to talk to
CLASS="question"
><P
><A
-NAME="AEN2235"><B
+NAME="AEN2154"><B
>A.10.1. </B
>
The query page is very confusing. Isn't there a simpler way to query?
CLASS="question"
><P
><A
-NAME="AEN2241"><B
+NAME="AEN2160"><B
>A.10.2. </B
>
I'm confused by the behavior of the "accept" button in the Show Bug form.
CLASS="question"
><P
><A
-NAME="AEN2251"><B
+NAME="AEN2170"><B
>A.10.3. </B
>
I can't upload anything into the database via the "Create Attachment"
CLASS="question"
><P
><A
-NAME="AEN2256"><B
+NAME="AEN2175"><B
>A.10.4. </B
>
Email submissions to Bugzilla that have attachments end up asking me to
CLASS="question"
><P
><A
-NAME="AEN2261"><B
+NAME="AEN2180"><B
>A.10.5. </B
>
How do I change a keyword in Bugzilla, once some bugs are using it?
CLASS="question"
><P
><A
-NAME="AEN2268"><B
+NAME="AEN2187"><B
>A.11.1. </B
>
What bugs are in Bugzilla right now?
CLASS="question"
><P
><A
-NAME="AEN2277"><B
+NAME="AEN2196"><B
>A.11.2. </B
>
How can I change the default priority to a null value? For instance, have the default
CLASS="question"
><P
><A
-NAME="AEN2283"><B
+NAME="AEN2202"><B
>A.11.3. </B
>
What's the best way to submit patches? What guidelines should I follow?
><H2
CLASS="section"
><A
-NAME="AEN942">3.5.1. Modifying Your Running System</H2
+NAME="AEN874">3.5.1. Modifying Your Running System</H2
><P
> Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
><H2
CLASS="section"
><A
-NAME="AEN949">3.5.2. Upgrading From Previous Versions</H2
+NAME="AEN881">3.5.2. Upgrading From Previous Versions</H2
><P
-> The developers of Bugzilla are constantly adding new tables, columns and
- fields. You'll get SQL errors if you just update the code. The strategy
- to update is to simply always run the checksetup.pl script whenever
- you upgrade your installation of Bugzilla. If you want to see what has
- changed, you can read the comments in that file, starting from the end.
+> A plain Bugzilla is fairly easy to upgrade from one version to a newer one.
+ However, things get a bit more complicated if you've made changes to
+ Bugzilla's code. In this case, you may have to re-make or reapply those
+ changes.
+ It is recommended that you take a backup of your database and your entire
+ Bugzilla installation before attempting an upgrade. You can upgrade a 'clean'
+ installation by untarring a new tarball over the old installation. If you
+ are upgrading from 2.12 or later, you can type <TT
+CLASS="filename"
+>cvs -z3
+ update</TT
+>, and resolve conflicts if there are any.
+ </P
+><P
+> Because the developers of Bugzilla are constantly adding new tables, columns
+ and fields, you'll probably get SQL errors if you just update the code and
+ attempt to use Bugzilla. Always run the checksetup.pl script whenever
+ you upgrade your installation.
</P
><P
> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
generate the <TT
CLASS="filename"
>.htaccess</TT
-> files.
+> files. These .htaccess files
+ will not work with Apache 1.2.x - but this has security holes, so you
+ shouldn't be using it anyway.
<DIV
CLASS="note"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
-NAME="AEN26
86"><BLOCKQUOTE
+NAME="AEN26
05"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Copyright (c) YEAR YOUR NAME.
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN25
96"><BLOCKQUOTE
+NAME="AEN25
15"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc.
><H1
CLASS="glossdiv"
><A
-NAME="AEN2691">0-9, high ascii</H1
+NAME="AEN2610">0-9, high ascii</H1
><DL
><DT
><B
><DIV
CLASS="example"
><A
><B
>Example 1. A Sample Product</B
></P
></TR
></TABLE
><P
-> Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or
- administering a Bugzilla installation, please consult the
+> This section contains information for end-users of Bugzilla.
+ If you are administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
- This section is principally aimed towards developing end-user
- mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking
- software.
</P
><P
-> Throughout this portion of the Guide, we will refer to user
- account options available at the Bugzilla test installation,
+> There is a Bugzilla test installation, called
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
-> landfill.tequilarista.org</A
->.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Some people have run into difficulties completing this
- tutorial. If you run into problems, please check the
- updated online documentation available at <A
-HREF="http://www.trilobyte.net/barnsons/"
-TARGET="_top"
->http://www.trilobyte.net/barnsons</A
->. If you're still stumped, please subscribe to the newsgroup and provide details of exactly what's stumping you! If enough people complain, I'll have to fix it in the next version of this Guide. You can subscribe to the newsgroup at <A
-HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
-TARGET="_top"
-> news://news.mozilla.org/netscape.public.mozilla.webtools</A
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-> Although Landfill serves as a great introduction to
- Bugzilla, it does not offer all the options you would have as a
- user on your own installation of Bugzilla, nor can it do more
- than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for
+> Landfill</A
+>, which you are welcome to play with.
+ However, it does not necessarily have all Bugzilla features
+ enabled, and often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</P
><A
NAME="myaccount">2.3.1. Create a Bugzilla Account</H2
><P
-> First things first! If you want to use Bugzilla, first you
+> If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
- should use to access it. If you're test-driving the end-user
-
Bugzilla experience, use this URL: <A
+ should use to access it. If you're test-driving Bugzilla,
+ use this URL: <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
TYPE="1"
><LI
><P
-> Click the "Open a new Bugzilla account" link.
- </P
-></LI
-><LI
-><P
-> Enter your "E-mail address" and "Real Name" (or whatever
- name you want to call yourself) in the spaces provided,
- then select the "Create Account" button.
+> Click the <SPAN
+CLASS="QUOTE"
+>"Open a new Bugzilla account"</SPAN
+> link, enter your
+ email address and, optionally, your name in the spaces provided,
+ then click <SPAN
+CLASS="QUOTE"
+>"Create Account"</SPAN
+>.
</P
></LI
><LI
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
- randomly generated, and should be changed at your nearest
- opportunity (we'll go into how to do it later).
+ randomly generated, and can be changed to something more memorable.
</P
></LI
><LI
CLASS="QUOTE"
>"Log In"</SPAN
> link in the yellow area at
- the bottom of the page in your browser, then enter your
- <SPAN
-CLASS="QUOTE"
->"E-mail address"</SPAN
-> and <SPAN
-CLASS="QUOTE"
->"Password"</SPAN
->
- you just received into the spaces provided, and select
+ the bottom of the page in your browser, enter your
+ email address and password into the spaces provided, and click
<SPAN
CLASS="QUOTE"
>"Login"</SPAN
>.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> If you ever forget your password, you can come back to
- this page, enter your <SPAN
-CLASS="QUOTE"
->"E-mail address"</SPAN
->,
- then select the <SPAN
-CLASS="QUOTE"
->"E-mail me a password"</SPAN
->
- button to have your password mailed to you again so
- that you can login.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- <DIV
-CLASS="caution"
-><P
-></P
-><TABLE
-CLASS="caution"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Many modern browsers include an
- <SPAN
-CLASS="QUOTE"
->"Auto-Complete"</SPAN
-> or <SPAN
-CLASS="QUOTE"
->"Form
- Fill"</SPAN
-> feature to remember the user names and
- passwords you type in at many sites. Unfortunately,
- sometimes they attempt to guess what you will put in
- as your password, and guess wrong. If you notice a
- text box is already filled out, please overwrite the
- contents of the text box so you can be sure to input
- the correct information.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
</P
></LI
></OL
><P
-> Congratulations! If you followed these directions, you now
- are the proud owner of a user account on
- landfill.tequilarista.org (Landfill) or your local Bugzilla
- install. You should now see in your browser a page called the
- <SPAN
-CLASS="QUOTE"
->"Bugzilla Query Page"</SPAN
->. It may look daunting, but with this
- Guide to walk you through it, you will master it in no time.
+> You are now logged in. Bugzilla uses cookies for authentication, so
+ (unless your IP address changes) you should not have to log in again.
</P
></DIV
><DIV
><H2
CLASS="section"
><A
-NAME="query">2.3.2. The Bugzilla Query Page</H2
+NAME="bug_page">2.3.2. Anatomy of a Bug</H2
><P
-> The Bugzilla Query Page is the heart and soul of the Bugzilla
- user experience. It is the master interface where you can
- find any bug report, comment, or patch currently in the
- Bugzilla system. We'll go into how to create your own bug
- report later on.
- </P
-><P
-> There are efforts underway to simplify query usage. If you
- have a local installation of Bugzilla 2.12 or higher, you
- should have <TT
-CLASS="filename"
->quicksearch.html</TT
-> available to
- use and simplify your searches. There is also a helper for
- the query interface, called
- <TT
-CLASS="filename"
->queryhelp.cgi</TT
->. Landfill tends to run the
- latest code, so these two utilities should be available there
- for your perusal.
- </P
-><P
-> At this point, let's visit the query page.
- <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
+> The core of Bugzilla is the screen which displays a particular bug.
+ It's a good place to explain some Bugzilla concepts.
+ <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1"
TARGET="_top"
-> landfill.tequilarista.org/bugzilla-tip/query.cgi</A
->
- </P
-><P
-> The first thing you need to notice about the Bugzilla Query
- Page is that nearly every box you see on your screen has a
- hyperlink nearby, explaining what it is or what it does. Near
- the upper-left-hand corner of your browser window you should
- see the word <SPAN
-CLASS="QUOTE"
->"Status"</SPAN
-> underlined. Select it.
- </P
-><P
-> Notice the page that popped up? Every underlined word you see
- on your screen is a hyperlink that will take you to
- context-sensitive help. Click around for a while, and learn
- what everything here does. To return to the query interface
- after pulling up a help page, use the <SPAN
-CLASS="QUOTE"
->"Back"</SPAN
->
- button in your browser.
- </P
-><P
-> I'm sure that after checking out the online help, you are now
- an expert on the Bugzilla Query Page. If, however, you feel
- you haven't mastered it yet, let me walk you through making a
- few successful queries to find out what there are in the
- Bugzilla bug-tracking system itself.
+>Bug 1 on Landfill</A
+> is a good example. Note that the names of most fields
+ are hyperlinks; clicking them will take you to context-sensitive
+ help on that particular field.
</P
><P
></P
TYPE="1"
><LI
><P
-> Ensure you are back on the <SPAN
-CLASS="QUOTE"
->"Bugzilla Query
- Page"</SPAN
->. Do nothing in the boxes marked "Status",
- "Resolution", "Platform", "OpSys", "Priority", or
- "Severity". The default query for "Status" is to find all
- bugs that are NEW, ASSIGNED, or REOPENED, which is what we
- want. If you don't select anything in the other 5
- scrollboxes there, then you are saying that "any of these
- are OK"; we're not locking ourselves into only finding
- bugs on the "DEC" Platform, or "Windows 95" OpSys
- (Operating System). You're smart, I think you have it
- figured out.
- </P
-><P
-> Basically, selecting <EM
->anything</EM
-> on the
- query page narrows your search down. Leaving stuff
- unselected, or text boxes unfilled, broadens your search.
- </P
-></LI
-><LI
-><P
-> You see the box immediately below the top six boxes that
- contains an "Email" text box, with the words "matching
- as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to
- filter your search down based upon email address. Let's
- put my email address in there, and see what happens.
- </P
-><P
-> Type "barnboy@trilobyte.net" in the top Email text box.
- </P
-></LI
-><LI
-><P
-> Let's narrow the search some more. Scroll down until you
- find the box with the word "Program" over the top of it.
- This is where we can narrow our search down to only
- specific products (software programs or product lines) in
- our Bugzilla database. Please notice the box is a
- <EM
->scrollbox</EM
->. Using the down arrow on
- the scrollbox, scroll down until you can see an entry
- called "Bugzilla". Select this entry.
- </P
-></LI
-><LI
-><P
-> Did you notice that some of the boxes to the right changed
- when you selected "Bugzilla"? Every Program (or Product)
- has different Versions, Components, and Target Milestones
- associated with it. A "Version" is the number of a
- software program.
- <DIV
-CLASS="example"
-><A
-NAME="AEN307"><P
-><B
->Example 2-1. Some Famous Software Versions</B
-></P
-><DIV
-CLASS="informalexample"
-><A
-NAME="AEN309"><P
-></P
-><P
-> Do you remember the hype in 1995 when Microsoft
- Windows 95(r) was released? It may have been several
- years ago, but Microsoft(tm) spent over $300 Million
- advertising this new Version of their software.
- Three years later, they released Microsoft Windows
- 98(r), another new version, to great fanfare, and
- then in 2000 quietly released Microsoft Windows
- ME(Millenium Edition)(r).
- </P
-><P
-> Software "Versions" help a manufacturer
- differentiate their current product from their
- previous products. Most do not identify their
- products by the year they were released. Instead,
- the "original" version of their software will often
- be numbered "1.0", with small bug-fix releases on
- subsequent tenths of a digit. In most cases, it's
- not a decimal number; for instance, often 1.9 is an
- <EM
->older</EM
-> version of the software
- than 1.11, but is a <EM
->newer</EM
->
- version than 1.1.1.
- </P
-><P
-> In general, a "Version" in Bugzilla should refer to
- <EM
->released</EM
-> products, not products
- that have not yet been released to the public.
- Forthcoming products are what the Target Milestone
- field is for.
- </P
-><P
-></P
-></DIV
-></DIV
->
- </P
-><P
-> A "Component" is a piece of a Product.
- It may be a standalone program, or some other logical
- division of a Product or Program.
- Normally, a Component has a single Owner, who is responsible
- for overseeing efforts to improve that Component.
- <DIV
-CLASS="example"
-><A
-NAME="AEN317"><P
-><B
->Example 2-2. Mozilla's Bugzilla Components</B
-></P
-><DIV
-CLASS="informalexample"
-><A
-NAME="AEN319"><P
-></P
-><P
-> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
+> <EM
+>Product and Component</EM
+>:
+ Bugs are divided up by Product and Component, with a Product having one
+ or more Components in it. For example, bugzilla.mozilla.org's
+ "Bugzilla" Product is composed of several Components:
<P
></P
><TABLE
><EM
>Administration</EM
>,
- Administration of a bugzilla installation, including
- <TT
+ Administration of a bugzilla installation, including
+ <TT
CLASS="filename"
>editcomponents.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editgroups.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editkeywords.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editparams.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editproducts.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editusers.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>editversions.cgi,</TT
> and
- <TT
+ <TT
CLASS="filename"
>sanitycheck.cgi</TT
>.
- </TD
+ </TD
></TR
><TR
><TD
><EM
>Bugzilla-General</EM
>,
- Anything that doesn't fit in the other components, or spans
- multiple components.
- </TD
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </TD
></TR
><TR
><TD
><EM
>Creating/Changing Bugs</EM
>,
- Creating, changing, and viewing bugs.
- <TT
+ Creating, changing, and viewing bugs.
+ <TT
CLASS="filename"
>enter_bug.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>post_bug.cgi</TT
>,
- <TT
+ <TT
CLASS="filename"
>show_bug.cgi</TT
> and
- <TT
+ <TT
CLASS="filename"
>process_bug.cgi</TT
>.
- </TD
+ </TD
></TR
><TR
><TD
><EM
>Documentation</EM
>,
- The bugzilla documentation, including anything in the
- <TT
+ The bugzilla documentation, including anything in the
+ <TT
CLASS="filename"
>docs/</TT
> directory and The Bugzilla Guide
- (This document :)
- </TD
+
+ </TD
></TR
><TR
><TD
><EM
>Email</EM
>,
- Anything to do with email sent by Bugzilla.
- <TT
+ Anything to do with email sent by Bugzilla.
+ <TT
CLASS="filename"
>processmail</TT
>
- </TD
+ </TD
></TR
><TR
><TD
><EM
>Installation</EM
>,
- The installation process of Bugzilla. This includes
- <TT
+ The installation process of Bugzilla. This includes
+ <TT
CLASS="filename"
>checksetup.pl</TT
> and whatever else it evolves into.
- </TD
+ </TD
></TR
><TR
><TD
><EM
>Query/Buglist</EM
>,
- Anything to do with searching for bugs and viewing the buglists.
- <TT
+ Anything to do with searching for bugs and viewing the buglists.
+ <TT
CLASS="filename"
>query.cgi</TT
> and
- <TT
+ <TT
CLASS="filename"
>buglist.cgi</TT
>
- </TD
+ </TD
></TR
><TR
><TD
><EM
>Reporting/Charting</EM
>,
- Getting reports from Bugzilla.
- <TT
+ Getting reports from Bugzilla.
+ <TT
CLASS="filename"
>reports.cgi</TT
> and
- <TT
+ <TT
CLASS="filename"
>duplicates.cgi</TT
>
- </TD
+ </TD
></TR
><TR
><TD
><EM
>User Accounts</EM
>,
- Anything about managing a user account from the user's perspective.
- <TT
+ Anything about managing a user account from the user's perspective.
+ <TT
CLASS="filename"
>userprefs.cgi</TT
>, saved queries, creating accounts,
- changing passwords, logging in, etc.
- </TD
+ changing passwords, logging in, etc.
+ </TD
></TR
><TR
><TD
><EM
>User Interface</EM
>,
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates, etc.
- </TD
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </TD
></TR
></TBODY
></TABLE
></P
>
</P
+></LI
+><LI
><P
-></P
-></DIV
-></DIV
->
+> <EM
+>Status and Resolution</EM
+>:
+ A bug passes through several Statuses in its lifetime, and ends up in the
+ RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
+ The different possible
+ values for Status and Resolution on your installation will be documented
+ in the context-sensitive help for those items.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Assigned To</EM
+>:
+ The person responsible for fixing the bug.
</P
+></LI
+><LI
><P
-> A "Milestone", or "Target Milestone" is a often a planned
- future "Version" of a product. In many cases, though,
- Milestones simply represent significant dates for a
- developer. Having certain features in your Product is
- frequently tied to revenue (money) the developer will
- receive if the features work by the time she reaches the
- Target Milestone. Target Milestones are a great tool to
- organize your time. If someone will pay you $100,000 for
- incorporating certain features by a certain date, those
- features by that Milestone date become a very high
- priority. Milestones tend to be highly malleable
- creatures, though, that appear to be in reach but are out
- of reach by the time the important day arrives.
+> <EM
+>URL</EM
+>:
+ A URL associated with the bug, if any.
</P
+></LI
+><LI
><P
-> The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
- Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric combination, like "M19".
+> <EM
+>Summary</EM
+>:
+ A one-sentence summary of the problem.
</P
></LI
><LI
><P
-> OK, now let's select the "Bugzilla" component from its scrollbox.
+> <EM
+>Status Whiteboard</EM
+>: (a.k.a. Whiteboard) A
+ free-form text area for adding short notes and tags to a bug.
</P
></LI
><LI
><P
-> Skip down the page a bit -- do you see the "submit query" button?
- Select it, and let's run
- this query!
+> <EM
+>Keywords</EM
+>:
+ The administrator can define keywords which you can use to tag and
+ categorise bugs - e.g. The Mozilla Project has keywords like crash
+ and regression.
</P
></LI
><LI
><P
-> Congratulations! You've completed your first Query, and
- have before you the Bug List of the author of this Guide,
- Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
- well, you'll have a cryptic "Zarro Boogs Found" message on
- your screen. It is just a happy hacker's way of saying
- "Zero Bugs Found". However, I am fairly certain I will
- always have some bugs assigned to me that aren't done yet,
- so you won't often see that message!
+> <EM
+>Platform and OS</EM
+>:
+ These indicate the computing environment where the bug was found.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Version</EM
+>:
+ The "Version" field is usually used for versions of a product which have
+ been released, and is set to indicate which versions of a Component
+ have the particular problem the bug report is about.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Priority</EM
+>:
+ The bug assignee uses this field to prioritise his or her bugs. It's
+ a good idea not to change this on other people's bugs.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Severity</EM
+>:
+ This indicates how severe the problem is - from blocker ("application
+ unusable") to trivial ("minor cosmetic issue"). You can also use this
+ field to indicate whether a bug is an enhancement request.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Target</EM
+>:
+ (a.k.a. Target Milestone) A future version by which the bug is to be
+ fixed. e.g. The Bugzilla Project's milestones for future
+ Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
+ not restricted to numbers, thought - you can use any text strings,
+ such as dates.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Reporter</EM
+>:
+ The person who filed the bug.
+ </P
+></LI
+><LI
+><P
+> <EM
+>CC list</EM
+>:
+ A list of people who get mail when the bug changes.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Attachments</EM
+>:
+ You can attach files (e.g. testcases or patches) to bugs. If there are
+ any attachments, they are listed in this section.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Dependencies</EM
+>:
+ If this bug cannot be fixed unless other bugs are fixed (depends on), or
+ this bug stops other bugs being fixed (blocks), their numbers are
+ recorded here.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Votes</EM
+>:
+ Whether this bug has any votes.
+ </P
+></LI
+><LI
+><P
+> <EM
+>Additional Comments</EM
+>:
+ You can add your two cents to the bug discussion here, if you have
+ something worthwhile to say.
</P
></LI
></OL
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="query">2.3.3. Searching for Bugs</H2
+><P
+> The Bugzilla Search page is is the interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. You can play with it here:
+ <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
+TARGET="_top"
+> landfill.tequilarista.org/bugzilla-tip/query.cgi</A
+>.
+ </P
+><P
+> The Search page has controls for selecting different possible values
+ for all of the fields in a bug, as described above. Once you've defined
+ a search, you can either run it, or save it as a Remembered Query, which
+ can optionally appear in the footer of your pages.
+ </P
+><P
+> Highly advanced querying is done using Boolean Charts, which have their
+ own <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
+TARGET="_top"
+>context-sensitive help</A
+>.
+ </P
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="list">2.3.4. Bug Lists</H2
><P
-> I encourage you to click the bug numbers in the left-hand
- column and examine my bugs. Also notice that if you click the
- underlined links near the top of this page, they do not take
- you to context-sensitive help here, but instead sort the
- columns of bugs on the screen! When you need to sort your bugs
- by priority, severity, or the people they are assigned to,
- this is a tremendous timesaver.
+> If you run a search, a list of matching bugs will be returned.
+ The default search is to return all open bugs on the system -
+ don't try running this search on a Bugzilla installation with
+ a lot of bugs!
</P
><P
-> A couple more interesting things about the Bug List page:
+> The format of the list is configurable. For example, it can be
+ sorted by clicking the column headings. Other useful features
+ can be accessed using the links at the bottom of the list:
<P
></P
><TABLE
><TR
><TD
><EM
+>Long Format</EM
+>: this gives you a large page
+ with a non-editable summary of the fields of each bug.</TD
+></TR
+><TR
+><TD
+><EM
>Change Columns</EM
->: by selecting
- this link, you can show all kinds of information in the
- Bug List</TD
+>: change the bug
+ attributes which appear in the list.</TD
></TR
><TR
><TD
><EM
>Change several bugs at once</EM
>: If
- you have sufficient rights to change all the bugs shown in
- the Bug List, you can mass-modify them. This is a big
- time-saver.</TD
+ your account is sufficiently empowered, you can make the same
+ change to all the bugs in the list - for example, changing their
+ owner.</TD
></TR
><TR
><TD
><EM
>Send mail to bug owners</EM
->: If you
- have many related bugs, you can request an update from
- every person who owns the bugs in the Bug List asking them
- the status.</TD
+>: Sends mail
+ to the owners of all bugs on the list.</TD
></TR
><TR
><TD
></P
>
</P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> There are many more options to the Bugzilla Query Page and
- the Bug List than I have shown you. But this should be
- enough for you to learn to get around. I encourage you to
- check out the <A
-HREF="http://www.mozilla.org/bugs/"
-TARGET="_top"
->Bugzilla Home Page</A
-> to learn about the Anatomy and Life Cycle of a Bug before continuing.
- </P
-></TD
-></TR
-></TABLE
-></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="bugreports">2.3.3. Creating and Managing Bug Reports</H2
+NAME="bugreports">2.3.5. Filing Bugs</H2
><TABLE
BORDER="0"
WIDTH="100%"
></TD
></TR
></TABLE
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="bug-writing">2.3.3.1. Writing a Great Bug Report</H3
-><P
-> Before we plunge into writing your first bug report, I
- encourage you to read some bug-writing guidelines. If you
- are reading this document as part of a Bugzilla CVS checkout
- or un-tarred Bugzilla distribution, you should be able to
- read them by clicking <A
-HREF="../../bugwritinghelp.html"
-TARGET="_top"
->here</A
->. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A
-HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html"
-TARGET="_top"
->http://www.mozilla.org/quality/bug-writing-guidelines.html</A
->. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
- </P
><P
-> While you are at it, why not learn how to find previously
- reported bugs? Mozilla.org has published a great tutorial
- on finding duplicate bugs, available at <A
-HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
+> Years of bug writing experience has been distilled for your reading
+ pleasure into the <A
+HREF="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html"
TARGET="_top"
-> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
->.
+> Bug Writing Guidelines</A
+>.
+While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</P
><P
-> I realize this was a lot to read. However, understanding
- the mentality of writing great bug reports will help us on
- the next part!
- </P
+> The procedure for filing a test bug is as follows:
+ </P
><P
></P
><OL
TYPE="1"
><LI
><P
+> Go to <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
-> http://landfill.tequilarista.org/bugzilla-tip/</A
-> in your browser.
- </P
-></LI
-><LI
-><P
-> Select the <A
+>Landfill</A
+>
+ in your browser and click
+ <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
> Enter a new bug report</A
-> link.
- </P
-></LI
-><LI
-><P
-> Select a product.
- </P
-></LI
-><LI
-><P
-> Now you should be at the "Enter Bug" form. The
- "reporter" should have been automatically filled out for
- you (or else Bugzilla prompted you to Log In again --
- you did keep the email with your username and password,
- didn't you?).
+>.
</P
></LI
><LI
><P
-> Select a Component in the scrollbox.
+> Select a product - any one will do.
</P
></LI
><LI
><P
-> Bugzilla should have made reasonable guesses, based upon
+> Fill in the fields.
+ Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on
- an SGI box running IRIX, we want to know!
+ boxes. If they are wrong, change them.
</P
></LI
><LI
><P
-> Fill in the "Assigned To" box with the email address you
- provided earlier. This way you don't end up sending
- copies of your bug to lots of other people, since it's
- just a test bug.
- </P
-></LI
-><LI
-><P
-> Leave the "CC" text box blank. Fill in the "URL" box
- with "http://www.mozilla.org".
- </P
-></LI
-><LI
-><P
-> Enter "The Bugzilla Guide" in the Summary text box, and
- place any comments you have on this tutorial, or the
- Guide in general, into the Description box.
+> Select "Commit" and send in your bug report.
</P
></LI
></OL
-><P
-> Voila! Select "Commit" and send in your bug report! Next
- we'll look at resolving bugs.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H3
-CLASS="section"
-><A
-NAME="bug-manage">2.3.3.2. Managing your Bug Reports</H3
-><P
-> OK, you should have a link to the bug you just created near
- the top of your page. It should say "Bug XXXX posted", with
- a link to the right saying "Back to BUG# XXXX". Select this
- link.
- </P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Scroll down a bit on the subsequent page, until you see
- the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would "Accept bug (change status to
- ASSIGNED)", fix it, and then resolve. But in this case,
- we're going to short-circuit the process because this
- wasn't a real bug. Change the dropdown next to "Resolve
- Bug" to "INVALID", make sure the radio button is marked
- next to "Resolve Bug", then click "Commit".
- </P
-></LI
-><LI
-><P
-> Hey! It said it couldn't take the change in a big red
- box! That's right, you must specify a Comment in order
- to make this change. Select the "Back" button in your
- browser, add a Comment, then try Resolving the bug with
- INVALID status again. This time it should work.
- </P
-></LI
-></OL
-><P
-> You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance. I encourage you to
- explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from
- this point on, so you are on your own there.
- </P
-><P
-> But I'll give a few last hints!
- </P
-><P
-> There is a <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html"
-TARGET="_top"
->CLUE</A
-> on the Query page that will teach you more how to use the form.
- </P
-><P
-> If you click the hyperlink on the <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi"
-TARGET="_top"
->Component</A
-> box of the Query page, you will be presented a form that will describe what all the components are.
- </P
-><P
-> Possibly the most powerful feature of the Query page is the
- <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
-TARGET="_top"
->Boolean Chart</A
-> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
- </P
-><P
-> Finally, you can build some nifty <A
-HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi"
-TARGET="_top"
->Reports</A
-> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
- </P
-></DIV
></DIV
></DIV
><DIV
><H3
CLASS="author"
><A
-NAME="AEN27">Matthew P. Barnson</H3
+NAME="AEN5">Matthew P. Barnson</H3
><DIV
CLASS="affiliation"
><DIV
CLASS="address"
><P
CLASS="address"
->barnboy@trilobyte.net</P
+>mbarnson@sisna.com</P
></DIV
></DIV
-><SPAN
-CLASS="collab"
-><SPAN
-CLASS="collabname"
->Zach Lipton</SPAN
-><DIV
-CLASS="affiliation"
-><DIV
-CLASS="address"
-><P
-CLASS="address"
->zach AT zachlipton DOT com</P
-></DIV
-></DIV
-><BR></SPAN
-><P
-CLASS="pubdate"
->2001-04-25<BR></P
-><DIV
-CLASS="revhistory"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-><TR
-><TH
-ALIGN="LEFT"
-VALIGN="TOP"
-COLSPAN="3"
-><B
->Revision History</B
-></TH
-></TR
-><TR
-><TD
-ALIGN="LEFT"
->Revision v2.11</TD
-><TD
-ALIGN="LEFT"
->20 December 2000</TD
-><TD
-ALIGN="LEFT"
->Revised by: MPB</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-COLSPAN="3"
->Converted the README, FAQ, and DATABASE information into
- SGML docbook format.</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
->Revision 2.11.1</TD
-><TD
-ALIGN="LEFT"
->06 March 2001</TD
-><TD
-ALIGN="LEFT"
->Revised by: MPB</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-COLSPAN="3"
->Took way too long to revise this for 2.12 release. Updated
- FAQ to use qandaset tags instead of literallayout, cleaned
- up administration section, added User Guide section,
- miscellaneous FAQ updates and third-party integration
- information. From this point on all new tags are lowercase
- in preparation for the 2.13 release of the Guide in XML
- format instead of SGML.</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
->Revision 2.12.0</TD
-><TD
-ALIGN="LEFT"
->24 April 2001</TD
-><TD
-ALIGN="LEFT"
->Revised by: MPB</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-COLSPAN="3"
->Things fixed this release: Elaborated on queryhelp
- interface, added FAQ regarding moving bugs from one keyword
- to another, clarified possible problems with the Landfill
- tutorial, fixed a boatload of typos and unclear sentence
- structures. Incorporated the README into the UNIX
- installation section, and changed the README to indicate the
- deprecated status. Things I know need work: Used
- "simplelist" a lot, where I should have used "procedure" to
- tag things. Need to lowercase all tags to be XML compliant.</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
->Revision 2.14.0</TD
-><TD
-ALIGN="LEFT"
->07 August 2001</TD
-><TD
-ALIGN="LEFT"
->Revised by: MPB</TD
-></TR
-><TR
-><TD
-ALIGN="LEFT"
-COLSPAN="3"
->Attempted to integrate relevant portions of the UNIX and
- Windows installation instructions, moved some data from FAQ
- to Install, removed references to README from text, added
- Mac OS X install instructions, fixed a bunch
- of tpyos (Mark Harig), linked text that referenced other
- parts of the Guide, and nuked the old MySQL permissions
- section.</TD
-></TR
-></TABLE
-></DIV
><DIV
><DIV
CLASS="abstract"
><A
></P
><P
-> This is the documentation for Bugzilla, the Mozilla
+> This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
- </P
-><P
-> Bugzilla is an enterprise-class set of software utilities
- that, when used together, power issue-tracking for hundreds of
+ Bugzilla is an enterprise-class piece of software
+ that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
- While it is easy to use and quite flexible, it is
- difficult for a novice to install and maintain. Although we
- have provided step-by-step directions, Bugzilla is not always
- easy to get working. Please be sure the person responsible
- for installing and maintaining this software is a qualified
- professional for the operating system upon which you install
- Bugzilla.
</P
><P
-> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
- IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
- TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
- ADDITIONS TO THE GUIDE WRITTEN IN HTML!
+> This documentation is maintained in DocBook 4.1.2 XML format.
+ Changes are best submitted as plain text or SGML diffs, attached
+ to a Bugzilla bug.
</P
><P
></P
></DT
><DT
>1.6. <A
-HREF="contributors.html"
->Contributors</A
-></DT
-><DT
->1.7. <A
-HREF="feedback.html"
->Feedback</A
-></DT
-><DT
->1.8. <A
HREF="translations.html"
>Translations</A
></DT
><DT
HREF="conventions.html"
>Document Conventions</A
></DT
></DD
><DT
>6. <A
-HREF="future.html"
->The Future of Bugzilla</A
-></DT
-><DT
->7. <A
HREF="variants.html"
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
>List of Examples</B
></DT
><DT
->2-1. <A
-HREF="how.html#AEN307"
->Some Famous Software Versions</A
-></DT
-><DT
->2-2. <A
-HREF="how.html#AEN317"
->Mozilla's Bugzilla Components</A
-></DT
-><DT
>3-1. <A
-HREF="stepbystep.html#AEN709"
+HREF="stepbystep.html#AEN641"
>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
-HREF="stepbystep.html#AEN800"
+HREF="stepbystep.html#AEN732"
>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
-HREF="win32.html#AEN1051"
+HREF="win32.html#AEN985"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
-HREF="win32.html#AEN1064"
+HREF="win32.html#AEN998"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>3-5. <A
-HREF="win32.html#AEN1246"
+HREF="win32.html#AEN1180"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
-HREF="programadmin.html#AEN1483"
+HREF="programadmin.html#AEN1405"
>Creating some Components</A
></DT
><DT
>4-2. <A
-HREF="programadmin.html#AEN1512"
+HREF="programadmin.html#AEN1434"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
-HREF="programadmin.html#AEN1516"
+HREF="programadmin.html#AEN1438"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
-HREF="programadmin.html#AEN1544"
+HREF="programadmin.html#AEN1466"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
-HREF="programadmin.html#AEN1580"
+HREF="programadmin.html#AEN1502"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
-HREF="programadmin.html#AEN1597"
+HREF="programadmin.html#AEN1519"
>Creating a New Group</A
></DT
><DT
>4-7. <A
-HREF="programadmin.html#AEN1614"
+HREF="programadmin.html#AEN1536"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
-HREF="setperl.html#AEN2461"
+HREF="setperl.html#AEN2380"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
-HREF="glossary.html#AEN2782"
+HREF="glossary.html#AEN2701"
>A Sample Product</A
></DT
></DL
><DL
><DT
>3.2.1. <A
-HREF="stepbystep.html#AEN509"
+HREF="stepbystep.html#AEN441"
>Introduction</A
></DT
><DT
>3.2.2. <A
-HREF="stepbystep.html#AEN515"
+HREF="stepbystep.html#AEN447"
>Installing the Prerequisites</A
></DT
><DT
></DT
><DT
>3.2.5. <A
-HREF="stepbystep.html#AEN602"
+HREF="stepbystep.html#AEN534"
>DBI Perl Module</A
></DT
><DT
>3.2.6. <A
-HREF="stepbystep.html#AEN640"
+HREF="stepbystep.html#AEN572"
>Data::Dumper Perl Module</A
></DT
><DT
>3.2.7. <A
-HREF="stepbystep.html#AEN645"
+HREF="stepbystep.html#AEN577"
>MySQL related Perl Module Collection</A
></DT
><DT
>3.2.8. <A
-HREF="stepbystep.html#AEN654"
+HREF="stepbystep.html#AEN586"
>TimeDate Perl Module Collection</A
></DT
><DT
>3.2.9. <A
-HREF="stepbystep.html#AEN658"
+HREF="stepbystep.html#AEN590"
>GD Perl Module (1.8.3)</A
></DT
><DT
>3.2.10. <A
-HREF="stepbystep.html#AEN667"
+HREF="stepbystep.html#AEN599"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>3.2.11. <A
-HREF="stepbystep.html#AEN671"
+HREF="stepbystep.html#AEN603"
>DB_File Perl Module</A
></DT
><DT
>3.2.12. <A
-HREF="stepbystep.html#AEN674"
+HREF="stepbystep.html#AEN606"
>HTTP Server</A
></DT
><DT
>3.2.13. <A
-HREF="stepbystep.html#AEN693"
+HREF="stepbystep.html#AEN625"
>Installing the Bugzilla Files</A
></DT
><DT
>3.2.14. <A
-HREF="stepbystep.html#AEN722"
+HREF="stepbystep.html#AEN654"
>Setting Up the MySQL Database</A
></DT
><DT
>3.2.15. <A
-HREF="stepbystep.html#AEN769"
+HREF="stepbystep.html#AEN701"
>Tweaking <TT
CLASS="filename"
>localconfig</TT
></DT
><DT
>3.2.16. <A
-HREF="stepbystep.html#AEN807"
+HREF="stepbystep.html#AEN739"
>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
>3.2.17. <A
-HREF="stepbystep.html#AEN818"
+HREF="stepbystep.html#AEN750"
>The Whining Cron (Optional)</A
></DT
><DT
>3.2.18. <A
-HREF="stepbystep.html#AEN828"
+HREF="stepbystep.html#AEN760"
>Bug Graphs (Optional)</A
></DT
><DT
>3.2.19. <A
-HREF="stepbystep.html#AEN840"
+HREF="stepbystep.html#AEN772"
>Securing MySQL</A
></DT
></DL
><DL
><DT
>3.5.1. <A
-HREF="geninstall.html#AEN942"
+HREF="geninstall.html#AEN874"
>Modifying Your Running System</A
></DT
><DT
>3.5.2. <A
-HREF="geninstall.html#AEN949"
+HREF="geninstall.html#AEN881"
>Upgrading From Previous Versions</A
></DT
><DT
><A
NAME="newversions">1.4. New Versions</H1
><P
-> This is the 2.14 version of The Bugzilla Guide. If you are
+> This is the 2.16 version of The Bugzilla Guide. If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
><LI
><P
> <A
-HREF="http://www.trilobyte.net/barnsons/"
+HREF="http://www.bugzilla.org/"
TARGET="_top"
->TriloBYTE</A
->
- </P
-></LI
-><LI
-><P
-> <A
-HREF="http://www.mozilla.org/projects/bugzilla/"
-TARGET="_top"
->Mozilla.org</A
+>bugzilla.org</A
>
</P
></LI
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>the Mozilla CVS page</A
->, and check out the mozilla/webtools/bugzilla/docs/ branch.
+>, and check out the <TT
+CLASS="filename"
+>mozilla/webtools/bugzilla/docs/</TT
+> branch.
</P
></DIV
><DIV
><DL
><DT
>D.5.1. <A
-HREF="bzhacking.html#AEN2517"
+HREF="bzhacking.html#AEN2436"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
-HREF="bzhacking.html#AEN2531"
+HREF="bzhacking.html#AEN2450"
>Coding Style for Bugzilla</A
></DT
></DL
<DIV
CLASS="example"
><A
><B
>Example 4-1. Creating some Components</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> The computer game you are designing may have a "UI"
<DIV
CLASS="example"
><A
><B
>Example 4-2. Common Use of Versions</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> A user reports a bug against Version "Beta 2.0" of your
<DIV
CLASS="example"
><A
><B
>Example 4-3. A Different Use of Versions</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> This field has been used to good effect by an online
><DIV
CLASS="example"
><A
><B
>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> Let's say you create a target milestone called
<DIV
CLASS="example"
><A
><B
>Example 4-5. When to Use Group Security</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> Many Bugzilla sites isolate "Security-related" bugs from
<DIV
CLASS="example"
><A
><B
>Example 4-6. Creating a New Group</B
></P
><DIV
CLASS="informalexample"
><A
></P
><P
> I created a group called DefaultGroup with a
<DIV
CLASS="example"
><A
><B
>Example 4-7. Bugzilla Groups</B
></P
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="rhbugzilla">7.1. Red Hat Bugzilla</H1
+NAME="rhbugzilla">6.1. Red Hat Bugzilla</H1
><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
></TABLE
></DIV
><P
+> When you run checksetup.pl, the script will attempt to modify various
+ permissions on files which Bugzilla uses. If you do not have a
+ webservergroup set in the localconfig file, then Bugzilla will have to
+ make certain files world readable and/or writable. <EM
+>THIS IS
+ INSECURE!</EM
+>. This means that anyone who can get access to
+ your system can do whatever they want to your Bugzilla installation.
+ </P
+><DIV
+CLASS="note"
+><P
+></P
+><TABLE
+CLASS="note"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This also means that if your webserver runs all cgi scripts as the
+ same user/group, anyone on the system who can run cgi scripts will
+ be able to take control of your Bugzilla installation.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
> On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
<DIV
CLASS="example"
><A
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><H2
CLASS="section"
><A
-NAME="AEN509">3.2.1. Introduction</H2
+NAME="AEN441">3.2.1. Introduction</H2
><P
> Installation of bugzilla is pretty straightforward, particularly if your
machine already has MySQL and the MySQL-related perl packages installed.
><H2
CLASS="section"
><A
-NAME="AEN515">3.2.2. Installing the Prerequisites</H2
+NAME="AEN447">3.2.2. Installing the Prerequisites</H2
><DIV
CLASS="note"
><P
><H2
CLASS="section"
><A
-NAME="AEN602">3.2.5. DBI Perl Module</H2
+NAME="AEN534">3.2.5. DBI Perl Module</H2
><P
> The DBI module is a generic Perl module used by other database related
Perl modules. For our purposes it's required by the MySQL-related
<DIV
CLASS="informalexample"
><A
></P
><P
> <TT
<DIV
CLASS="informalexample"
><A
></P
><P
> Untar the module tarball -- it should create its own directory
><H2
CLASS="section"
><A
-NAME="AEN640">3.2.6. Data::Dumper Perl Module</H2
+NAME="AEN572">3.2.6. Data::Dumper Perl Module</H2
><P
> The Data::Dumper module provides data structure persistence for Perl
(similar to Java's serialization). It comes with later sub-releases of
><H2
CLASS="section"
><A
-NAME="AEN645">3.2.7. MySQL related Perl Module Collection</H2
+NAME="AEN577">3.2.7. MySQL related Perl Module Collection</H2
><P
> The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
><H2
CLASS="section"
><A
-NAME="AEN654">3.2.8. TimeDate Perl Module Collection</H2
+NAME="AEN586">3.2.8. TimeDate Perl Module Collection</H2
><P
> Many of the more common date/time/calendar related Perl
modules have been grouped into a bundle similar to the MySQL
><H2
CLASS="section"
><A
-NAME="AEN658">3.2.9. GD Perl Module (1.8.3)</H2
+NAME="AEN590">3.2.9. GD Perl Module (1.8.3)</H2
><P
> The GD library was written by Thomas Boutell a long while
ago to programatically generate images in C. Since then it's
><H2
CLASS="section"
><A
-NAME="AEN667">3.2.10. Chart::Base Perl Module (0.99c)</H2
+NAME="AEN599">3.2.10. Chart::Base Perl Module (0.99c)</H2
><P
> The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it
><H2
CLASS="section"
><A
-NAME="AEN671">3.2.11. DB_File Perl Module</H2
+NAME="AEN603">3.2.11. DB_File Perl Module</H2
><P
> DB_File is a module which allows Perl programs to make use
of the facilities provided by Berkeley DB version 1.x. This
><H2
CLASS="section"
><A
-NAME="AEN674">3.2.12. HTTP Server</H2
+NAME="AEN606">3.2.12. HTTP Server</H2
><P
> You have a freedom of choice here - Apache, Netscape or any
other server on UNIX would do. You can easily run the web
><H2
CLASS="section"
><A
-NAME="AEN693">3.2.13. Installing the Bugzilla Files</H2
+NAME="AEN625">3.2.13. Installing the Bugzilla Files</H2
><P
> You should untar the Bugzilla files into a directory that
you're willing to make writable by the default web server user
<DIV
CLASS="example"
><A
><B
>Example 3-1. Setting up bonsaitools symlink</B
></P
COLOR="#000000"
><PRE
CLASS="programlisting"
-> perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb
+> perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
+processmail syncshadowdb
</PRE
></FONT
></TD
><H2
CLASS="section"
><A
-NAME="AEN722">3.2.14. Setting Up the MySQL Database</H2
+NAME="AEN654">3.2.14. Setting Up the MySQL Database</H2
><P
> After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high
><H2
CLASS="section"
><A
-NAME="AEN769">3.2.15. Tweaking <TT
+NAME="AEN701">3.2.15. Tweaking <TT
CLASS="filename"
>localconfig</TT
></H2
<DIV
CLASS="example"
><A
><B
>Example 3-2. Running checksetup.pl as the web user</B
></P
><H2
CLASS="section"
><A
-NAME="AEN807">3.2.16. Setting Up Maintainers Manually (Optional)</H2
+NAME="AEN739">3.2.16. Setting Up Maintainers Manually (Optional)</H2
><P
> If you want to add someone else to every group by hand, you
can do it by typing the appropriate MySQL commands. Run
><H2
CLASS="section"
><A
-NAME="AEN818">3.2.17. The Whining Cron (Optional)</H2
+NAME="AEN750">3.2.17. The Whining Cron (Optional)</H2
><P
> By now you have a fully functional bugzilla, but what good
are bugs if they're not annoying? To help make those bugs
><H2
CLASS="section"
><A
-NAME="AEN828">3.2.18. Bug Graphs (Optional)</H2
+NAME="AEN760">3.2.18. Bug Graphs (Optional)</H2
><P
> As long as you installed the GD and Graph::Base Perl modules
you might as well turn on the nifty bugzilla bug reporting
><H2
CLASS="section"
><A
-NAME="AEN840">3.2.19. Securing MySQL</H2
+NAME="AEN772">3.2.19. Securing MySQL</H2
><P
> If you followed the installation instructions for setting up
your "bugs" and "root" user in MySQL, much of this should not
TITLE="Perforce SCM"
HREF="scm.html"><LINK
REL="NEXT"
-TITLE="The Future of Bugzilla"
-HREF="future.html"></HEAD
+TITLE="Bugzilla Variants and Competitors"
+HREF="variants.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="future.html"
+HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
ALIGN="right"
VALIGN="top"
><A
-HREF="future.html"
+HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->The Future of Bugzilla</TD
+>Bugzilla Variants and Competitors</TD
></TR
></TABLE
></DIV
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
-TITLE="Feedback"
-HREF="feedback.html"><LINK
+TITLE="Credits"
+HREF="credits.html"><LINK
REL="NEXT"
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
ALIGN="left"
VALIGN="bottom"
><A
-HREF="feedback.html"
+HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
><H1
CLASS="section"
><A
-NAME="translations">1.8. Translations</H1
+NAME="translations">1.6. Translations</H1
><P
> The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will
>mozilla-webtools@mozilla.org</A
>></TT
>, and arrange with
- Matt Barnson to check it into CVS.
+ The Bugzilla Team to check it into CVS.
</P
></DIV
><DIV
ALIGN="left"
VALIGN="top"
><A
-HREF="feedback.html"
+HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Feedback</TD
+>Credits</TD
><TD
WIDTH="34%"
ALIGN="center"
><LI
><P
> <EM
->Email Notification</EM
->: You may choose
- from one of three options:
- <P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> All qualifying bugs except those which I change:
- The user will be notified of any change to any bug
- for which she is the reporter, assignee, QA
- Contact, CC recipient, or "watcher".
- </P
-></LI
-><LI
-><P
-> Only those bugs which I am listed on the CC line:
- The user will not be notified of changes to bugs
- where she is the assignee, reporter, or QA
- Contact, but will receive them if she is on the CC
- list.
- <DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> She will still receive whining cron emails if
- you set up the "whinemail" feature.
- </P
-></TD
-></TR
-></TABLE
-></DIV
->
- </P
-></LI
-><LI
-><P
-> <EM
->All Qualifying Bugs</EM
->: This
- user is a glutton for punishment. If her name is
- in the reporter, QA Contact, CC, assignee, or is a
- "watcher", she will get email updates regarding
- the bug.
- </P
-></LI
-></OL
->
-</P
-><P
-> <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
></DT
><DT
>2.3.2. <A
-HREF="how.html#query"
->The Bugzilla Query Page</A
+HREF="how.html#bug_page"
+>Anatomy of a Bug</A
></DT
><DT
>2.3.3. <A
+HREF="how.html#query"
+>Searching for Bugs</A
+></DT
+><DT
+>2.3.4. <A
+HREF="how.html#list"
+>Bug Lists</A
+></DT
+><DT
+>2.3.5. <A
HREF="how.html#bugreports"
->Creating and Managing Bug Reports</A
+>Filing Bugs</A
></DT
></DL
></DD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="variant-fenris">7.2. Loki Bugzilla (Fenris)</H1
+NAME="variant-fenris">6.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris can be found at <A
HREF="http://fenris.lokigames.com/"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="variant-issuezilla">7.3. Issuezilla</H1
+NAME="variant-issuezilla">6.3. Issuezilla</H1
><P
>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="variant-perforce">7.5. Perforce SCM</H1
+NAME="variant-perforce">6.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="variant-scarab">7.4. Scarab</H1
+NAME="variant-scarab">6.4. Scarab</H1
><P
>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
->Chapter 7. Bugzilla Variants and Competitors</TD
+>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
><H1
CLASS="section"
><A
-NAME="variant-sourceforge">7.6. SourceForge</H1
+NAME="variant-sourceforge">6.6. SourceForge</H1
><P
>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="The Future of Bugzilla"
-HREF="future.html"><LINK
+TITLE="Tinderbox/Tinderbox2"
+HREF="tinderbox.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
ALIGN="left"
VALIGN="bottom"
><A
-HREF="future.html"
+HREF="tinderbox.html"
ACCESSKEY="P"
>Prev</A
></TD
CLASS="chapter"
><H1
><A
-NAME="variants">Chapter 7. Bugzilla Variants and Competitors</H1
+NAME="variants">Chapter 6. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
>Table of Contents</B
></DT
><DT
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
ALIGN="left"
VALIGN="top"
><A
-HREF="future.html"
+HREF="tinderbox.html"
ACCESSKEY="P"
>Prev</A
></TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->The Future of Bugzilla</TD
+>Tinderbox/Tinderbox2</TD
><TD
WIDTH="34%"
ALIGN="center"
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
originally written by Terry Weissman in a programming language called
-"TCL", to replace a crappy bug-tracking database used internally for
+"TCL", to replace a crappy bug-tracking database used internally by
Netscape Communications. Terry later ported Bugzilla to Perl from
TCL, and in Perl it remains to this day. Most commercial
defect-tracking software vendors at the time charged enormous
><UL
><LI
><P
-> integrated, product-based granular security schema
- </P
+>Powerful searching</P
></LI
><LI
><P
-> inter-bug dependencies and dependency graphing
- </P
+>User-configurable email notifications of bug changes</P
></LI
><LI
><P
-> advanced reporting capabilities
- </P
+>Full change history</P
></LI
><LI
><P
-> a robust, stable RDBMS back-end
- </P
+>Inter-bug dependency tracking and graphing</P
></LI
><LI
><P
-> extensive configurability
- </P
+>Excellent attachment management</P
></LI
><LI
><P
-> a very well-understood and well-thought-out natural bug resolution protocol
- </P
+>Integrated, product-based, granular security schema</P
></LI
><LI
><P
-> email, XML, console, and HTTP APIs
- </P
+>Fully security-audited, and runs under Perl's taint mode</P
></LI
><LI
><P
-> available integration with automated software
- configuration management systems, including Perforce and
- CVS (through the Bugzilla email interface and
- checkin/checkout scripts)
- </P
+>A robust, stable RDBMS back-end</P
></LI
><LI
><P
-> too many more features to list
- </P
+>Web, XML, email and console interfaces</P
></LI
-></UL
->
- </P
+><LI
><P
-> Despite its current robustness and popularity, Bugzilla faces
- some near-term challenges, such as reliance on a single
- database, a lack of abstraction of the user interface and
- program logic, verbose email bug notifications, a powerful but
- daunting query interface, little reporting configurability,
- problems with extremely large queries, some unsupportable bug
- resolution options, little internationalization (although non-US
- character sets are accepted for comments), and dependence on
- some nonstandard libraries.
- </P
+>Completely customisable and/or localisable web user interface</P
+></LI
+><LI
><P
-> Some recent headway has been made on the query front, however.
- If you are using the latest version of Bugzilla, you should see
- a <SPAN
-CLASS="QUOTE"
->"simple search"</SPAN
-> form on the default front page of
- your Bugzilla install. Type in two or three search terms and
- you should pull up some relevant information. This is also
- available as "queryhelp.cgi".
- </P
+>Extensive configurability</P
+></LI
+><LI
><P
-> Despite these small problems, Bugzilla is very hard to beat. It
- is under <EM
->very</EM
-> active development to address
- the current issues, and continually gains new features.
+>Smooth upgrade pathway between versions</P
+></LI
+></UL
+>
</P
></DIV
><DIV
><DIV
CLASS="example"
><A
><B
>Example 3-3. Installing ActivePerl ppd Modules on Microsoft Windows</B
></P
<DIV
CLASS="example"
><A
><B
>Example 3-4. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
><P
> From Andrew Pearson:
<A
-NAME="AEN1
234"><BLOCKQUOTE
+NAME="AEN1
168"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> You can make Bugzilla work with Personal Web Server for
>not necessary</EM
> for Bugzilla 2.13 and
later, which includes the current release, Bugzilla
- 2.14.
+ 2.16.
<DIV
CLASS="example"
><A
><B
>Example 3-5. Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</B
make certain files world readable and/or writable. <emphasis>THIS IS
INSECURE!</emphasis>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
- <note>
+ </para>
+ <note>
+ <para>
This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
- </note>
- </para>
+ </para>
+ </note>
<para>
On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ulink> for the localconfig file, and <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"> Bug 65572</ulink> for adequate protection in your data/ and shadow/ directories.
<row>
<entry>Warnings</entry>
<entry><caution>
- <para>Warnings.</para>
+ <para>Don't run with scissors!</para>
</caution></entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
- <para>Hint.</para>
+ <para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
- <para>Note.</para>
+ <para>Dear John...</para>
</note></entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
- <para>Warning.</para>
+ <para>Read this or the cat gets it.</para>
</warning></entry>
</row>
<row>
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
<itemizedlist>
- <listitem>
- <para>
- integrated, product-based granular security schema
- </para>
- </listitem>
- <listitem>
- <para>
- inter-bug dependencies and dependency graphing
- </para>
- </listitem>
- <listitem>
- <para>
- advanced reporting capabilities
- </para>
- </listitem>
- <listitem>
- <para>
- a robust, stable RDBMS back-end
- </para>
- </listitem>
- <listitem>
- <para>
- extensive configurability
- </para>
- </listitem>
- <listitem>
- <para>
- a very well-understood and well-thought-out natural bug resolution protocol
- </para>
- </listitem>
- <listitem>
- <para>
- email, XML, console, and web interfaces
- </para>
- </listitem>
- <listitem>
- <para>
- available integration with automated software
- configuration management systems, including Perforce and
- CVS (through the Bugzilla email interface and
- checkin/checkout scripts)
- </para>
- </listitem>
- <listitem>
- <para>
- too many more features to list
- </para>
- </listitem>
+
+<listitem><para>Powerful searching</para></listitem>
+<listitem><para>User-configurable email notifications of bug changes</para></listitem>
+<listitem><para>Full change history</para></listitem>
+<listitem><para>Inter-bug dependency tracking and graphing</para></listitem>
+<listitem><para>Excellent attachment management</para></listitem>
+<listitem><para>Integrated, product-based, granular security schema</para></listitem>
+<listitem><para>Fully security-audited, and runs under Perl's taint mode</para></listitem>
+<listitem><para>A robust, stable RDBMS back-end</para></listitem>
+<listitem><para>Web, XML, email and console interfaces</para></listitem>
+<listitem><para>Completely customisable and/or localisable web user interface</para></listitem>
+<listitem><para>Extensive configurability</para></listitem>
+<listitem><para>Smooth upgrade pathway between versions</para></listitem>
+
</itemizedlist>
</para>
</section>
</epigraph>
<para>
- Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or
- administering a Bugzilla installation, please consult the
+ This section contains information for end-users of Bugzilla.
+ If you are administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
- This section is principally aimed towards developing end-user
- mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking
- software.
</para>
<para>
- Throughout this portion of the Guide, we will refer to user
- account options available at the Bugzilla test installation,
+ There is a Bugzilla test installation, called
<ulink url="http://landfill.tequilarista.org/">
- landfill.tequilarista.org</ulink>.
- Although Landfill serves as a great introduction to
- Bugzilla, it does not offer all the options you would have as a
- user on your own installation of Bugzilla, nor can it do more
- than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for
+ Landfill</ulink>, which you are welcome to play with.
+ However, it does not necessarily have all Bugzilla features
+ enabled, and often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</para>
If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
- should use to access it. If you're test-driving the end-user
-
Bugzilla experience, use this URL: <ulink
+ should use to access it. If you're test-driving Bugzilla,
+ use this URL: <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
<para>
- Click the "Open a new Bugzilla account" link.
- </para>
- </listitem>
- <listitem>
- <para>
- Enter your "E-mail address" and "Real Name" (or whatever
- name you want to call yourself) in the spaces provided,
- then select the "Create Account" button.
+ Click the <quote>Open a new Bugzilla account</quote> link, enter your
+ email address and, optionally, your name in the spaces provided,
+ then click <quote>Create Account</quote>.
</para>
</listitem>
<listitem>
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
- randomly generated, and should be changed at your nearest
- opportunity (we'll go into how to do it later).
+ randomly generated, and can be changed to something more memorable.
</para>
</listitem>
<listitem>
<para>
Click the <quote>Log In</quote> link in the yellow area at
- the bottom of the page in your browser, then enter your
- <quote>E-mail address</quote> and <quote>Password</quote>
- you just received into the spaces provided, and select
+ the bottom of the page in your browser, enter your
+ email address and password into the spaces provided, and click
<quote>Login</quote>.
- <note>
- <para>
- If you ever forget your password, you can come back to
- this page, enter your <quote>E-mail address</quote>,
- then select the <quote>E-mail me a password</quote>
- button to have your password mailed to you again so
- that you can login.
- </para>
- </note>
</para>
</listitem>
</orderedlist>
<para>
- Congratulations! If you followed these directions, you now
- are the proud owner of a user account on
- landfill.tequilarista.org (Landfill) or your local Bugzilla
- install. You should now see in your browser a page called the
- <quote>Bugzilla Query Page</quote>. It may look daunting, but with this
- Guide to walk you through it, you will master it in no time.
+ You are now logged in. Bugzilla uses cookies for authentication, so
+ (unless your IP address changes) you should not have to log in again.
</para>
</section>
- <section id="query">
- <title>The Bugzilla Query Page</title>
- <para>
- The Bugzilla Query Page is the heart and soul of the Bugzilla
- user experience. It is the master interface where you can
- find any bug report, comment, or patch currently in the
- Bugzilla system. We'll go into how to create your own bug
- report later on.
- </para>
- <para>
- At this point, let's visit the query page.
- <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
- landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>
- </para>
- <para>
- The first thing you need to notice about the Bugzilla Query
- Page is that nearly every box you see on your screen has a
- hyperlink nearby, explaining what it is or what it does. Near
- the upper-left-hand corner of your browser window you should
- see the word <quote>Status</quote> underlined. Select it.
- </para>
+ <section id="bug_page">
+ <title>Anatomy of a Bug</title>
<para>
- Notice the page that popped up? Every underlined word you see
- on your screen is a hyperlink that will take you to
- context-sensitive help. Click around for a while, and learn
- what everything here does. To return to the query interface
- after pulling up a help page, use the <quote>Back</quote>
- button in your browser.
+ The core of Bugzilla is the screen which displays a particular bug.
+ It's a good place to explain some Bugzilla concepts.
+ <ulink url="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">Bug 1 on Landfill</ulink> is a good example. Note that the names of most fields
+ are hyperlinks; clicking them will take you to context-sensitive
+ help on that particular field.
</para>
- <para>
- I'm sure that after checking out the online help, you are now
- an expert on the Bugzilla Query Page. If, however, you feel
- you haven't mastered it yet, let me walk you through making a
- few successful queries to find out what there are in the
- Bugzilla bug-tracking system itself.
- </para>
- <orderedlist>
- <listitem>
+
+ <orderedlist>
+ <listitem>
+ <para>
+ <emphasis>Product and Component</emphasis>:
+ Bugs are divided up by Product and Component, with a Product having one
+ or more Components in it. For example, bugzilla.mozilla.org's
+ "Bugzilla" Product is composed of several Components:
+ <simplelist>
+ <member><emphasis>Administration</emphasis>,
+ Administration of a bugzilla installation, including
+ <filename>editcomponents.cgi</filename>,
+ <filename>editgroups.cgi</filename>,
+ <filename>editkeywords.cgi</filename>,
+ <filename>editparams.cgi</filename>,
+ <filename>editproducts.cgi</filename>,
+ <filename>editusers.cgi</filename>,
+ <filename>editversions.cgi,</filename> and
+ <filename>sanitycheck.cgi</filename>.
+ </member>
+ <member><emphasis>Bugzilla-General</emphasis>,
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </member>
+ <member><emphasis>Creating/Changing Bugs</emphasis>,
+ Creating, changing, and viewing bugs.
+ <filename>enter_bug.cgi</filename>,
+ <filename>post_bug.cgi</filename>,
+ <filename>show_bug.cgi</filename> and
+ <filename>process_bug.cgi</filename>.
+ </member>
+ <member><emphasis>Documentation</emphasis>,
+ The bugzilla documentation, including anything in the
+ <filename>docs/</filename> directory and The Bugzilla Guide
+
+ </member>
+ <member><emphasis>Email</emphasis>,
+ Anything to do with email sent by Bugzilla.
+ <filename>processmail</filename>
+ </member>
+ <member><emphasis>Installation</emphasis>,
+ The installation process of Bugzilla. This includes
+ <filename>checksetup.pl</filename> and whatever else it evolves into.
+ </member>
+ <member><emphasis>Query/Buglist</emphasis>,
+ Anything to do with searching for bugs and viewing the buglists.
+ <filename>query.cgi</filename> and
+ <filename>buglist.cgi</filename>
+ </member>
+ <member><emphasis>Reporting/Charting</emphasis>,
+ Getting reports from Bugzilla.
+ <filename>reports.cgi</filename> and
+ <filename>duplicates.cgi</filename>
+ </member>
+ <member><emphasis>User Accounts</emphasis>,
+ Anything about managing a user account from the user's perspective.
+ <filename>userprefs.cgi</filename>, saved queries, creating accounts,
+ changing passwords, logging in, etc.
+ </member>
+ <member><emphasis>User Interface</emphasis>,
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </member>
+ </simplelist>
+ </para>
+ </listitem>
+
+ <listitem>
<para>
- Ensure you are back on the <quote>Bugzilla Query
- Page</quote>. Do nothing in the boxes marked "Status",
- "Resolution", "Platform", "OpSys", "Priority", or
- "Severity". The default query for "Status" is to find all
- bugs that are NEW, ASSIGNED, or REOPENED, which is what we
- want. If you don't select anything in the other 5
- scrollboxes there, then you are saying that "any of these
- are OK"; we're not locking ourselves into only finding
- bugs on the "DEC" Platform, or "Windows 95" OpSys
- (Operating System). You're smart, I think you have it
- figured out.
+ <emphasis>Status and Resolution</emphasis>:
+ A bug passes through several Statuses in its lifetime, and ends up in the
+ RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
+ The different possible
+ values for Status and Resolution on your installation will be documented
+ in the context-sensitive help for those items.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Assigned To</emphasis>:
+ The person responsible for fixing the bug.
</para>
+ </listitem>
+
+ <listitem>
<para>
- Basically, selecting <emphasis>anything</emphasis> on the
- query page narrows your search down. Leaving stuff
- unselected, or text boxes unfilled, broadens your search.
+ <emphasis>URL</emphasis>:
+ A URL associated with the bug, if any.
</para>
- </listitem>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- You see the box immediately below the top six boxes that
- contains an "Email" text box, with the words "matching
- as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to
- filter your search down based upon email address. Let's
- put my email address in there, and see what happens.
+ <emphasis>Summary</emphasis>:
+ A one-sentence summary of the problem.
</para>
+ </listitem>
+
+ <listitem>
<para>
- Type "barnboy@trilobyte.net" in the top Email text box.
+ <emphasis>Status Whiteboard</emphasis>: (a.k.a. Whiteboard) A
+ free-form text area for adding short notes and tags to a bug.
</para>
- </listitem>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Keywords</emphasis>:
+ The administrator can define keywords which you can use to tag and
+ categorise bugs - e.g. The Mozilla Project has keywords like crash
+ and regression.
+ </para>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- Let's narrow the search some more. Scroll down until you
- find the box with the word "Program" over the top of it.
- This is where we can narrow our search down to only
- specific products (software programs or product lines) in
- our Bugzilla database. Please notice the box is a
- <emphasis>scrollbox</emphasis>. Using the down arrow on
- the scrollbox, scroll down until you can see an entry
- called "Bugzilla". Select this entry.
+ <emphasis>Platform and OS</emphasis>:
+ These indicate the computing environment where the bug was found.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Did you notice that some of the boxes to the right changed
- when you selected "Bugzilla"? Every Program (or Product)
- has different Versions, Components, and Target Milestones
- associated with it. A "Version" is the number of a
- software program.
- <example>
- <title>Some Famous Software Versions</title>
- <informalexample>
- <para>
- Do you remember the hype in 1995 when Microsoft
- Windows 95(r) was released? It may have been several
- years ago, but Microsoft(tm) spent over $300 Million
- advertising this new Version of their software.
- Three years later, they released Microsoft Windows
- 98(r), another new version, to great fanfare, and
- then in 2000 quietly released Microsoft Windows
- ME(Millenium Edition)(r).
- </para>
- <para>
- Software "Versions" help a manufacturer
- differentiate their current product from their
- previous products. Most do not identify their
- products by the year they were released. Instead,
- the "original" version of their software will often
- be numbered "1.0", with small bug-fix releases on
- subsequent tenths of a digit. In most cases, it's
- not a decimal number; for instance, often 1.9 is an
- <emphasis>older</emphasis> version of the software
- than 1.11, but is a <emphasis>newer</emphasis>
- version than 1.1.1.
- </para>
- <para>
- In general, a "Version" in Bugzilla should refer to
- <emphasis>released</emphasis> products, not products
- that have not yet been released to the public.
- Forthcoming products are what the Target Milestone
- field is for.
- </para>
- </informalexample>
- </example>
+ <emphasis>Version</emphasis>:
+ The "Version" field is usually used for versions of a product which have
+ been released, and is set to indicate which versions of a Component
+ have the particular problem the bug report is about.
</para>
+ </listitem>
+
+ <listitem>
<para>
- A "Component" is a piece of a Product.
- It may be a standalone program, or some other logical
- division of a Product or Program.
- Normally, a Component has a single Owner, who is responsible
- for overseeing efforts to improve that Component.
- <example>
- <title>Mozilla's Bugzilla Components</title>
- <informalexample>
- <para>
- Mozilla's "Bugzilla" Product is composed of several pieces (Components):
- <simplelist>
- <member><emphasis>Administration</emphasis>,
- Administration of a bugzilla installation, including
- <filename>editcomponents.cgi</filename>,
- <filename>editgroups.cgi</filename>,
- <filename>editkeywords.cgi</filename>,
- <filename>editparams.cgi</filename>,
- <filename>editproducts.cgi</filename>,
- <filename>editusers.cgi</filename>,
- <filename>editversions.cgi,</filename> and
- <filename>sanitycheck.cgi</filename>.
- </member>
- <member><emphasis>Bugzilla-General</emphasis>,
- Anything that doesn't fit in the other components, or spans
- multiple components.
- </member>
- <member><emphasis>Creating/Changing Bugs</emphasis>,
- Creating, changing, and viewing bugs.
- <filename>enter_bug.cgi</filename>,
- <filename>post_bug.cgi</filename>,
- <filename>show_bug.cgi</filename> and
- <filename>process_bug.cgi</filename>.
- </member>
- <member><emphasis>Documentation</emphasis>,
- The bugzilla documentation, including anything in the
- <filename>docs/</filename> directory and The Bugzilla Guide
- (This document :)
- </member>
- <member><emphasis>Email</emphasis>,
- Anything to do with email sent by Bugzilla.
- <filename>processmail</filename>
- </member>
- <member><emphasis>Installation</emphasis>,
- The installation process of Bugzilla. This includes
- <filename>checksetup.pl</filename> and whatever else it evolves into.
- </member>
- <member><emphasis>Query/Buglist</emphasis>,
- Anything to do with searching for bugs and viewing the buglists.
- <filename>query.cgi</filename> and
- <filename>buglist.cgi</filename>
- </member>
- <member><emphasis>Reporting/Charting</emphasis>,
- Getting reports from Bugzilla.
- <filename>reports.cgi</filename> and
- <filename>duplicates.cgi</filename>
- </member>
- <member><emphasis>User Accounts</emphasis>,
- Anything about managing a user account from the user's perspective.
- <filename>userprefs.cgi</filename>, saved queries, creating accounts,
- changing passwords, logging in, etc.
- </member>
- <member><emphasis>User Interface</emphasis>,
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates, etc.
- </member>
- </simplelist>
- </para>
- </informalexample>
- </example>
+ <emphasis>Priority</emphasis>:
+ The bug assignee uses this field to prioritise his or her bugs. It's
+ a good idea not to change this on other people's bugs.
</para>
+ </listitem>
+
+ <listitem>
<para>
- A "Milestone", or "Target Milestone" is a often a planned
- future "Version" of a product. In many cases, though,
- Milestones simply represent significant dates for a
- developer. Having certain features in your Product is
- frequently tied to revenue (money) the developer will
- receive if the features work by the time she reaches the
- Target Milestone. Target Milestones are a great tool to
- organize your time. If someone will pay you $100,000 for
- incorporating certain features by a certain date, those
- features by that Milestone date become a very high
- priority. Milestones tend to be highly malleable
- creatures, though, that appear to be in reach but are out
- of reach by the time the important day arrives.
+ <emphasis>Severity</emphasis>:
+ This indicates how severe the problem is - from blocker ("application
+ unusable") to trivial ("minor cosmetic issue"). You can also use this
+ field to indicate whether a bug is an enhancement request.
</para>
+ </listitem>
+
+ <listitem>
<para>
- The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
- Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric combination, like "M19".
+ <emphasis>Target</emphasis>:
+ (a.k.a. Target Milestone) A future version by which the bug is to be
+ fixed. e.g. The Bugzilla Project's milestones for future
+ Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
+ not restricted to numbers, thought - you can use any text strings,
+ such as dates.
</para>
- </listitem>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Reporter</emphasis>:
+ The person who filed the bug.
+ </para>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- OK, now let's select the "Bugzilla" component from its scrollbox.
+ <emphasis>CC list</emphasis>:
+ A list of people who get mail when the bug changes.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Skip down the page a bit -- do you see the "submit query" button?
- Select it, and let's run
- this query!
+ <emphasis>Attachments</emphasis>:
+ You can attach files (e.g. testcases or patches) to bugs. If there are
+ any attachments, they are listed in this section.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Congratulations! You've completed your first Query, and
- have before you the Bug List of the author of this Guide,
- Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
- well, you'll have a cryptic "Zarro Boogs Found" message on
- your screen. It is just a happy hacker's way of saying
- "Zero Bugs Found". However, I am fairly certain I will
- always have some bugs assigned to me that aren't done yet,
- so you won't often see that message!
+ <emphasis>Dependencies</emphasis>:
+ If this bug cannot be fixed unless other bugs are fixed (depends on), or
+ this bug stops other bugs being fixed (blocks), their numbers are
+ recorded here.
</para>
- </listitem>
- </orderedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Votes</emphasis>:
+ Whether this bug has any votes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Additional Comments</emphasis>:
+ You can add your two cents to the bug discussion here, if you have
+ something worthwhile to say.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </section>
+
+ <section id="query">
+ <title>Searching for Bugs</title>
<para>
- I encourage you to click the bug numbers in the left-hand
- column and examine my bugs. Also notice that if you click the
- underlined links near the top of this page, they do not take
- you to context-sensitive help here, but instead sort the
- columns of bugs on the screen! When you need to sort your bugs
- by priority, severity, or the people they are assigned to,
- this is a tremendous timesaver.
+ The Bugzilla Search page is is the interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. You can play with it here:
+ <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
+ landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>.
+ </para>
+
+ <para>
+ The Search page has controls for selecting different possible values
+ for all of the fields in a bug, as described above. Once you've defined
+ a search, you can either run it, or save it as a Remembered Query, which
+ can optionally appear in the footer of your pages.
+ </para>
+
+ <para>
+ Highly advanced querying is done using Boolean Charts, which have their
+ own <ulink url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">context-sensitive help</ulink>.
+ </para>
+
+ </section>
+
+ <section id="list">
+ <title>Bug Lists</title>
+ <para>
+ If you run a search, a list of matching bugs will be returned.
+ The default search is to return all open bugs on the system -
+ don't try running this search on a Bugzilla installation with
+ a lot of bugs!
</para>
<para>
- A couple more interesting things about the Bug List page:
+ The format of the list is configurable. For example, it can be
+ sorted by clicking the column headings. Other useful features
+ can be accessed using the links at the bottom of the list:
<simplelist>
- <member><emphasis>Change Columns</emphasis>: by selecting
- this link, you can show all kinds of information in the
- Bug List</member>
+ <member><emphasis>Long Format</emphasis>: this gives you a large page
+ with a non-editable summary of the fields of each bug.</member>
+ <member><emphasis>Change Columns</emphasis>: change the bug
+ attributes which appear in the list.</member>
<member><emphasis>Change several bugs at once</emphasis>: If
- you have sufficient rights to change all the bugs shown in
- the Bug List, you can mass-modify them. This is a big
- time-saver.</member>
- <member><emphasis>Send mail to bug owners</emphasis>: If you
- have many related bugs, you can request an update from
- every person who owns the bugs in the Bug List asking them
- the status.</member>
+ your account is sufficiently empowered, you can make the same
+ change to all the bugs in the list - for example, changing their
+ owner.</member>
+ <member><emphasis>Send mail to bug owners</emphasis>: Sends mail
+ to the owners of all bugs on the list.</member>
<member><emphasis>Edit this query</emphasis>: If you didn't
get exactly the results you were looking for, you can
return to the Query page through this link and make small
accurate results.</member>
</simplelist>
</para>
- <note>
- <para>
- There are many more options to the Bugzilla Query Page and
- the Bug List than I have shown you. But this should be
- enough for you to learn to get around. I encourage you to
- check out the <ulink
- url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing.
- </para>
- </note>
</section>
<section id="bugreports">
- <title>Creating and Managing Bug Reports</title>
+ <title>Filing Bugs</title>
<epigraph>
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
- <section id="bug-writing">
- <title>Writing a Great Bug Report</title>
- <para>
- Before we plunge into writing your first bug report, I
- encourage you to read some bug-writing guidelines. If you
- are reading this document as part of a Bugzilla CVS checkout
- or un-tarred Bugzilla distribution, you should be able to
- read them by clicking <ulink
- url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
- </para>
- <para>
- While you are at it, why not learn how to find previously
- reported bugs? Mozilla.org has published a great tutorial
- on finding duplicate bugs, available at <ulink
- url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
- </para>
<para>
- I realize this was a lot to read. However, understanding
- the mentality of writing great bug reports will help us on
- the next part!
+ Years of bug writing experience has been distilled for your reading
+ pleasure into the <ulink url="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html">
+ Bug Writing Guidelines</ulink>.
+While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
+ <para>
+ The procedure for filing a test bug is as follows:
+ </para>
+
<orderedlist>
<listitem>
<para>
- Go back to <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link.
+ Go to <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/">Landfill</ulink>
+ in your browser and click
+ <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink>.
</para>
</listitem>
<listitem>
<para>
- Select a product.
- </para>
- </listitem>
- <listitem>
- <para>
- Now you should be at the "Enter Bug" form. The
- "reporter" should have been automatically filled out for
- you (or else Bugzilla prompted you to Log In again --
- you did keep the email with your username and password,
- didn't you?).
- </para>
- </listitem>
- <listitem>
- <para>
- Select a Component in the scrollbox.
+ Select a product - any one will do.
</para>
</listitem>
<listitem>
<para>
+ Fill in the fields.
Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on
- an SGI box running IRIX, we want to know!
- </para>
- </listitem>
- <listitem>
- <para>
- Fill in the "Assigned To" box with the email address you
- provided earlier. This way you don't end up sending
- copies of your bug to lots of other people, since it's
- just a test bug.
- </para>
- </listitem>
- <listitem>
- <para>
- Leave the "CC" text box blank. Fill in the "URL" box
- with "http://www.mozilla.org".
- </para>
- </listitem>
- <listitem>
- <para>
- Enter "The Bugzilla Guide" in the Summary text box, and
- place any comments you have on this tutorial, or the
- Guide in general, into the Description box.
- </para>
- </listitem>
- </orderedlist>
- <para>
- Voila! Select "Commit" and send in your bug report! Next
- we'll look at resolving bugs.
- </para>
- </section>
-
- <section id="bug-manage">
- <title>Managing your Bug Reports</title>
- <para>
- OK, you should have a link to the bug you just created near
- the top of your page. It should say "Bug XXXX posted", with
- a link to the right saying "Back to BUG# XXXX". Select this
- link.
- </para>
- <orderedlist>
- <listitem>
- <para>
- Scroll down a bit on the subsequent page, until you see
- the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would "Accept bug (change status to
- ASSIGNED)", fix it, and then resolve. But in this case,
- we're going to short-circuit the process because this
- wasn't a real bug. Change the dropdown next to "Resolve
- Bug" to "INVALID", make sure the radio button is marked
- next to "Resolve Bug", then click "Commit".
+ boxes. If they are wrong, change them.
</para>
</listitem>
<listitem>
<para>
- Hey! It said it couldn't take the change in a big red
- box! That's right, you must specify a Comment in order
- to make this change. Select the "Back" button in your
- browser, add a Comment, then try Resolving the bug with
- INVALID status again. This time it should work.
+ Select "Commit" and send in your bug report.
</para>
</listitem>
- </orderedlist>
- <para>
- You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance. I encourage you to
- explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from
- this point on, so you are on your own there.
- </para>
- <para>
- But I'll give a few last hints!
- </para>
- <para>
- There is a <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form.
- </para>
- <para>
- If you click the hyperlink on the <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are.
- </para>
- <para>
- Possibly the most powerful feature of the Query page is the
- <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
- </para>
- <para>
- Finally, you can build some nifty <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
- </para>
- </section>
+ </orderedlist>
</section>
</section>
make certain files world readable and/or writable. <emphasis>THIS IS
INSECURE!</emphasis>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
- <note>
+ </para>
+ <note>
+ <para>
This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
- </note>
- </para>
+ </para>
+ </note>
<para>
On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ulink> for the localconfig file, and <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"> Bug 65572</ulink> for adequate protection in your data/ and shadow/ directories.
<row>
<entry>Warnings</entry>
<entry><caution>
- <para>Warnings.</para>
+ <para>Don't run with scissors!</para>
</caution></entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
- <para>Hint.</para>
+ <para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
- <para>Note.</para>
+ <para>Dear John...</para>
</note></entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
- <para>Warning.</para>
+ <para>Read this or the cat gets it.</para>
</warning></entry>
</row>
<row>
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
<itemizedlist>
- <listitem>
- <para>
- integrated, product-based granular security schema
- </para>
- </listitem>
- <listitem>
- <para>
- inter-bug dependencies and dependency graphing
- </para>
- </listitem>
- <listitem>
- <para>
- advanced reporting capabilities
- </para>
- </listitem>
- <listitem>
- <para>
- a robust, stable RDBMS back-end
- </para>
- </listitem>
- <listitem>
- <para>
- extensive configurability
- </para>
- </listitem>
- <listitem>
- <para>
- a very well-understood and well-thought-out natural bug resolution protocol
- </para>
- </listitem>
- <listitem>
- <para>
- email, XML, console, and web interfaces
- </para>
- </listitem>
- <listitem>
- <para>
- available integration with automated software
- configuration management systems, including Perforce and
- CVS (through the Bugzilla email interface and
- checkin/checkout scripts)
- </para>
- </listitem>
- <listitem>
- <para>
- too many more features to list
- </para>
- </listitem>
+
+<listitem><para>Powerful searching</para></listitem>
+<listitem><para>User-configurable email notifications of bug changes</para></listitem>
+<listitem><para>Full change history</para></listitem>
+<listitem><para>Inter-bug dependency tracking and graphing</para></listitem>
+<listitem><para>Excellent attachment management</para></listitem>
+<listitem><para>Integrated, product-based, granular security schema</para></listitem>
+<listitem><para>Fully security-audited, and runs under Perl's taint mode</para></listitem>
+<listitem><para>A robust, stable RDBMS back-end</para></listitem>
+<listitem><para>Web, XML, email and console interfaces</para></listitem>
+<listitem><para>Completely customisable and/or localisable web user interface</para></listitem>
+<listitem><para>Extensive configurability</para></listitem>
+<listitem><para>Smooth upgrade pathway between versions</para></listitem>
+
</itemizedlist>
</para>
</section>
</epigraph>
<para>
- Bugzilla is a large, complex system. Describing how to use it
- requires some time. If you are only interested in installing or
- administering a Bugzilla installation, please consult the
+ This section contains information for end-users of Bugzilla.
+ If you are administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
- This section is principally aimed towards developing end-user
- mastery of Bugzilla, so you may fully enjoy the benefits
- afforded by using this reliable open-source bug-tracking
- software.
</para>
<para>
- Throughout this portion of the Guide, we will refer to user
- account options available at the Bugzilla test installation,
+ There is a Bugzilla test installation, called
<ulink url="http://landfill.tequilarista.org/">
- landfill.tequilarista.org</ulink>.
- Although Landfill serves as a great introduction to
- Bugzilla, it does not offer all the options you would have as a
- user on your own installation of Bugzilla, nor can it do more
- than serve as a general introduction to Bugzilla. Additionally,
- Landfill often runs cutting-edge versions of Bugzilla for
+ Landfill</ulink>, which you are welcome to play with.
+ However, it does not necessarily have all Bugzilla features
+ enabled, and often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</para>
If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
- should use to access it. If you're test-driving the end-user
-
Bugzilla experience, use this URL: <ulink
+ should use to access it. If you're test-driving Bugzilla,
+ use this URL: <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
<para>
- Click the "Open a new Bugzilla account" link.
- </para>
- </listitem>
- <listitem>
- <para>
- Enter your "E-mail address" and "Real Name" (or whatever
- name you want to call yourself) in the spaces provided,
- then select the "Create Account" button.
+ Click the <quote>Open a new Bugzilla account</quote> link, enter your
+ email address and, optionally, your name in the spaces provided,
+ then click <quote>Create Account</quote>.
</para>
</listitem>
<listitem>
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
- randomly generated, and should be changed at your nearest
- opportunity (we'll go into how to do it later).
+ randomly generated, and can be changed to something more memorable.
</para>
</listitem>
<listitem>
<para>
Click the <quote>Log In</quote> link in the yellow area at
- the bottom of the page in your browser, then enter your
- <quote>E-mail address</quote> and <quote>Password</quote>
- you just received into the spaces provided, and select
+ the bottom of the page in your browser, enter your
+ email address and password into the spaces provided, and click
<quote>Login</quote>.
- <note>
- <para>
- If you ever forget your password, you can come back to
- this page, enter your <quote>E-mail address</quote>,
- then select the <quote>E-mail me a password</quote>
- button to have your password mailed to you again so
- that you can login.
- </para>
- </note>
</para>
</listitem>
</orderedlist>
<para>
- Congratulations! If you followed these directions, you now
- are the proud owner of a user account on
- landfill.tequilarista.org (Landfill) or your local Bugzilla
- install. You should now see in your browser a page called the
- <quote>Bugzilla Query Page</quote>. It may look daunting, but with this
- Guide to walk you through it, you will master it in no time.
+ You are now logged in. Bugzilla uses cookies for authentication, so
+ (unless your IP address changes) you should not have to log in again.
</para>
</section>
- <section id="query">
- <title>The Bugzilla Query Page</title>
- <para>
- The Bugzilla Query Page is the heart and soul of the Bugzilla
- user experience. It is the master interface where you can
- find any bug report, comment, or patch currently in the
- Bugzilla system. We'll go into how to create your own bug
- report later on.
- </para>
- <para>
- At this point, let's visit the query page.
- <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
- landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>
- </para>
- <para>
- The first thing you need to notice about the Bugzilla Query
- Page is that nearly every box you see on your screen has a
- hyperlink nearby, explaining what it is or what it does. Near
- the upper-left-hand corner of your browser window you should
- see the word <quote>Status</quote> underlined. Select it.
- </para>
+ <section id="bug_page">
+ <title>Anatomy of a Bug</title>
<para>
- Notice the page that popped up? Every underlined word you see
- on your screen is a hyperlink that will take you to
- context-sensitive help. Click around for a while, and learn
- what everything here does. To return to the query interface
- after pulling up a help page, use the <quote>Back</quote>
- button in your browser.
+ The core of Bugzilla is the screen which displays a particular bug.
+ It's a good place to explain some Bugzilla concepts.
+ <ulink url="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">Bug 1 on Landfill</ulink> is a good example. Note that the names of most fields
+ are hyperlinks; clicking them will take you to context-sensitive
+ help on that particular field.
</para>
- <para>
- I'm sure that after checking out the online help, you are now
- an expert on the Bugzilla Query Page. If, however, you feel
- you haven't mastered it yet, let me walk you through making a
- few successful queries to find out what there are in the
- Bugzilla bug-tracking system itself.
- </para>
- <orderedlist>
- <listitem>
+
+ <orderedlist>
+ <listitem>
+ <para>
+ <emphasis>Product and Component</emphasis>:
+ Bugs are divided up by Product and Component, with a Product having one
+ or more Components in it. For example, bugzilla.mozilla.org's
+ "Bugzilla" Product is composed of several Components:
+ <simplelist>
+ <member><emphasis>Administration</emphasis>,
+ Administration of a bugzilla installation, including
+ <filename>editcomponents.cgi</filename>,
+ <filename>editgroups.cgi</filename>,
+ <filename>editkeywords.cgi</filename>,
+ <filename>editparams.cgi</filename>,
+ <filename>editproducts.cgi</filename>,
+ <filename>editusers.cgi</filename>,
+ <filename>editversions.cgi,</filename> and
+ <filename>sanitycheck.cgi</filename>.
+ </member>
+ <member><emphasis>Bugzilla-General</emphasis>,
+ Anything that doesn't fit in the other components, or spans
+ multiple components.
+ </member>
+ <member><emphasis>Creating/Changing Bugs</emphasis>,
+ Creating, changing, and viewing bugs.
+ <filename>enter_bug.cgi</filename>,
+ <filename>post_bug.cgi</filename>,
+ <filename>show_bug.cgi</filename> and
+ <filename>process_bug.cgi</filename>.
+ </member>
+ <member><emphasis>Documentation</emphasis>,
+ The bugzilla documentation, including anything in the
+ <filename>docs/</filename> directory and The Bugzilla Guide
+
+ </member>
+ <member><emphasis>Email</emphasis>,
+ Anything to do with email sent by Bugzilla.
+ <filename>processmail</filename>
+ </member>
+ <member><emphasis>Installation</emphasis>,
+ The installation process of Bugzilla. This includes
+ <filename>checksetup.pl</filename> and whatever else it evolves into.
+ </member>
+ <member><emphasis>Query/Buglist</emphasis>,
+ Anything to do with searching for bugs and viewing the buglists.
+ <filename>query.cgi</filename> and
+ <filename>buglist.cgi</filename>
+ </member>
+ <member><emphasis>Reporting/Charting</emphasis>,
+ Getting reports from Bugzilla.
+ <filename>reports.cgi</filename> and
+ <filename>duplicates.cgi</filename>
+ </member>
+ <member><emphasis>User Accounts</emphasis>,
+ Anything about managing a user account from the user's perspective.
+ <filename>userprefs.cgi</filename>, saved queries, creating accounts,
+ changing passwords, logging in, etc.
+ </member>
+ <member><emphasis>User Interface</emphasis>,
+ General issues having to do with the user interface cosmetics (not
+ functionality) including cosmetic issues, HTML templates, etc.
+ </member>
+ </simplelist>
+ </para>
+ </listitem>
+
+ <listitem>
<para>
- Ensure you are back on the <quote>Bugzilla Query
- Page</quote>. Do nothing in the boxes marked "Status",
- "Resolution", "Platform", "OpSys", "Priority", or
- "Severity". The default query for "Status" is to find all
- bugs that are NEW, ASSIGNED, or REOPENED, which is what we
- want. If you don't select anything in the other 5
- scrollboxes there, then you are saying that "any of these
- are OK"; we're not locking ourselves into only finding
- bugs on the "DEC" Platform, or "Windows 95" OpSys
- (Operating System). You're smart, I think you have it
- figured out.
+ <emphasis>Status and Resolution</emphasis>:
+ A bug passes through several Statuses in its lifetime, and ends up in the
+ RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
+ The different possible
+ values for Status and Resolution on your installation will be documented
+ in the context-sensitive help for those items.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Assigned To</emphasis>:
+ The person responsible for fixing the bug.
</para>
+ </listitem>
+
+ <listitem>
<para>
- Basically, selecting <emphasis>anything</emphasis> on the
- query page narrows your search down. Leaving stuff
- unselected, or text boxes unfilled, broadens your search.
+ <emphasis>URL</emphasis>:
+ A URL associated with the bug, if any.
</para>
- </listitem>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- You see the box immediately below the top six boxes that
- contains an "Email" text box, with the words "matching
- as", a drop-down selection box, then some checkboxes with
- "Assigned To" checked by default? This allows you to
- filter your search down based upon email address. Let's
- put my email address in there, and see what happens.
+ <emphasis>Summary</emphasis>:
+ A one-sentence summary of the problem.
</para>
+ </listitem>
+
+ <listitem>
<para>
- Type "barnboy@trilobyte.net" in the top Email text box.
+ <emphasis>Status Whiteboard</emphasis>: (a.k.a. Whiteboard) A
+ free-form text area for adding short notes and tags to a bug.
</para>
- </listitem>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Keywords</emphasis>:
+ The administrator can define keywords which you can use to tag and
+ categorise bugs - e.g. The Mozilla Project has keywords like crash
+ and regression.
+ </para>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- Let's narrow the search some more. Scroll down until you
- find the box with the word "Program" over the top of it.
- This is where we can narrow our search down to only
- specific products (software programs or product lines) in
- our Bugzilla database. Please notice the box is a
- <emphasis>scrollbox</emphasis>. Using the down arrow on
- the scrollbox, scroll down until you can see an entry
- called "Bugzilla". Select this entry.
+ <emphasis>Platform and OS</emphasis>:
+ These indicate the computing environment where the bug was found.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Did you notice that some of the boxes to the right changed
- when you selected "Bugzilla"? Every Program (or Product)
- has different Versions, Components, and Target Milestones
- associated with it. A "Version" is the number of a
- software program.
- <example>
- <title>Some Famous Software Versions</title>
- <informalexample>
- <para>
- Do you remember the hype in 1995 when Microsoft
- Windows 95(r) was released? It may have been several
- years ago, but Microsoft(tm) spent over $300 Million
- advertising this new Version of their software.
- Three years later, they released Microsoft Windows
- 98(r), another new version, to great fanfare, and
- then in 2000 quietly released Microsoft Windows
- ME(Millenium Edition)(r).
- </para>
- <para>
- Software "Versions" help a manufacturer
- differentiate their current product from their
- previous products. Most do not identify their
- products by the year they were released. Instead,
- the "original" version of their software will often
- be numbered "1.0", with small bug-fix releases on
- subsequent tenths of a digit. In most cases, it's
- not a decimal number; for instance, often 1.9 is an
- <emphasis>older</emphasis> version of the software
- than 1.11, but is a <emphasis>newer</emphasis>
- version than 1.1.1.
- </para>
- <para>
- In general, a "Version" in Bugzilla should refer to
- <emphasis>released</emphasis> products, not products
- that have not yet been released to the public.
- Forthcoming products are what the Target Milestone
- field is for.
- </para>
- </informalexample>
- </example>
+ <emphasis>Version</emphasis>:
+ The "Version" field is usually used for versions of a product which have
+ been released, and is set to indicate which versions of a Component
+ have the particular problem the bug report is about.
</para>
+ </listitem>
+
+ <listitem>
<para>
- A "Component" is a piece of a Product.
- It may be a standalone program, or some other logical
- division of a Product or Program.
- Normally, a Component has a single Owner, who is responsible
- for overseeing efforts to improve that Component.
- <example>
- <title>Mozilla's Bugzilla Components</title>
- <informalexample>
- <para>
- Mozilla's "Bugzilla" Product is composed of several pieces (Components):
- <simplelist>
- <member><emphasis>Administration</emphasis>,
- Administration of a bugzilla installation, including
- <filename>editcomponents.cgi</filename>,
- <filename>editgroups.cgi</filename>,
- <filename>editkeywords.cgi</filename>,
- <filename>editparams.cgi</filename>,
- <filename>editproducts.cgi</filename>,
- <filename>editusers.cgi</filename>,
- <filename>editversions.cgi,</filename> and
- <filename>sanitycheck.cgi</filename>.
- </member>
- <member><emphasis>Bugzilla-General</emphasis>,
- Anything that doesn't fit in the other components, or spans
- multiple components.
- </member>
- <member><emphasis>Creating/Changing Bugs</emphasis>,
- Creating, changing, and viewing bugs.
- <filename>enter_bug.cgi</filename>,
- <filename>post_bug.cgi</filename>,
- <filename>show_bug.cgi</filename> and
- <filename>process_bug.cgi</filename>.
- </member>
- <member><emphasis>Documentation</emphasis>,
- The bugzilla documentation, including anything in the
- <filename>docs/</filename> directory and The Bugzilla Guide
- (This document :)
- </member>
- <member><emphasis>Email</emphasis>,
- Anything to do with email sent by Bugzilla.
- <filename>processmail</filename>
- </member>
- <member><emphasis>Installation</emphasis>,
- The installation process of Bugzilla. This includes
- <filename>checksetup.pl</filename> and whatever else it evolves into.
- </member>
- <member><emphasis>Query/Buglist</emphasis>,
- Anything to do with searching for bugs and viewing the buglists.
- <filename>query.cgi</filename> and
- <filename>buglist.cgi</filename>
- </member>
- <member><emphasis>Reporting/Charting</emphasis>,
- Getting reports from Bugzilla.
- <filename>reports.cgi</filename> and
- <filename>duplicates.cgi</filename>
- </member>
- <member><emphasis>User Accounts</emphasis>,
- Anything about managing a user account from the user's perspective.
- <filename>userprefs.cgi</filename>, saved queries, creating accounts,
- changing passwords, logging in, etc.
- </member>
- <member><emphasis>User Interface</emphasis>,
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates, etc.
- </member>
- </simplelist>
- </para>
- </informalexample>
- </example>
+ <emphasis>Priority</emphasis>:
+ The bug assignee uses this field to prioritise his or her bugs. It's
+ a good idea not to change this on other people's bugs.
</para>
+ </listitem>
+
+ <listitem>
<para>
- A "Milestone", or "Target Milestone" is a often a planned
- future "Version" of a product. In many cases, though,
- Milestones simply represent significant dates for a
- developer. Having certain features in your Product is
- frequently tied to revenue (money) the developer will
- receive if the features work by the time she reaches the
- Target Milestone. Target Milestones are a great tool to
- organize your time. If someone will pay you $100,000 for
- incorporating certain features by a certain date, those
- features by that Milestone date become a very high
- priority. Milestones tend to be highly malleable
- creatures, though, that appear to be in reach but are out
- of reach by the time the important day arrives.
+ <emphasis>Severity</emphasis>:
+ This indicates how severe the problem is - from blocker ("application
+ unusable") to trivial ("minor cosmetic issue"). You can also use this
+ field to indicate whether a bug is an enhancement request.
</para>
+ </listitem>
+
+ <listitem>
<para>
- The Bugzilla Project has set up Milestones for future
- Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
- Target Milestone can just as easily be a specific date,
- code name, or weird alphanumeric combination, like "M19".
+ <emphasis>Target</emphasis>:
+ (a.k.a. Target Milestone) A future version by which the bug is to be
+ fixed. e.g. The Bugzilla Project's milestones for future
+ Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
+ not restricted to numbers, thought - you can use any text strings,
+ such as dates.
</para>
- </listitem>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Reporter</emphasis>:
+ The person who filed the bug.
+ </para>
+ </listitem>
- <listitem>
+ <listitem>
<para>
- OK, now let's select the "Bugzilla" component from its scrollbox.
+ <emphasis>CC list</emphasis>:
+ A list of people who get mail when the bug changes.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Skip down the page a bit -- do you see the "submit query" button?
- Select it, and let's run
- this query!
+ <emphasis>Attachments</emphasis>:
+ You can attach files (e.g. testcases or patches) to bugs. If there are
+ any attachments, they are listed in this section.
</para>
- </listitem>
- <listitem>
+ </listitem>
+
+ <listitem>
<para>
- Congratulations! You've completed your first Query, and
- have before you the Bug List of the author of this Guide,
- Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
- well, you'll have a cryptic "Zarro Boogs Found" message on
- your screen. It is just a happy hacker's way of saying
- "Zero Bugs Found". However, I am fairly certain I will
- always have some bugs assigned to me that aren't done yet,
- so you won't often see that message!
+ <emphasis>Dependencies</emphasis>:
+ If this bug cannot be fixed unless other bugs are fixed (depends on), or
+ this bug stops other bugs being fixed (blocks), their numbers are
+ recorded here.
</para>
- </listitem>
- </orderedlist>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Votes</emphasis>:
+ Whether this bug has any votes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Additional Comments</emphasis>:
+ You can add your two cents to the bug discussion here, if you have
+ something worthwhile to say.
+ </para>
+ </listitem>
+
+ </orderedlist>
+
+ </section>
+
+ <section id="query">
+ <title>Searching for Bugs</title>
<para>
- I encourage you to click the bug numbers in the left-hand
- column and examine my bugs. Also notice that if you click the
- underlined links near the top of this page, they do not take
- you to context-sensitive help here, but instead sort the
- columns of bugs on the screen! When you need to sort your bugs
- by priority, severity, or the people they are assigned to,
- this is a tremendous timesaver.
+ The Bugzilla Search page is is the interface where you can
+ find any bug report, comment, or patch currently in the
+ Bugzilla system. You can play with it here:
+ <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
+ landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>.
+ </para>
+
+ <para>
+ The Search page has controls for selecting different possible values
+ for all of the fields in a bug, as described above. Once you've defined
+ a search, you can either run it, or save it as a Remembered Query, which
+ can optionally appear in the footer of your pages.
+ </para>
+
+ <para>
+ Highly advanced querying is done using Boolean Charts, which have their
+ own <ulink url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">context-sensitive help</ulink>.
+ </para>
+
+ </section>
+
+ <section id="list">
+ <title>Bug Lists</title>
+ <para>
+ If you run a search, a list of matching bugs will be returned.
+ The default search is to return all open bugs on the system -
+ don't try running this search on a Bugzilla installation with
+ a lot of bugs!
</para>
<para>
- A couple more interesting things about the Bug List page:
+ The format of the list is configurable. For example, it can be
+ sorted by clicking the column headings. Other useful features
+ can be accessed using the links at the bottom of the list:
<simplelist>
- <member><emphasis>Change Columns</emphasis>: by selecting
- this link, you can show all kinds of information in the
- Bug List</member>
+ <member><emphasis>Long Format</emphasis>: this gives you a large page
+ with a non-editable summary of the fields of each bug.</member>
+ <member><emphasis>Change Columns</emphasis>: change the bug
+ attributes which appear in the list.</member>
<member><emphasis>Change several bugs at once</emphasis>: If
- you have sufficient rights to change all the bugs shown in
- the Bug List, you can mass-modify them. This is a big
- time-saver.</member>
- <member><emphasis>Send mail to bug owners</emphasis>: If you
- have many related bugs, you can request an update from
- every person who owns the bugs in the Bug List asking them
- the status.</member>
+ your account is sufficiently empowered, you can make the same
+ change to all the bugs in the list - for example, changing their
+ owner.</member>
+ <member><emphasis>Send mail to bug owners</emphasis>: Sends mail
+ to the owners of all bugs on the list.</member>
<member><emphasis>Edit this query</emphasis>: If you didn't
get exactly the results you were looking for, you can
return to the Query page through this link and make small
accurate results.</member>
</simplelist>
</para>
- <note>
- <para>
- There are many more options to the Bugzilla Query Page and
- the Bug List than I have shown you. But this should be
- enough for you to learn to get around. I encourage you to
- check out the <ulink
- url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing.
- </para>
- </note>
</section>
<section id="bugreports">
- <title>Creating and Managing Bug Reports</title>
+ <title>Filing Bugs</title>
<epigraph>
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
- <section id="bug-writing">
- <title>Writing a Great Bug Report</title>
- <para>
- Before we plunge into writing your first bug report, I
- encourage you to read some bug-writing guidelines. If you
- are reading this document as part of a Bugzilla CVS checkout
- or un-tarred Bugzilla distribution, you should be able to
- read them by clicking <ulink
- url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
- </para>
- <para>
- While you are at it, why not learn how to find previously
- reported bugs? Mozilla.org has published a great tutorial
- on finding duplicate bugs, available at <ulink
- url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
- </para>
<para>
- I realize this was a lot to read. However, understanding
- the mentality of writing great bug reports will help us on
- the next part!
+ Years of bug writing experience has been distilled for your reading
+ pleasure into the <ulink url="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html">
+ Bug Writing Guidelines</ulink>.
+While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
+ <para>
+ The procedure for filing a test bug is as follows:
+ </para>
+
<orderedlist>
<listitem>
<para>
- Go back to <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser.
- </para>
- </listitem>
- <listitem>
- <para>
- Select the <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link.
+ Go to <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/">Landfill</ulink>
+ in your browser and click
+ <ulink
+ url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink>.
</para>
</listitem>
<listitem>
<para>
- Select a product.
- </para>
- </listitem>
- <listitem>
- <para>
- Now you should be at the "Enter Bug" form. The
- "reporter" should have been automatically filled out for
- you (or else Bugzilla prompted you to Log In again --
- you did keep the email with your username and password,
- didn't you?).
- </para>
- </listitem>
- <listitem>
- <para>
- Select a Component in the scrollbox.
+ Select a product - any one will do.
</para>
</listitem>
<listitem>
<para>
+ Fill in the fields.
Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
- boxes. If those are wrong, change them -- if you're on
- an SGI box running IRIX, we want to know!
- </para>
- </listitem>
- <listitem>
- <para>
- Fill in the "Assigned To" box with the email address you
- provided earlier. This way you don't end up sending
- copies of your bug to lots of other people, since it's
- just a test bug.
- </para>
- </listitem>
- <listitem>
- <para>
- Leave the "CC" text box blank. Fill in the "URL" box
- with "http://www.mozilla.org".
- </para>
- </listitem>
- <listitem>
- <para>
- Enter "The Bugzilla Guide" in the Summary text box, and
- place any comments you have on this tutorial, or the
- Guide in general, into the Description box.
- </para>
- </listitem>
- </orderedlist>
- <para>
- Voila! Select "Commit" and send in your bug report! Next
- we'll look at resolving bugs.
- </para>
- </section>
-
- <section id="bug-manage">
- <title>Managing your Bug Reports</title>
- <para>
- OK, you should have a link to the bug you just created near
- the top of your page. It should say "Bug XXXX posted", with
- a link to the right saying "Back to BUG# XXXX". Select this
- link.
- </para>
- <orderedlist>
- <listitem>
- <para>
- Scroll down a bit on the subsequent page, until you see
- the "Resolve bug, changing resolution to (dropdown box).
- Normally, you would "Accept bug (change status to
- ASSIGNED)", fix it, and then resolve. But in this case,
- we're going to short-circuit the process because this
- wasn't a real bug. Change the dropdown next to "Resolve
- Bug" to "INVALID", make sure the radio button is marked
- next to "Resolve Bug", then click "Commit".
+ boxes. If they are wrong, change them.
</para>
</listitem>
<listitem>
<para>
- Hey! It said it couldn't take the change in a big red
- box! That's right, you must specify a Comment in order
- to make this change. Select the "Back" button in your
- browser, add a Comment, then try Resolving the bug with
- INVALID status again. This time it should work.
+ Select "Commit" and send in your bug report.
</para>
</listitem>
- </orderedlist>
- <para>
- You have now learned the basics of Bugzilla navigation,
- entering a bug, and bug maintenance. I encourage you to
- explore these features, and see what you can do with them!
- We'll spend no more time on individual Bugs or Queries from
- this point on, so you are on your own there.
- </para>
- <para>
- But I'll give a few last hints!
- </para>
- <para>
- There is a <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form.
- </para>
- <para>
- If you click the hyperlink on the <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are.
- </para>
- <para>
- Possibly the most powerful feature of the Query page is the
- <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
- </para>
- <para>
- Finally, you can build some nifty <ulink
- url="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
- </para>
- </section>
+ </orderedlist>
</section>
</section>
projects / thirdparty / bugzilla.git / commitdiff
