<HTML
><HEAD
><TITLE
->The Bugzilla Guide - 2.16.3 Release</TITLE
+>The Bugzilla Guide - 2.16.4 Release</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
><DIV
CLASS="BOOK"
><A
-NAME="index"
-></A
-><DIV
+NAME="index"><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
-NAME="AEN2"
-></A
->The Bugzilla Guide - 2.16.3 Release</H1
+NAME="AEN2">The Bugzilla Guide - 2.16.4 Release</H1
><H3
CLASS="author"
><A
-NAME="AEN5"
-></A
->Matthew P. Barnson</H3
+NAME="AEN5">Matthew P. Barnson</H3
><H3
CLASS="author"
><A
-NAME="AEN9"
-></A
->The Bugzilla Team</H3
+NAME="AEN9">The Bugzilla Team</H3
><P
CLASS="pubdate"
->2003-04-23<BR></P
+>2003-11-01<BR></P
><DIV
><DIV
CLASS="abstract"
><A
-NAME="AEN14"
-></A
-><P
+NAME="AEN14"><P
></P
><P
> This is the documentation for Bugzilla, the mozilla.org
>.
</P
><P
+> The most current version of this document can always be found on the
+ <A
+HREF="http://www.bugzilla.org/documentation.html"
+TARGET="_top"
+>Bugzilla Documentation Page</A
+>.
+ </P
+><P
></P
></DIV
></DIV
></DT
><DT
>4-1. <A
-HREF="#AEN861"
+HREF="#AEN863"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
-HREF="#AEN874"
+HREF="#AEN876"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
-HREF="#AEN1056"
+HREF="#AEN1058"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
></DT
CLASS="chapter"
><HR><H1
><A
-NAME="about"
-></A
->Chapter 1. About This Guide</H1
+NAME="about">Chapter 1. About This Guide</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="copyright"
-></A
->1.1. Copyright Information</H1
+NAME="copyright">1.1. Copyright Information</H1
><A
-NAME="AEN32"
-></A
-><TABLE
+NAME="AEN34"><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
><HR><H1
CLASS="section"
><A
-NAME="disclaimer"
-></A
->1.2. Disclaimer</H1
+NAME="disclaimer">1.2. Disclaimer</H1
><P
> No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
><HR><H1
CLASS="section"
><A
-NAME="newversions"
-></A
->1.3. New Versions</H1
+NAME="newversions">1.3. New Versions</H1
><P
-> This is the 2.16.3 version of The Bugzilla Guide. It is so named
+> This is the 2.16.4 version of The Bugzilla Guide. It is so named
to match the version of Bugzilla it is disributed with. 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
><HR><H1
CLASS="section"
><A
-NAME="credits"
-></A
->1.4. Credits</H1
+NAME="credits">1.4. Credits</H1
><P
> The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
><HR><H1
CLASS="section"
><A
-NAME="conventions"
-></A
->1.5. Document Conventions</H1
+NAME="conventions">1.5. Document Conventions</H1
><P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><A
-NAME="AEN109"
-></A
-><P
+NAME="AEN111"><P
></P
><TABLE
BORDER="0"
CLASS="chapter"
><HR><H1
><A
-NAME="introduction"
-></A
->Chapter 2. Introduction</H1
+NAME="introduction">Chapter 2. Introduction</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="whatis"
-></A
->2.1. What is Bugzilla?</H1
+NAME="whatis">2.1. What is Bugzilla?</H1
><P
> Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
><HR><H1
CLASS="section"
><A
-NAME="why"
-></A
->2.2. Why Should We Use Bugzilla?</H1
+NAME="why">2.2. Why Should We Use Bugzilla?</H1
><P
>For many years, defect-tracking software has remained principally
the domain of large software development houses. Even then, most shops
CLASS="chapter"
><HR><H1
><A
-NAME="using"
-></A
->Chapter 3. Using Bugzilla</H1
+NAME="using">Chapter 3. Using Bugzilla</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="how"
-></A
->3.1. How do I use Bugzilla?</H1
+NAME="how">3.1. How do I use Bugzilla?</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
><HR><H2
CLASS="section"
><A
-NAME="myaccount"
-></A
->3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
><HR><H2
CLASS="section"
><A
-NAME="bug_page"
-></A
->3.1.2. Anatomy of a Bug</H2
+NAME="bug_page">3.1.2. Anatomy of a Bug</H2
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
><HR><H2
CLASS="section"
><A
-NAME="query"
-></A
->3.1.3. Searching for Bugs</H2
+NAME="query">3.1.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
><HR><H2
CLASS="section"
><A
-NAME="list"
-></A
->3.1.4. Bug Lists</H2
+NAME="list">3.1.4. Bug Lists</H2
><P
>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
><HR><H2
CLASS="section"
><A
-NAME="bugreports"
-></A
->3.1.5. Filing Bugs</H2
+NAME="bugreports">3.1.5. Filing Bugs</H2
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
><HR><H1
CLASS="section"
><A
-NAME="hintsandtips"
-></A
->3.2. Hints and Tips</H1
+NAME="hintsandtips">3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
><HR><H2
CLASS="section"
><A
-NAME="AEN370"
-></A
->3.2.1. Autolinkification</H2
+NAME="AEN372">3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
><HR><H2
CLASS="section"
><A
-NAME="quicksearch"
-></A
->3.2.2. Quicksearch</H2
+NAME="quicksearch">3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
><HR><H2
CLASS="section"
><A
-NAME="commenting"
-></A
->3.2.3. Comments</H2
+NAME="commenting">3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
><HR><H2
CLASS="section"
><A
-NAME="attachments"
-></A
->3.2.4. Attachments</H2
+NAME="attachments">3.2.4. Attachments</H2
><P
> Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
><HR><H2
CLASS="section"
><A
-NAME="AEN399"
-></A
->3.2.5. Filing Bugs</H2
+NAME="AEN401">3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
><HR><H1
CLASS="section"
><A
-NAME="userpreferences"
-></A
->3.3. User Preferences</H1
+NAME="userpreferences">3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
><HR><H2
CLASS="section"
><A
-NAME="accountsettings"
-></A
->3.3.1. Account Settings</H2
+NAME="accountsettings">3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
><HR><H2
CLASS="section"
><A
-NAME="emailsettings"
-></A
->3.3.2. Email Settings</H2
+NAME="emailsettings">3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
><HR><H2
CLASS="section"
><A
-NAME="footersettings"
-></A
->3.3.3. Page Footer</H2
+NAME="footersettings">3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
><HR><H2
CLASS="section"
><A
-NAME="permissionsettings"
-></A
->3.3.4. Permissions</H2
+NAME="permissionsettings">3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
CLASS="chapter"
><HR><H1
><A
-NAME="installation"
-></A
->Chapter 4. Installation</H1
+NAME="installation">Chapter 4. Installation</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="stepbystep"
-></A
->4.1. Step-by-step Install</H1
+NAME="stepbystep">4.1. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN428"
-></A
->4.1.1. Introduction</H2
+NAME="AEN430">4.1.1. Introduction</H2
><P
>Bugzilla has been successfully installed under Solaris, Linux,
and Win32. Win32 is not yet officially supported, but many people
><HR><H2
CLASS="section"
><A
-NAME="AEN432"
-></A
->4.1.2. Package List</H2
+NAME="AEN434">4.1.2. Package List</H2
><DIV
CLASS="note"
><P
><HR><H2
CLASS="section"
><A
-NAME="install-mysql"
-></A
->4.1.3. MySQL</H2
+NAME="install-mysql">4.1.3. MySQL</H2
><P
>Visit the MySQL homepage at
<A
><HR><H2
CLASS="section"
><A
-NAME="install-perl"
-></A
->4.1.4. Perl</H2
+NAME="install-perl">4.1.4. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
><DIV
CLASS="tip"
><A
-NAME="bundlebugzilla"
-></A
-><P
+NAME="bundlebugzilla"><P
></P
><TABLE
CLASS="tip"
><HR><H2
CLASS="section"
><A
-NAME="perl-modules"
-></A
->4.1.5. Perl Modules</H2
+NAME="perl-modules">4.1.5. Perl Modules</H2
><P
>
All Perl modules can be found on the
><HR><H3
CLASS="section"
><A
-NAME="AEN578"
-></A
->4.1.5.1. DBI</H3
+NAME="AEN580">4.1.5.1. DBI</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
><HR><H3
CLASS="section"
><A
-NAME="AEN581"
-></A
->4.1.5.2. Data::Dumper</H3
+NAME="AEN583">4.1.5.2. Data::Dumper</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
><HR><H3
CLASS="section"
><A
-NAME="AEN584"
-></A
->4.1.5.3. MySQL-related modules</H3
+NAME="AEN586">4.1.5.3. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
><HR><H3
CLASS="section"
><A
-NAME="AEN589"
-></A
->4.1.5.4. TimeDate modules</H3
+NAME="AEN591">4.1.5.4. TimeDate modules</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
><HR><H3
CLASS="section"
><A
-NAME="AEN592"
-></A
->4.1.5.5. GD (optional)</H3
+NAME="AEN594">4.1.5.5. GD (optional)</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
><HR><H3
CLASS="section"
><A
-NAME="AEN599"
-></A
->4.1.5.6. Chart::Base (optional)</H3
+NAME="AEN601">4.1.5.6. Chart::Base (optional)</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
><HR><H3
CLASS="section"
><A
-NAME="AEN602"
-></A
->4.1.5.7. Template Toolkit</H3
+NAME="AEN604">4.1.5.7. Template Toolkit</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
><HR><H2
CLASS="section"
><A
-NAME="AEN605"
-></A
->4.1.6. HTTP Server</H2
+NAME="AEN607">4.1.6. HTTP Server</H2
><P
>You have a freedom of choice here - Apache, Netscape or any other
server on UNIX would do. You can run the web server on a
><HR><H2
CLASS="section"
><A
-NAME="AEN624"
-></A
->4.1.7. Bugzilla</H2
+NAME="AEN626">4.1.7. Bugzilla</H2
><P
>You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
><HR><H2
CLASS="section"
><A
-NAME="AEN641"
-></A
->4.1.8. Setting Up the MySQL Database</H2
+NAME="AEN643">4.1.8. 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 the back end to
><HR><H2
CLASS="section"
><A
-NAME="AEN679"
-></A
->4.1.9. <TT
+NAME="AEN681">4.1.9. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><HR><H2
CLASS="section"
><A
-NAME="AEN711"
-></A
->4.1.10. Configuring Bugzilla</H2
+NAME="AEN713">4.1.10. Configuring Bugzilla</H2
><P
> You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
><HR><H1
CLASS="section"
><A
-NAME="extraconfig"
-></A
->4.2. Optional Additional Configuration</H1
+NAME="extraconfig">4.2. Optional Additional Configuration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="AEN717"
-></A
->4.2.1. Dependency Charts</H2
+NAME="AEN719">4.2.1. Dependency Charts</H2
><P
>As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
><HR><H2
CLASS="section"
><A
-NAME="AEN732"
-></A
->4.2.2. Bug Graphs</H2
+NAME="AEN734">4.2.2. Bug Graphs</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 graphs.</P
><HR><H2
CLASS="section"
><A
-NAME="AEN745"
-></A
->4.2.3. The Whining Cron</H2
+NAME="AEN747">4.2.3. The Whining Cron</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 more annoying you
><HR><H2
CLASS="section"
><A
-NAME="bzldap"
-></A
->4.2.4. LDAP Authentication</H2
+NAME="bzldap">4.2.4. LDAP Authentication</H2
><P
> <DIV
CLASS="warning"
><HR><H2
CLASS="section"
><A
-NAME="content-type"
-></A
->4.2.5. Preventing untrusted Bugzilla content from executing malicious
+NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
incorporate the code changes necessary to fulfill the CERT advisory
requirements mentioned in
<A
-HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
+HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3"
TARGET="_top"
> http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
>.
><HR><H2
CLASS="section"
><A
-NAME="htaccess"
-></A
->4.2.6. <TT
+NAME="htaccess">4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
><HR><H2
CLASS="section"
><A
-NAME="mod-throttle"
-></A
->4.2.7. <TT
+NAME="mod-throttle">4.2.7. <TT
CLASS="filename"
>mod_throttle</TT
>
><HR><H1
CLASS="section"
><A
-NAME="win32"
-></A
->4.3. Win32 Installation Notes</H1
+NAME="win32">4.3. Win32 Installation Notes</H1
><P
>This section covers installation on Microsoft Windows.
Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
><HR><H2
CLASS="section"
><A
-NAME="wininstall"
-></A
->4.3.1. Win32 Installation: Step-by-step</H2
+NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2
><DIV
CLASS="note"
><P
><DIV
CLASS="example"
><A
-NAME="AEN861"
-></A
-><P
+NAME="AEN863"><P
><B
>Example 4-1. Installing ActivePerl ppd Modules on Microsoft
Windows</B
<DIV
CLASS="example"
><A
-NAME="AEN874"
-></A
-><P
+NAME="AEN876"><P
><B
>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
><HR><H2
CLASS="section"
><A
-NAME="addlwintips"
-></A
->4.3.2. Additional Windows Tips</H2
+NAME="addlwintips">4.3.2. Additional Windows Tips</H2
><DIV
CLASS="tip"
><P
><P
>From Andrew Pearson:
<A
-NAME="AEN1044"
-></A
-><BLOCKQUOTE
+NAME="AEN1046"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>You can make Bugzilla work with Personal Web Server for
>
for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla 2.16.3.
+ Bugzilla 2.16.4.
<DIV
CLASS="example"
><A
-NAME="AEN1056"
-></A
-><P
+NAME="AEN1058"><P
><B
>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</B
><HR><H1
CLASS="section"
><A
-NAME="osx"
-></A
->4.4. Mac OS X Installation Notes</H1
+NAME="osx">4.4. Mac OS X Installation Notes</H1
><P
>There are a lot of common libraries and utilities out there that
Apple did not include with Mac OS X, but which run perfectly well on it.
><HR><H1
CLASS="section"
><A
-NAME="troubleshooting"
-></A
->4.5. Troubleshooting</H1
+NAME="troubleshooting">4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
><HR><H2
CLASS="section"
><A
-NAME="AEN1090"
-></A
->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
+NAME="AEN1092">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
> Try executing <B
CLASS="command"
><HR><H2
CLASS="section"
><A
-NAME="AEN1095"
-></A
->4.5.2. DBD::Sponge::db prepare failed</H2
+NAME="AEN1097">4.5.2. DBD::Sponge::db prepare failed</H2
><P
> The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
><HR><H2
CLASS="section"
><A
-NAME="paranoid-security"
-></A
->4.5.3. cannot chdir(/var/spool/mqueue)</H2
+NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE Linux, or some other
distributions with
><HR><H2
CLASS="section"
><A
-NAME="trouble-filetemp"
-></A
->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
+NAME="trouble-filetemp">4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2
><P
>This is caused by a bug in the version of
<SPAN
><DIV
CLASS="figure"
><A
-NAME="trouble-filetemp-errors"
-></A
-><P
+NAME="trouble-filetemp-errors"><P
><B
>Figure 4-1. Other File::Temp error messages</B
></P
><DIV
CLASS="figure"
><A
-NAME="trouble-filetemp-patch"
-></A
-><P
+NAME="trouble-filetemp-patch"><P
><B
>Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
></P
CLASS="chapter"
><HR><H1
><A
-NAME="administration"
-></A
->Chapter 5. Administering Bugzilla</H1
+NAME="administration">Chapter 5. Administering Bugzilla</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
-NAME="parameters"
-></A
->5.1. Bugzilla Configuration</H1
+NAME="parameters">5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
><HR><H1
CLASS="section"
><A
-NAME="useradmin"
-></A
->5.2. User Administration</H1
+NAME="useradmin">5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="defaultuser"
-></A
->5.2.1. Creating the Default User</H2
+NAME="defaultuser">5.2.1. Creating the Default User</H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email address) and
><HR><H2
CLASS="section"
><A
-NAME="manageusers"
-></A
->5.2.2. Managing Other Users</H2
+NAME="manageusers">5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
-NAME="createnewusers"
-></A
->5.2.2.1. Creating new users</H3
+NAME="createnewusers">5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
><HR><H3
CLASS="section"
><A
-NAME="modifyusers"
-></A
->5.2.2.2. Modifying Users</H3
+NAME="modifyusers">5.2.2.2. Modifying Users</H3
><P
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
><HR><H1
CLASS="section"
><A
-NAME="programadmin"
-></A
->5.3. Product, Component, Milestone, and Version Administration</H1
+NAME="programadmin">5.3. Product, Component, Milestone, and Version Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="products"
-></A
->5.3.1. Products</H2
+NAME="products">5.3.1. Products</H2
><P
> <A
HREF="#gloss-product"
><HR><H2
CLASS="section"
><A
-NAME="components"
-></A
->5.3.2. Components</H2
+NAME="components">5.3.2. Components</H2
><P
>Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
><HR><H2
CLASS="section"
><A
-NAME="versions"
-></A
->5.3.3. Versions</H2
+NAME="versions">5.3.3. Versions</H2
><P
>Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select
><HR><H2
CLASS="section"
><A
-NAME="milestones"
-></A
->5.3.4. Milestones</H2
+NAME="milestones">5.3.4. Milestones</H2
><P
>Milestones are "targets" that you plan to get a bug fixed by. For
example, you have a bug that you plan to fix for your 3.0 release, it
><HR><H1
CLASS="section"
><A
-NAME="voting"
-></A
->5.4. Voting</H1
+NAME="voting">5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
><HR><H1
CLASS="section"
><A
-NAME="groups"
-></A
->5.5. Groups and Group Security</H1
+NAME="groups">5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
><HR><H1
CLASS="section"
><A
-NAME="security"
-></A
->5.6. Bugzilla Security</H1
+NAME="security">5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
><HR><H2
CLASS="section"
><A
-NAME="security-networking"
-></A
->5.6.1. TCP/IP Ports</H2
+NAME="security-networking">5.6.1. TCP/IP Ports</H2
><P
>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla
only needs 1... 2 if you need to use features that require e-mail such
><HR><H2
CLASS="section"
><A
-NAME="security-mysql"
-></A
->5.6.2. MySQL</H2
+NAME="security-mysql">5.6.2. MySQL</H2
><P
>MySQL ships by default with many settings that should be changed.
By defaults it allows anybody to connect from localhost without a
><HR><H2
CLASS="section"
><A
-NAME="security-daemon"
-></A
->5.6.3. Daemon Accounts</H2
+NAME="security-daemon">5.6.3. Daemon Accounts</H2
><P
>Many daemons, such as Apache's httpd and MySQL's mysqld default to
running as either <SPAN
><HR><H2
CLASS="section"
><A
-NAME="security-access"
-></A
->5.6.4. Web Server Access Controls</H2
+NAME="security-access">5.6.4. Web Server Access Controls</H2
><P
>There are many files that are placed in the Bugzilla directory
area that should not be accessable from the web. Because of the way
><HR><H1
CLASS="section"
><A
-NAME="cust-templates"
-></A
->5.7. Template Customisation</H1
+NAME="cust-templates">5.7. Template Customisation</H1
><P
> One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
><HR><H2
CLASS="section"
><A
-NAME="AEN1532"
-></A
->5.7.1. What to Edit</H2
+NAME="AEN1534">5.7.1. What to Edit</H2
><P
> There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
></TR
></TABLE
></DIV
+><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
+>It is recommended that you run <B
+CLASS="command"
+>./checksetup.pl</B
+>
+ after any template edits, especially if you've created a new file in
+ the <TT
+CLASS="filename"
+>custom</TT
+> directory.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
-NAME="AEN1551"
-></A
->5.7.2. How To Edit Templates</H2
+NAME="AEN1557">5.7.2. How To Edit Templates</H2
><P
> The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
><HR><H2
CLASS="section"
><A
-NAME="AEN1561"
-></A
->5.7.3. Template Formats</H2
+NAME="AEN1567">5.7.3. Template Formats</H2
><P
> Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
><HR><H2
CLASS="section"
><A
-NAME="AEN1574"
-></A
->5.7.4. Particular Templates</H2
+NAME="AEN1580">5.7.4. Particular Templates</H2
><P
> There are a few templates you may be particularly interested in
customising for your installation.
><HR><H1
CLASS="section"
><A
-NAME="upgrading"
-></A
->5.8. Upgrading to New Releases</H1
+NAME="upgrading">5.8. Upgrading to New Releases</H1
><P
>Upgrading Bugzilla is something we all want to do from time to time,
be it to get new features or pick up the latest security fix. How easy
><DIV
CLASS="example"
><A
-NAME="upgrade-cvs"
-></A
-><P
+NAME="upgrade-cvs"><P
><B
>Example 5-1. Upgrading using CVS</B
></P
><DIV
CLASS="example"
><A
-NAME="upgrade-tarball"
-></A
-><P
+NAME="upgrade-tarball"><P
><B
>Example 5-2. Upgrading using the tarball</B
></P
><DIV
CLASS="example"
><A
-NAME="upgrade-patches"
-></A
-><P
+NAME="upgrade-patches"><P
><B
>Example 5-3. Upgrading using patches</B
></P
><HR><H1
CLASS="section"
><A
-NAME="integration"
-></A
->5.9. Integrating Bugzilla with Third-Party Tools</H1
+NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
-NAME="bonsai"
-></A
->5.9.1. Bonsai</H2
+NAME="bonsai">5.9.1. Bonsai</H2
><P
>Bonsai is a web-based tool for managing
<A
><HR><H2
CLASS="section"
><A
-NAME="cvs"
-></A
->5.9.2. CVS</H2
+NAME="cvs">5.9.2. CVS</H2
><P
>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.</P
><HR><H2
CLASS="section"
><A
-NAME="scm"
-></A
->5.9.3. Perforce SCM</H2
+NAME="scm">5.9.3. Perforce SCM</H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
><HR><H2
CLASS="section"
><A
-NAME="tinderbox"
-></A
->5.9.4. Tinderbox/Tinderbox2</H2
+NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
><P
>We need Tinderbox integration information.</P
></DIV
CLASS="appendix"
><HR><H1
><A
-NAME="faq"
-></A
->Appendix A. The Bugzilla FAQ</H1
+NAME="faq">Appendix A. The Bugzilla FAQ</H1
><P
> This FAQ includes questions not covered elsewhere in the Guide.
</P
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
+><DT
+>A.7.6. <A
+HREF="#faq-use-close"
+> Why can't I close bugs from the "Change Several Bugs at Once" page?
+ </A
+></DT
></DL
></DD
><DT
CLASS="qandadiv"
><H3
><A
-NAME="faq-general"
-></A
->1. General Questions</H3
+NAME="faq-general">1. General Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-general-information"
-></A
-><B
+NAME="faq-general-information"><B
>A.1.1. </B
>
Where can I find information about Bugzilla?</P
CLASS="question"
><P
><A
-NAME="faq-general-license"
-></A
-><B
+NAME="faq-general-license"><B
>A.1.2. </B
>
What license is Bugzilla distributed under?
CLASS="question"
><P
><A
-NAME="faq-general-support"
-></A
-><B
+NAME="faq-general-support"><B
>A.1.3. </B
>
How do I get commercial support for Bugzilla?
CLASS="question"
><P
><A
-NAME="faq-general-companies"
-></A
-><B
+NAME="faq-general-companies"><B
>A.1.4. </B
>
What major companies or projects are currently using Bugzilla
CLASS="question"
><P
><A
-NAME="faq-general-maintainers"
-></A
-><B
+NAME="faq-general-maintainers"><B
>A.1.5. </B
>
Who maintains Bugzilla?
TARGET="_top"
>core team</A
>,
- led by Dave Miller (justdave@netscape.com).
+ led by Dave Miller (justdave@bugzilla.org).
</P
></DIV
></DIV
CLASS="question"
><P
><A
-NAME="faq-general-compare"
-></A
-><B
+NAME="faq-general-compare"><B
>A.1.6. </B
>
How does Bugzilla stack up against other bug-tracking databases?
CLASS="question"
><P
><A
-NAME="faq-general-bzmissing"
-></A
-><B
+NAME="faq-general-bzmissing"><B
>A.1.7. </B
>
Why doesn't Bugzilla offer this or that feature or compatibility
CLASS="question"
><P
><A
-NAME="faq-general-mysql"
-></A
-><B
+NAME="faq-general-mysql"><B
>A.1.8. </B
>
Why MySQL? I'm interested in seeing Bugzilla run on
CLASS="question"
><P
><A
-NAME="faq-general-bonsaitools"
-></A
-><B
+NAME="faq-general-bonsaitools"><B
>A.1.9. </B
>
Why do the scripts say
CLASS="question"
><P
><A
-NAME="faq-general-cookie"
-></A
-><B
+NAME="faq-general-cookie"><B
>A.1.10. </B
>
Is there an easy way to change the Bugzilla cookie name?
CLASS="qandadiv"
><H3
><A
-NAME="faq-phb"
-></A
->2. Managerial Questions</H3
+NAME="faq-phb">2. Managerial Questions</H3
><P
> <DIV
CLASS="note"
CLASS="question"
><P
><A
-NAME="faq-phb-client"
-></A
-><B
+NAME="faq-phb-client"><B
>A.2.1. </B
>
Is Bugzilla web-based, or do you have to have specific software or
CLASS="question"
><P
><A
-NAME="faq-phb-integration"
-></A
-><B
+NAME="faq-phb-integration"><B
>A.2.2. </B
>
Can Bugzilla integrate with
CLASS="question"
><P
><A
-NAME="faq-phb-projects"
-></A
-><B
+NAME="faq-phb-projects"><B
>A.2.3. </B
>
Does Bugzilla allow the user to track multiple projects?
CLASS="question"
><P
><A
-NAME="faq-phb-sorting"
-></A
-><B
+NAME="faq-phb-sorting"><B
>A.2.4. </B
>
If I am on many projects, and search for all bugs assigned to me, will
CLASS="question"
><P
><A
-NAME="faq-phb-attachments"
-></A
-><B
+NAME="faq-phb-attachments"><B
>A.2.5. </B
>
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
CLASS="question"
><P
><A
-NAME="faq-phb-priorities"
-></A
-><B
+NAME="faq-phb-priorities"><B
>A.2.6. </B
>
Does Bugzilla allow us to define our own priorities and levels? Do we
CLASS="question"
><P
><A
-NAME="faq-phb-reporting"
-></A
-><B
+NAME="faq-phb-reporting"><B
>A.2.7. </B
>
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
CLASS="question"
><P
><A
-NAME="faq-phb-email"
-></A
-><B
+NAME="faq-phb-email"><B
>A.2.8. </B
>
Is there email notification and if so, what do you see when you get an
CLASS="question"
><P
><A
-NAME="faq-phb-cclist"
-></A
-><B
+NAME="faq-phb-cclist"><B
>A.2.9. </B
>
Can email notification be set up to send to multiple
CLASS="question"
><P
><A
-NAME="faq-phb-emailapp"
-></A
-><B
+NAME="faq-phb-emailapp"><B
>A.2.10. </B
>
Do users have to have any particular
CLASS="question"
><P
><A
-NAME="faq-phb-data"
-></A
-><B
+NAME="faq-phb-data"><B
>A.2.11. </B
>
Does Bugzilla allow data to be imported and exported? If I had outsiders
CLASS="question"
><P
><A
-NAME="faq-phb-l10n"
-></A
-><B
+NAME="faq-phb-l10n"><B
>A.2.12. </B
>
Has anyone converted Bugzilla to another language to be used in other
CLASS="question"
><P
><A
-NAME="faq-phb-reports"
-></A
-><B
+NAME="faq-phb-reports"><B
>A.2.13. </B
>
Can a user create and save reports? Can they do this in Word format?
CLASS="question"
><P
><A
-NAME="faq-phb-searching"
-></A
-><B
+NAME="faq-phb-searching"><B
>A.2.14. </B
>
Does Bugzilla have the ability to search by word, phrase, compound
CLASS="question"
><P
><A
-NAME="faq-phb-midair"
-></A
-><B
+NAME="faq-phb-midair"><B
>A.2.15. </B
>
Does Bugzilla provide record locking when there is simultaneous access
CLASS="question"
><P
><A
-NAME="faq-phb-backup"
-></A
-><B
+NAME="faq-phb-backup"><B
>A.2.16. </B
>
Are there any backup features provided?
CLASS="question"
><P
><A
-NAME="faq-phb-livebackup"
-></A
-><B
+NAME="faq-phb-livebackup"><B
>A.2.17. </B
>
Can users be on the system while a backup is in progress?
CLASS="question"
><P
><A
-NAME="faq-phb-maintenance"
-></A
-><B
+NAME="faq-phb-maintenance"><B
>A.2.18. </B
>
What type of human resources are needed to be on staff to install and
CLASS="question"
><P
><A
-NAME="faq-phb-installtime"
-></A
-><B
+NAME="faq-phb-installtime"><B
>A.2.19. </B
>
What time frame are we looking at if we decide to hire people to install
CLASS="question"
><P
><A
-NAME="faq-phb-cost"
-></A
-><B
+NAME="faq-phb-cost"><B
>A.2.20. </B
>
Is there any licensing fee or other fees for using Bugzilla? Any
CLASS="qandadiv"
><H3
><A
-NAME="faq-security"
-></A
->3. Bugzilla Security</H3
+NAME="faq-security">3. Bugzilla Security</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-security-mysql"
-></A
-><B
+NAME="faq-security-mysql"><B
>A.3.1. </B
>
How do I completely disable MySQL security if it's giving me problems
CLASS="question"
><P
><A
-NAME="faq-security-knownproblems"
-></A
-><B
+NAME="faq-security-knownproblems"><B
>A.3.2. </B
>
Are there any security problems with Bugzilla?
CLASS="question"
><P
><A
-NAME="faq-security-mysqluser"
-></A
-><B
+NAME="faq-security-mysqluser"><B
>A.3.3. </B
>
I've implemented the security fixes mentioned in Chris Yeh's security
CLASS="qandadiv"
><H3
><A
-NAME="faq-email"
-></A
->4. Bugzilla Email</H3
+NAME="faq-email">4. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-email-nomail"
-></A
-><B
+NAME="faq-email-nomail"><B
>A.4.1. </B
>
I have a user who doesn't want to receive any more email from Bugzilla.
CLASS="question"
><P
><A
-NAME="faq-email-testing"
-></A
-><B
+NAME="faq-email-testing"><B
>A.4.2. </B
>
I'm evaluating/testing Bugzilla, and don't want it to send email to
CLASS="question"
><P
><A
-NAME="faq-email-whine"
-></A
-><B
+NAME="faq-email-whine"><B
>A.4.3. </B
>
I want whineatnews.pl to whine at something more, or other than, only new
CLASS="question"
><P
><A
-NAME="faq-email-procmail"
-></A
-><B
+NAME="faq-email-procmail"><B
>A.4.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="AEN1973"
-></A
-><BLOCKQUOTE
+NAME="AEN1979"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
CLASS="question"
><P
><A
-NAME="faq-email-mailif"
-></A
-><B
+NAME="faq-email-mailif"><B
>A.4.5. </B
>
How do I set up the email interface to submit/change bugs via email?
CLASS="question"
><P
><A
-NAME="faq-email-sendmailnow"
-></A
-><B
+NAME="faq-email-sendmailnow"><B
>A.4.6. </B
>
Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
CLASS="question"
><P
><A
-NAME="faq-email-nonreceived"
-></A
-><B
+NAME="faq-email-nonreceived"><B
>A.4.7. </B
>
How come email from Bugzilla changes never reaches me?
CLASS="qandadiv"
><H3
><A
-NAME="faq-db"
-></A
->5. Bugzilla Database</H3
+NAME="faq-db">5. Bugzilla Database</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-db-oracle"
-></A
-><B
+NAME="faq-db-oracle"><B
>A.5.1. </B
>
I've heard Bugzilla can be used with Oracle?
CLASS="question"
><P
><A
-NAME="faq-db-corrupted"
-></A
-><B
+NAME="faq-db-corrupted"><B
>A.5.2. </B
>
I think my database might be corrupted, or contain invalid entries. What
CLASS="question"
><P
><A
-NAME="faq-db-manualedit"
-></A
-><B
+NAME="faq-db-manualedit"><B
>A.5.3. </B
>
I want to manually edit some entries in my database. How?
CLASS="question"
><P
><A
-NAME="faq-db-permissions"
-></A
-><B
+NAME="faq-db-permissions"><B
>A.5.4. </B
>
I think I've set up MySQL permissions correctly, but Bugzilla still can't
CLASS="question"
><P
><A
-NAME="faq-db-synchronize"
-></A
-><B
+NAME="faq-db-synchronize"><B
>A.5.5. </B
>
How do I synchronize bug information among multiple different Bugzilla
CLASS="qandadiv"
><H3
><A
-NAME="faq-nt"
-></A
->6. Bugzilla and Win32</H3
+NAME="faq-nt">6. Bugzilla and Win32</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-nt-easiest"
-></A
-><B
+NAME="faq-nt-easiest"><B
>A.6.1. </B
>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
CLASS="question"
><P
><A
-NAME="faq-nt-bundle"
-></A
-><B
+NAME="faq-nt-bundle"><B
>A.6.2. </B
>
Is there a "Bundle::Bugzilla" equivalent for Win32?
CLASS="question"
><P
><A
-NAME="faq-nt-mappings"
-></A
-><B
+NAME="faq-nt-mappings"><B
>A.6.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="AEN2049"
-></A
-><BLOCKQUOTE
+NAME="AEN2055"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> "Set application mappings. In the ISM, map the extension for the script
CLASS="question"
><P
><A
-NAME="faq-nt-dbi"
-></A
-><B
+NAME="faq-nt-dbi"><B
>A.6.4. </B
>
I'm having trouble with the perl modules for NT not being able to talk to
CLASS="qandadiv"
><H3
><A
-NAME="faq-use"
-></A
->7. Bugzilla Usage</H3
+NAME="faq-use">7. Bugzilla Usage</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-use-changeaddress"
-></A
-><B
+NAME="faq-use-changeaddress"><B
>A.7.1. </B
>
How do I change my user name (email address) in Bugzilla?
CLASS="question"
><P
><A
-NAME="faq-use-query"
-></A
-><B
+NAME="faq-use-query"><B
>A.7.2. </B
>
The query page is very confusing. Isn't there a simpler way to query?
CLASS="question"
><P
><A
-NAME="faq-use-accept"
-></A
-><B
+NAME="faq-use-accept"><B
>A.7.3. </B
>
I'm confused by the behavior of the "accept" button in the Show Bug form.
CLASS="question"
><P
><A
-NAME="faq-use-attachment"
-></A
-><B
+NAME="faq-use-attachment"><B
>A.7.4. </B
>
I can't upload anything into the database via the "Create Attachment"
CLASS="question"
><P
><A
-NAME="faq-use-keyword"
-></A
-><B
+NAME="faq-use-keyword"><B
>A.7.5. </B
>
How do I change a keyword in Bugzilla, once some bugs are using it?
</P
></DIV
></DIV
+><DIV
+CLASS="qandaentry"
+><DIV
+CLASS="question"
+><P
+><A
+NAME="faq-use-close"><B
+>A.7.6. </B
+>
+ Why can't I close bugs from the "Change Several Bugs at Once" page?
+ </P
+></DIV
+><DIV
+CLASS="answer"
+><P
+><B
+> </B
+>
+ The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
+ You <EM
+>can</EM
+> mass-CLOSE bugs from the change several
+ bugs at once page. <EM
+>but</EM
+>, every bug listed on the
+ page has to be in VERIFIED state before the control to do it will show
+ up on the form. You can also mass-VERIFY, but every bug listed has to be
+ RESOLVED in order for the control to show up on the form. The logic
+ behind this is that if you pick one of the bugs that's not VERIFIED and
+ try to CLOSE it, the bug change will fail miserably (thus killing any
+ changes in the list after it while doing the bulk change) so it doesn't
+ even give you the choice.
+ </P
+></DIV
+></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
-NAME="faq-hacking"
-></A
->8. Bugzilla Hacking</H3
+NAME="faq-hacking">8. Bugzilla Hacking</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
-NAME="faq-hacking-bugzillabugs"
-></A
-><B
+NAME="faq-hacking-bugzillabugs"><B
>A.8.1. </B
>
What bugs are in Bugzilla right now?
CLASS="question"
><P
><A
-NAME="faq-hacking-priority"
-></A
-><B
+NAME="faq-hacking-priority"><B
>A.8.2. </B
>
How can I change the default priority to a null value? For instance, have the default
CLASS="question"
><P
><A
-NAME="faq-hacking-patches"
-></A
-><B
+NAME="faq-hacking-patches"><B
>A.8.3. </B
>
What's the best way to submit patches? What guidelines should I follow?
CLASS="appendix"
><HR><H1
><A
-NAME="database"
-></A
->Appendix B. The Bugzilla Database</H1
+NAME="database">Appendix B. The Bugzilla Database</H1
><DIV
CLASS="note"
><P
><HR><H1
CLASS="section"
><A
-NAME="dbschema"
-></A
->B.1. Database Schema Chart</H1
+NAME="dbschema">B.1. Database Schema Chart</H1
><P
> <DIV
CLASS="mediaobject"
><HR><H1
CLASS="section"
><A
-NAME="dbdoc"
-></A
->B.2. MySQL Bugzilla Database Introduction</H1
+NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
><P
>This information comes straight from my life. I was forced to learn
how Bugzilla organizes database because of nitpicky requests from users
><HR><H2
CLASS="section"
><A
-NAME="AEN2162"
-></A
->B.2.1. Bugzilla Database Basics</H2
+NAME="AEN2175">B.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 executive order from
><HR><H3
CLASS="section"
><A
-NAME="AEN2189"
-></A
->B.2.1.1. Bugzilla Database Tables</H3
+NAME="AEN2202">B.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 command:</P
CLASS="appendix"
><HR><H1
><A
-NAME="patches"
-></A
->Appendix C. Useful Patches and Utilities for Bugzilla</H1
+NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
><P
>Are you looking for a way to put your Bugzilla into overdrive? Catch
some of the niftiest tricks here in this section.</P
><HR><H1
CLASS="section"
><A
-NAME="rewrite"
-></A
->C.1. Apache
+NAME="rewrite">C.1. Apache
<TT
CLASS="filename"
>mod_rewrite</TT
><HR><H1
CLASS="section"
><A
-NAME="cmdline"
-></A
->C.2. Command-line Bugzilla Queries</H1
+NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
><P
>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
CLASS="appendix"
><HR><H1
><A
-NAME="variants"
-></A
->Appendix D. Bugzilla Variants and Competitors</H1
+NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
><P
>I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of what
><HR><H1
CLASS="section"
><A
-NAME="variant-redhat"
-></A
->D.1. Red Hat Bugzilla</H1
+NAME="variant-redhat">D.1. Red Hat Bugzilla</H1
><P
>Red Hat's old fork of Bugzilla which was based on version 2.8 is now
obsolete. The newest version in use is based on version 2.17.1 and is in
><HR><H1
CLASS="section"
><A
-NAME="variant-fenris"
-></A
->D.2. Loki Bugzilla (Fenris)</H1
+NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
><HR><H1
CLASS="section"
><A
-NAME="variant-issuezilla"
-></A
->D.3. Issuezilla</H1
+NAME="variant-issuezilla">D.3. Issuezilla</H1
><P
>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
><HR><H1
CLASS="section"
><A
-NAME="variant-scarab"
-></A
->D.4. Scarab</H1
+NAME="variant-scarab">D.4. Scarab</H1
><P
>Scarab is a new open source bug-tracking system built using Java
Servlet technology. It is currently at version 1.0 beta 13.</P
><HR><H1
CLASS="section"
><A
-NAME="variant-perforce"
-></A
->D.5. Perforce SCM</H1
+NAME="variant-perforce">D.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used as
such through the <SPAN
><HR><H1
CLASS="section"
><A
-NAME="variant-sourceforge"
-></A
->D.6. SourceForge</H1
+NAME="variant-sourceforge">D.6. SourceForge</H1
><P
>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
CLASS="appendix"
><HR><H1
><A
-NAME="gfdl"
-></A
->Appendix E. GNU Free Documentation License</H1
+NAME="gfdl">Appendix E. GNU Free Documentation License</H1
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2277"
-></A
-><BLOCKQUOTE
+NAME="AEN2290"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
><HR><H1
CLASS="section"
><A
-NAME="gfdl-0"
-></A
->0. PREAMBLE</H1
+NAME="gfdl-0">0. PREAMBLE</H1
><P
>The purpose of this License is to make a manual, textbook, or other
written document "free" in the sense of freedom: to assure everyone the
><HR><H1
CLASS="section"
><A
-NAME="gfdl-1"
-></A
->1. APPLICABILITY AND DEFINITIONS</H1
+NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H1
><P
>This License applies to any manual or other work that contains a
notice placed by the copyright holder saying it can be distributed under
><HR><H1
CLASS="section"
><A
-NAME="gfdl-2"
-></A
->2. VERBATIM COPYING</H1
+NAME="gfdl-2">2. VERBATIM COPYING</H1
><P
>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
><HR><H1
CLASS="section"
><A
-NAME="gfdl-3"
-></A
->3. COPYING IN QUANTITY</H1
+NAME="gfdl-3">3. COPYING IN QUANTITY</H1
><P
>If you publish printed copies of the Document numbering more than
100, and the Document's license notice requires Cover Texts, you must
><HR><H1
CLASS="section"
><A
-NAME="gfdl-4"
-></A
->4. MODIFICATIONS</H1
+NAME="gfdl-4">4. MODIFICATIONS</H1
><P
>You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you release
><HR><H1
CLASS="section"
><A
-NAME="gfdl-5"
-></A
->5. COMBINING DOCUMENTS</H1
+NAME="gfdl-5">5. COMBINING DOCUMENTS</H1
><P
>You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for modified
><HR><H1
CLASS="section"
><A
-NAME="gfdl-6"
-></A
->6. COLLECTIONS OF DOCUMENTS</H1
+NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H1
><P
>You may make a collection consisting of the Document and other
documents released under this License, and replace the individual copies
><HR><H1
CLASS="section"
><A
-NAME="gfdl-7"
-></A
->7. AGGREGATION WITH INDEPENDENT WORKS</H1
+NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H1
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
><HR><H1
CLASS="section"
><A
-NAME="gfdl-8"
-></A
->8. TRANSLATION</H1
+NAME="gfdl-8">8. TRANSLATION</H1
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
><HR><H1
CLASS="section"
><A
-NAME="gfdl-9"
-></A
->9. TERMINATION</H1
+NAME="gfdl-9">9. TERMINATION</H1
><P
>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
><HR><H1
CLASS="section"
><A
-NAME="gfdl-10"
-></A
->10. FUTURE REVISIONS OF THIS LICENSE</H1
+NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H1
><P
>The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new versions
><HR><H1
CLASS="section"
><A
-NAME="gfdl-howto"
-></A
->How to use this License for your documents</H1
+NAME="gfdl-howto">How to use this License for your documents</H1
><P
>To use this License in a document you have written, include a copy
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
-NAME="AEN2367"
-></A
-><BLOCKQUOTE
+NAME="AEN2380"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
CLASS="GLOSSARY"
><H1
><A
-NAME="glossary"
-></A
->Glossary</H1
+NAME="glossary">Glossary</H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2372"
-></A
->0-9, high ascii</H1
+NAME="AEN2385">0-9, high ascii</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-a"
-></A
->A</H1
+NAME="gloss-a">A</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-b"
-></A
->B</H1
+NAME="gloss-b">B</H1
><DL
><DT
><B
></DD
><DT
><A
-NAME="gloss-bugzilla"
-></A
-><B
+NAME="gloss-bugzilla"><B
>Bugzilla</B
></DT
><DD
><H1
CLASS="glossdiv"
><A
-NAME="gloss-c"
-></A
->C</H1
+NAME="gloss-c">C</H1
><DL
><DT
><A
-NAME="gloss-cgi"
-></A
-><B
+NAME="gloss-cgi"><B
>Common Gateway Interface</B
></DT
> (CGI)<DD
></DD
><DT
><A
-NAME="gloss-component"
-></A
-><B
+NAME="gloss-component"><B
>Component</B
></DT
><DD
></DD
><DT
><A
-NAME="gloss-cpan"
-></A
-><B
+NAME="gloss-cpan"><B
> <SPAN
CLASS="acronym"
>CPAN</SPAN
><H1
CLASS="glossdiv"
><A
-NAME="gloss-d"
-></A
->D</H1
+NAME="gloss-d">D</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-g"
-></A
->G</H1
+NAME="gloss-g">G</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-m"
-></A
->M</H1
+NAME="gloss-m">M</H1
><DL
><DT
><A
-NAME="gloss-mta"
-></A
-><B
+NAME="gloss-mta"><B
>Message Transport Agent</B
></DT
> (MTA)<DD
></DD
><DT
><A
-NAME="gloss-mysql"
-></A
-><B
+NAME="gloss-mysql"><B
>MySQL</B
></DT
><DD
><H1
CLASS="glossdiv"
><A
-NAME="gloss-p"
-></A
->P</H1
+NAME="gloss-p">P</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-q"
-></A
->Q</H1
+NAME="gloss-q">Q</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-r"
-></A
->R</H1
+NAME="gloss-r">R</H1
><DL
><DT
><A
-NAME="gloss-rdbms"
-></A
-><B
+NAME="gloss-rdbms"><B
>Relational DataBase Managment System</B
></DT
> (RDBMS)<DD
><H1
CLASS="glossdiv"
><A
-NAME="gloss-s"
-></A
->S</H1
+NAME="gloss-s">S</H1
><DL
><DT
><B
><H1
CLASS="glossdiv"
><A
-NAME="gloss-t"
-></A
->T</H1
+NAME="gloss-t">T</H1
><DL
><DT
><A
-NAME="gloss-target-milestone"
-></A
-><B
+NAME="gloss-target-milestone"><B
>Target Milestone</B
></DT
><DD
></DD
><DT
><A
-NAME="gloss-tcl"
-></A
-><B
+NAME="gloss-tcl"><B
>Tool Command Language</B
></DT
> (TCL)<DD
><H1
CLASS="glossdiv"
><A
-NAME="gloss-z"
-></A
->Z</H1
+NAME="gloss-z">Z</H1
><DL
><DT
><A
-NAME="gloss-zarro"
-></A
-><B
+NAME="gloss-zarro"><B
>Zarro Boogs Found</B
></DT
><DD
Terry had the following to say:
</P
><A
-NAME="AEN2566"
-></A
-><TABLE
+NAME="AEN2579"><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
-The Bugzilla Guide - 2.16.3 Release
+The Bugzilla Guide - 2.16.4 ReleaseMatthew P. BarnsonThe Bugzilla Team
-Matthew P. Barnson
-
-The Bugzilla Team
-
- 2003-04-23
+2003-11-01
This is the documentation for Bugzilla, the mozilla.org bug-tracking
system. Bugzilla is an enterprise-class piece of software that powers
This documentation is maintained in DocBook 4.1.2 XML format. Changes
are best submitted as plain text or XML diffs, attached to a bug filed
in mozilla.org's Bugzilla.
- _________________________________________________________________
+
+ The most current version of this document can always be found on the
+ Bugzilla Documentation Page.
+ _______________________________________________________________________
Table of Contents
1. About This Guide
Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in Appendix E.
- --Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team
+--Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team
If you have any questions regarding this document, its copyright, or
publishing this document in non-electronic form, please contact The
1.2. Disclaimer
- No liability for the contents of this document can be accepted. Use
- the concepts, examples, and other content at your own risk. This
- document may contain errors and inaccuracies that may damage your
- system, cause your partner to leave you, your boss to fire you, your
- cats to pee on your furniture and clothing, and global thermonuclear
- war. Proceed with caution.
-
- All copyrights are held by their respective owners, unless
- specifically noted otherwise. Use of a term in this document should
- not be regarded as affecting the validity of any trademark or service
- mark.
-
- Naming of particular products or brands should not be seen as
- 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 environment for
- Bugzilla.
-
- You are strongly recommended to make a backup of your system before
- installing Bugzilla and at regular intervals thereafter. If you
- implement any suggestion in this Guide, implement this one!
-
- Although the Bugzilla development team has taken great care to ensure
- that all easily-exploitable bugs or options are documented or fixed in
- the code, security holes surely exist. Great care should be taken both
- in the installation and usage of this software. Carefully consider the
- implications of installing other network services with Bugzilla. The
- Bugzilla development team members, Netscape Communications, America
- Online Inc., and any affiliated developers or sponsors assume no
- liability for your use of this product. You have the source code to
- this product, and are responsible for auditing it yourself to ensure
- your security needs are met.
+No liability for the contents of this document can be accepted. Use the
+concepts, examples, and other content at your own risk. This document may
+contain errors and inaccuracies that may damage your system, cause your
+partner to leave you, your boss to fire you, your cats to pee on your
+furniture and clothing, and global thermonuclear war. Proceed with caution.
+
+All copyrights are held by their respective owners, unless specifically
+noted otherwise. Use of a term in this document should not be regarded as
+affecting the validity of any trademark or service mark.
+
+Naming of particular products or brands should not be seen as 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 environment for Bugzilla.
+
+You are strongly recommended to make a backup of your system before
+installing Bugzilla and at regular intervals thereafter. If you implement
+any suggestion in this Guide, implement this one!
+
+Although the Bugzilla development team has taken great care to ensure that
+all easily-exploitable bugs or options are documented or fixed in the code,
+security holes surely exist. Great care should be taken both in the
+installation and usage of this software. Carefully consider the implications
+of installing other network services with Bugzilla. The Bugzilla development
+team members, Netscape Communications, America Online Inc., and any
+affiliated developers or sponsors assume no liability for your use of this
+product. You have the source code to this product, and are responsible for
+auditing it yourself to ensure your security needs are met.
_________________________________________________________________
1.3. New Versions
- This is the 2.16.3 version of The Bugzilla Guide. It is so named to
- match the version of Bugzilla it is disributed with. 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.
+This is the 2.16.4 version of The Bugzilla Guide. It is so named to match
+the version of Bugzilla it is disributed with. 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.
- The newest version of this guide can always be found at bugzilla.org;
- including documentation for past releases and the current development
- version.
+The newest version of this guide can always be found at bugzilla.org;
+including documentation for past releases and the current development
+version.
- The documentation for the most recent stable release of Bugzilla can
- also be found at The Linux Documentation Project.
+The documentation for the most recent stable release of Bugzilla can also be
+found at The Linux Documentation Project.
- The latest version of this document can always be checked out via CVS.
- Please follow the instructions available at the Mozilla CVS page, and
- check out the mozilla/webtools/bugzilla/docs/ subtree.
+The latest version of this document can always be checked out via CVS.
+Please follow the instructions available at the Mozilla CVS page, and check
+out the mozilla/webtools/bugzilla/docs/ subtree.
- The Bugzilla Guide is currently only available in English. If you
- would like to volunteer to translate it, please contact Dave Miller.
+The Bugzilla Guide is currently only available in English. If you would like
+to volunteer to translate it, please contact Dave Miller.
_________________________________________________________________
1.4. Credits
- The people listed below have made enormous contributions to the
- creation of this Guide, through their writing, dedicated hacking
- efforts, numerous e-mail and IRC support sessions, and overall
- excellent contribution to the Bugzilla community:
+The people listed below have made enormous contributions to the creation of
+this Guide, through their writing, dedicated hacking efforts, numerous
+e-mail and IRC support sessions, and overall excellent contribution to the
+Bugzilla community:
Matthew P. Barnson <mbarnson@sisna.com>
for the Herculaean task of pulling together the Bugzilla Guide
1.5. Document Conventions
- This document uses the following conventions:
+This document uses the following conventions:
Descriptions Appearance
Use caution
2.1. What is Bugzilla?
- Bugzilla is a bug- or issue-tracking system. Bug-tracking systems
- allow individual or groups of developers effectively to keep track of
- outstanding problems with their product. Bugzilla was originally
- written by Terry Weissman in a programming language called TCL, to
- replace a rudimentary 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 licensing fees, and
- Bugzilla quickly became a favorite of the open-source crowd (with its
- genesis in the open-source browser project, Mozilla). It is now the
- de-facto standard defect-tracking system against which all others are
- measured.
-
- Bugzilla boasts many advanced features. These include:
+Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow
+individual or groups of developers effectively to keep track of outstanding
+problems with their product. Bugzilla was originally written by Terry
+Weissman in a programming language called TCL, to replace a rudimentary
+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 licensing fees, and Bugzilla quickly became a favorite of the
+open-source crowd (with its genesis in the open-source browser project,
+Mozilla). It is now the de-facto standard defect-tracking system against
+which all others are measured.
+
+Bugzilla boasts many advanced features. These include:
* Powerful searching
* User-configurable email notifications of bug changes
2.2. Why Should We Use Bugzilla?
- For many years, defect-tracking software has remained principally the
- domain of large software development houses. Even then, most shops
- never bothered with bug-tracking software, and instead simply relied
- on shared lists and email to monitor the status of defects. This
- procedure is error-prone and tends to cause those bugs judged least
- significant by developers to be dropped or ignored.
-
- These days, many companies are finding that integrated defect-tracking
- systems reduce downtime, increase productivity, and raise customer
- satisfaction with their systems. Along with full disclosure, an open
- bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout
- the data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support
- accountability, telephone support knowledge bases, and a common,
- well-understood system for accounting for unusual system or software
- issues.
-
- But why should you use Bugzilla?
-
- Bugzilla is very adaptable to various situations. Known uses currently
- include IT support queues, Systems Administration deployment
- management, chip design and development problem tracking (both
- pre-and-post fabrication), and software and hardware bug tracking for
- luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
- provides a powerful, easy-to-use solution to configuration management
- and replication problems.
-
- Bugzilla can dramatically increase the productivity and accountability
- of individual employees by providing a documented workflow and
- positive feedback for good performance. How many times do you wake up
- in the morning, remembering that you were supposed to do something
- today, but you just can't quite remember? Put it in Bugzilla, and you
- have a record of it from which you can extrapolate milestones, predict
- product versions for integration, and follow the discussion trail that
- led to critical decisions.
-
- Ultimately, Bugzilla puts the power in your hands to improve your
- value to your employer or business while providing a usable framework
- for your natural attention to detail and knowledge store to flourish.
+For many years, defect-tracking software has remained principally the domain
+of large software development houses. Even then, most shops never bothered
+with bug-tracking software, and instead simply relied on shared lists and
+email to monitor the status of defects. This procedure is error-prone and
+tends to cause those bugs judged least significant by developers to be
+dropped or ignored.
+
+These days, many companies are finding that integrated defect-tracking
+systems reduce downtime, increase productivity, and raise customer
+satisfaction with their systems. Along with full disclosure, an open
+bug-tracker allows manufacturers to keep in touch with their clients and
+resellers, to communicate about problems effectively throughout the data
+management chain. Many corporations have also discovered that
+defect-tracking helps reduce costs by providing IT support accountability,
+telephone support knowledge bases, and a common, well-understood system for
+accounting for unusual system or software issues.
+
+But why should you use Bugzilla?
+
+Bugzilla is very adaptable to various situations. Known uses currently
+include IT support queues, Systems Administration deployment management,
+chip design and development problem tracking (both pre-and-post
+fabrication), and software and hardware bug tracking for luminaries such as
+Redhat, NASA, Linux-Mandrake, and VA Systems. Combined with systems such as
+CVS, Bonsai, or Perforce SCM, Bugzilla provides a powerful, easy-to-use
+solution to configuration management and replication problems.
+
+Bugzilla can dramatically increase the productivity and accountability of
+individual employees by providing a documented workflow and positive
+feedback for good performance. How many times do you wake up in the morning,
+remembering that you were supposed to do something today, but you just can't
+quite remember? Put it in Bugzilla, and you have a record of it from which
+you can extrapolate milestones, predict product versions for integration,
+and follow the discussion trail that led to critical decisions.
+
+Ultimately, Bugzilla puts the power in your hands to improve your value to
+your employer or business while providing a usable framework for your
+natural attention to detail and knowledge store to flourish.
_________________________________________________________________
Chapter 3. Using Bugzilla
3.1. How do I use Bugzilla?
- This section contains information for end-users of Bugzilla. There is
- a Bugzilla test installation, called Landfill, which you are welcome
- to play with (if it's up.) 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.
+This section contains information for end-users of Bugzilla. There is a
+Bugzilla test installation, called Landfill, which you are welcome to play
+with (if it's up.) 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.
_________________________________________________________________
3.1.1. Create a Bugzilla Account
- 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 Bugzilla, use this URL:
- http://landfill.bugzilla.org/bugzilla-tip/
+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 Bugzilla, use this
+URL: http://landfill.bugzilla.org/bugzilla-tip/
1. Click the "Open a new Bugzilla account" link, enter your email
address and, optionally, your name in the spaces provided, then
3.1.2. Anatomy of a Bug
- The core of Bugzilla is the screen which displays a particular bug.
- It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill
- is a good example. Note that the labels for most fields are
- hyperlinks; clicking them will take you to context-sensitive help on
- that particular field. Fields marked * may not be present on every
- installation of Bugzilla.
+The core of Bugzilla is the screen which displays a particular bug. It's a
+good place to explain some Bugzilla concepts. Bug 1 on Landfill is a good
+example. Note that the labels for most fields are hyperlinks; clicking them
+will take you to context-sensitive help on that particular field. Fields
+marked * may not be present on every installation of Bugzilla.
1. Product and Component: Bugs are divided up by Product and
Component, with a Product having one or more Components in it. For
3.1.3. Searching for Bugs
- 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: landfill.bugzilla.org/bugzilla-tip/query.cgi .
+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: landfill.bugzilla.org/bugzilla-tip/query.cgi .
- 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.
+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.
- Highly advanced querying is done using Boolean Charts, which have
- their own context-sensitive help .
+Highly advanced querying is done using Boolean Charts, which have their own
+context-sensitive help .
_________________________________________________________________
3.1.4. Bug Lists
- 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!
+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!
- 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:
+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:
Long Format: this gives you a large page with a non-editable summary
of the fields of each bug.
- Change Columns: change the bug attributes which appear in the list.
+Change Columns: change the bug attributes which appear in the list.
Change several bugs at once: If your account is sufficiently
empowered, you can make the same change to all the bugs in the list -
for example, changing their owner.
3.1.5. Filing Bugs
- Years of bug writing experience has been distilled for your reading
- pleasure into the Bug Writing Guidelines. 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.
+Years of bug writing experience has been distilled for your reading pleasure
+into the Bug Writing Guidelines. 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.
- The procedure for filing a test bug is as follows:
+The procedure for filing a test bug is as follows:
1. Go to Landfill in your browser and click Enter a new bug report.
2. Select a product - any one will do.
3.2. Hints and Tips
- This section distills some Bugzilla tips and best practices that have
- been developed.
+This section distills some Bugzilla tips and best practices that have been
+developed.
_________________________________________________________________
3.2.1. Autolinkification
- Bugzilla comments are plain text - so posting HTML will result in
- literal HTML tags rather than being interpreted by a browser. However,
- Bugzilla will automatically make hyperlinks out of certain sorts of
- text in comments. For example, the text http://www.bugzilla.org will
- be turned into http://www.bugzilla.org. Other strings which get
- linkified in the obvious manner are:
-
- bug 12345
- bug 23456, comment 53
- attachment 4321
- mailto:george@example.com
- george@example.com
- ftp://ftp.mozilla.org
- Most other sorts of URL
+Bugzilla comments are plain text - so posting HTML will result in literal
+HTML tags rather than being interpreted by a browser. However, Bugzilla will
+automatically make hyperlinks out of certain sorts of text in comments. For
+example, the text http://www.bugzilla.org will be turned into
+http://www.bugzilla.org. Other strings which get linkified in the obvious
+manner are:
+
+bug 12345
+bug 23456, comment 53
+attachment 4321
+mailto:george@example.com
+george@example.com
+ftp://ftp.mozilla.org
+Most other sorts of URL
A corollary here is that if you type a bug number in a comment, you
should put the word "bug" before it, so it gets autolinkified for the
3.2.2. Quicksearch
- Quicksearch is a single-text-box query tool which uses metacharacters
- to indicate what is to be searched. For example, typing "foo|bar" into
- Quicksearch would search for "foo" or "bar" in the summary and status
- whiteboard of a bug; adding ":BazProduct" would search only in that
- product.
+Quicksearch is a single-text-box query tool which uses metacharacters to
+indicate what is to be searched. For example, typing "foo|bar" into
+Quicksearch would search for "foo" or "bar" in the summary and status
+whiteboard of a bug; adding ":BazProduct" would search only in that product.
- You'll find the Quicksearch box on Bugzilla's front page, along with a
- Help link which details how to use it.
+You'll find the Quicksearch box on Bugzilla's front page, along with a Help
+link which details how to use it.
_________________________________________________________________
3.2.3. Comments
- If you are changing the fields on a bug, only comment if either you
- have something pertinent to say, or Bugzilla requires it. Otherwise,
- you may spam people unnecessarily with bug mail. To take an example: a
- user can set up their account to filter out messages where someone
- just adds themselves to the CC field of a bug (which happens a lot.)
- If you come along, add yourself to the CC field, and add a comment
- saying "Adding self to CC", then that person gets a pointless piece of
- mail they would otherwise have avoided.
-
- Don't use sigs in comments. Signing your name ("Bill") is acceptable,
- particularly if you do it out of habit, but full mail/news-style four
- line ASCII art creations are not.
+If you are changing the fields on a bug, only comment if either you have
+something pertinent to say, or Bugzilla requires it. Otherwise, you may spam
+people unnecessarily with bug mail. To take an example: a user can set up
+their account to filter out messages where someone just adds themselves to
+the CC field of a bug (which happens a lot.) If you come along, add yourself
+to the CC field, and add a comment saying "Adding self to CC", then that
+person gets a pointless piece of mail they would otherwise have avoided.
+
+Don't use sigs in comments. Signing your name ("Bill") is acceptable,
+particularly if you do it out of habit, but full mail/news-style four line
+ASCII art creations are not.
_________________________________________________________________
3.2.4. Attachments
- Use attachments, rather than comments, for large chunks of ASCII data,
- such as trace, debugging output files, or log files. That way, it
- doesn't bloat the bug for everyone who wants to read it, and cause
- people to receive fat, useless mails.
+Use attachments, rather than comments, for large chunks of ASCII data, such
+as trace, debugging output files, or log files. That way, it doesn't bloat
+the bug for everyone who wants to read it, and cause people to receive fat,
+useless mails.
- Trim screenshots. There's no need to show the whole screen if you are
- pointing out a single-pixel problem.
+Trim screenshots. There's no need to show the whole screen if you are
+pointing out a single-pixel problem.
- Don't attach simple test cases (e.g. one HTML file, one CSS file and
- an image) as a ZIP file. Instead, upload them in reverse order and
- edit the referring file so that they point to the attached files. This
- way, the test case works immediately out of the bug.
+Don't attach simple test cases (e.g. one HTML file, one CSS file and an
+image) as a ZIP file. Instead, upload them in reverse order and edit the
+referring file so that they point to the attached files. This way, the test
+case works immediately out of the bug.
_________________________________________________________________
3.2.5. Filing Bugs
- Try to make sure that everything said in the summary is also said in
- the first comment. Summaries are often updated and this will ensure
- your original information is easily accessible.
+Try to make sure that everything said in the summary is also said in the
+first comment. Summaries are often updated and this will ensure your
+original information is easily accessible.
- You do not need to put "any" or similar strings in the URL field. If
- there is no specific URL associated with the bug, leave this field
- blank.
+You do not need to put "any" or similar strings in the URL field. If there
+is no specific URL associated with the bug, leave this field blank.
- If you feel a bug you filed was incorrectly marked as a DUPLICATE of
- another, please question it in your bug, not the bug it was duped to.
- Feel free to CC the person who duped it if they are not already CCed.
+If you feel a bug you filed was incorrectly marked as a DUPLICATE of
+another, please question it in your bug, not the bug it was duped to. Feel
+free to CC the person who duped it if they are not already CCed.
_________________________________________________________________
3.3. User Preferences
- Once you have logged in, you can customise various aspects of Bugzilla
- via the "Edit prefs" link in the page footer. The preferences are
- split into four tabs:
+Once you have logged in, you can customise various aspects of Bugzilla via
+the "Edit prefs" link in the page footer. The preferences are split into
+four tabs:
_________________________________________________________________
3.3.1. Account Settings
- On this tab, you can change your basic account information, including
- your password, email address and real name. For security reasons, in
- order to change anything on this page you must type your current
- password into the "Password" field at the top of the page. If you
- attempt to change your email address, a confirmation email is sent to
- both the old and new addresses, with a link to use to confirm the
- change. This helps to prevent account hijacking.
+On this tab, you can change your basic account information, including your
+password, email address and real name. For security reasons, in order to
+change anything on this page you must type your current password into the
+"Password" field at the top of the page. If you attempt to change your email
+address, a confirmation email is sent to both the old and new addresses,
+with a link to use to confirm the change. This helps to prevent account
+hijacking.
_________________________________________________________________
3.3.2. Email Settings
- On this tab you can reduce or increase the amount of email sent you
- from Bugzilla, opting in our out depending on your relationship to the
- bug and the change that was made to it. (Note that you can also do
- client-side filtering using the X-Bugzilla-Reason header which
- Bugzilla adds to all bugmail.)
+On this tab you can reduce or increase the amount of email sent you from
+Bugzilla, opting in our out depending on your relationship to the bug and
+the change that was made to it. (Note that you can also do client-side
+filtering using the X-Bugzilla-Reason header which Bugzilla adds to all
+bugmail.)
- By entering user email names, delineated by commas, into the "Users to
- watch" text entry box you can receive a copy of all the bugmail of
- other users (security settings permitting.) This powerful
- functionality enables seamless transitions as developers change
- projects or users go on holiday.
+By entering user email names, delineated by commas, into the "Users to
+watch" text entry box you can receive a copy of all the bugmail of other
+users (security settings permitting.) This powerful functionality enables
+seamless transitions as developers change projects or users go on holiday.
Note
3.3.3. Page Footer
- On the Search page, you can store queries in Bugzilla, so if you
- regularly run a particular query it is just a drop-down menu away.
- Once you have a stored query, you can come here to request that it
- also be displayed in your page footer.
+On the Search page, you can store queries in Bugzilla, so if you regularly
+run a particular query it is just a drop-down menu away. Once you have a
+stored query, you can come here to request that it also be displayed in your
+page footer.
_________________________________________________________________
3.3.4. Permissions
- This is a purely informative page which outlines your current
- permissions on this installation of Bugzilla - what product groups you
- are in, and whether you can edit bugs or perform various
- administration functions.
+This is a purely informative page which outlines your current permissions on
+this installation of Bugzilla - what product groups you are in, and whether
+you can edit bugs or perform various administration functions.
_________________________________________________________________
Chapter 4. Installation
4.1.1. Introduction
- Bugzilla has been successfully installed under Solaris, Linux, and
- Win32. Win32 is not yet officially supported, but many people have got
- it working fine. Please see the Win32 Installation Notes for further
- advice on getting Bugzilla to work on Microsoft Windows.
+Bugzilla has been successfully installed under Solaris, Linux, and Win32.
+Win32 is not yet officially supported, but many people have got it working
+fine. Please see the Win32 Installation Notes for further advice on getting
+Bugzilla to work on Microsoft Windows.
_________________________________________________________________
4.1.2. Package List
4.1.3. MySQL
- Visit the MySQL homepage at www.mysql.com to grab and install the
- latest stable release of the server.
+Visit the MySQL homepage at www.mysql.com to grab and install the latest
+stable release of the server.
Note
4.1.4. Perl
- Any machine that doesn't have Perl on it is a sad machine indeed. Perl
- can be got in source form from perl.com for the rare *nix systems
- which don't have it. Although Bugzilla runs with all post-5.005
- versions of Perl, it's a good idea to be up to the very latest version
- if you can when running Bugzilla. As of this writing, that is Perl
- version 5.6.1.
+Any machine that doesn't have Perl on it is a sad machine indeed. Perl can
+be got in source form from perl.com for the rare *nix systems which don't
+have it. Although Bugzilla runs with all post-5.005 versions of Perl, it's a
+good idea to be up to the very latest version if you can when running
+Bugzilla. As of this writing, that is Perl version 5.6.1.
Tip
4.1.5. Perl Modules
- All Perl modules can be found on the Comprehensive Perl Archive
- Network (CPAN). The CPAN servers have a real tendency to bog down, so
- please use mirrors.
+All Perl modules can be found on the Comprehensive Perl Archive Network
+(CPAN). The CPAN servers have a real tendency to bog down, so please use
+mirrors.
- Quality, general Perl module installation instructions can be found on
- the CPAN website, but the easy thing to do is to just use the CPAN
- shell which does all the hard work for you. To use the CPAN shell to
- install a module:
+Quality, general Perl module installation instructions can be found on the
+CPAN website, but the easy thing to do is to just use the CPAN shell which
+does all the hard work for you. To use the CPAN shell to install a module:
- bash# perl -MCPAN -e 'install "<modulename>"'
+bash# perl -MCPAN -e 'install "<modulename>"'
- To do it the hard way:
+To do it the hard way:
- Untar the module tarball -- it should create its own directory
+Untar the module tarball -- it should create its own directory
- CD to the directory just created, and enter the following commands:
+CD to the directory just created, and enter the following commands:
1. bash# perl Makefile.PL
2. bash# make
4.1.5.1. DBI
- The DBI module is a generic Perl module used the MySQL-related
- modules. As long as your Perl installation was done correctly the DBI
- module should be a breeze. It's a mixed Perl/C module, but Perl's
- MakeMaker system simplifies the C compilation greatly.
+The DBI module is a generic Perl module used the MySQL-related modules. As
+long as your Perl installation was done correctly the DBI module should be a
+breeze. It's a mixed Perl/C module, but Perl's MakeMaker system simplifies
+the C compilation greatly.
_________________________________________________________________
4.1.5.2. Data::Dumper
- The Data::Dumper module provides data structure persistence for Perl
- (similar to Java's serialization). It comes with later sub-releases of
- Perl 5.004, but a re-installation just to be sure it's available won't
- hurt anything.
+The Data::Dumper module provides data structure persistence for Perl
+(similar to Java's serialization). It comes with later sub-releases of Perl
+5.004, but a re-installation just to be sure it's available won't hurt
+anything.
_________________________________________________________________
4.1.5.3. MySQL-related modules
- The Perl/MySQL interface requires a few mutually-dependent Perl
- modules. These modules are grouped together into the the
- Msql-Mysql-modules package.
-
- The MakeMaker process will ask you a few questions about the desired
- compilation target and your MySQL installation. For most of the
- questions the provided default will be adequate, but when asked if
- your desired target is the MySQL or mSQL packages, you should select
- the MySQL related ones. Later you will be asked if you wish to provide
- backwards compatibility with the older MySQL packages; you should
- answer YES to this question. The default is NO.
-
- A host of 'localhost' should be fine and a testing user of 'test' with
- a null password should find itself with sufficient access to run tests
- on the 'test' database which MySQL created upon installation.
+The Perl/MySQL interface requires a few mutually-dependent Perl modules.
+These modules are grouped together into the the Msql-Mysql-modules package.
+
+The MakeMaker process will ask you a few questions about the desired
+compilation target and your MySQL installation. For most of the questions
+the provided default will be adequate, but when asked if your desired target
+is the MySQL or mSQL packages, you should select the MySQL related ones.
+Later you will be asked if you wish to provide backwards compatibility with
+the older MySQL packages; you should answer YES to this question. The
+default is NO.
+
+A host of 'localhost' should be fine and a testing user of 'test' with a
+null password should find itself with sufficient access to run tests on the
+'test' database which MySQL created upon installation.
_________________________________________________________________
4.1.5.4. TimeDate modules
- Many of the more common date/time/calendar related Perl modules have
- been grouped into a bundle similar to the MySQL modules bundle. This
- bundle is stored on the CPAN under the name TimeDate. The component
- module we're most interested in is the Date::Format module, but
- installing all of them is probably a good idea anyway.
+Many of the more common date/time/calendar related Perl modules have been
+grouped into a bundle similar to the MySQL modules bundle. This bundle is
+stored on the CPAN under the name TimeDate. The component module we're most
+interested in is the Date::Format module, but installing all of them is
+probably a good idea anyway.
_________________________________________________________________
4.1.5.5. GD (optional)
- The GD library was written by Thomas Boutell a long while ago to
- programatically generate images in C. Since then it's become the
- defacto standard for programatic image construction. The Perl bindings
- to it found in the GD library are used on millions of web pages to
- generate graphs on the fly. That's what Bugzilla will be using it for
- so you must install it if you want any of the graphing to work.
+The GD library was written by Thomas Boutell a long while ago to
+programatically generate images in C. Since then it's become the defacto
+standard for programatic image construction. The Perl bindings to it found
+in the GD library are used on millions of web pages to generate graphs on
+the fly. That's what Bugzilla will be using it for so you must install it if
+you want any of the graphing to work.
Note
4.1.5.6. Chart::Base (optional)
- The Chart module provides Bugzilla with on-the-fly charting abilities.
- It can be installed in the usual fashion after it has been fetched
- from CPAN. Note that earlier versions that 0.99c used GIFs, which are
- no longer supported by the latest versions of GD.
+The Chart module provides Bugzilla with on-the-fly charting abilities. It
+can be installed in the usual fashion after it has been fetched from CPAN.
+Note that earlier versions that 0.99c used GIFs, which are no longer
+supported by the latest versions of GD.
_________________________________________________________________
4.1.5.7. Template Toolkit
- When you install Template Toolkit, you'll get asked various questions
- about features to enable. The defaults are fine, except that it is
- recommended you use the high speed XS Stash of the Template Toolkit,
- in order to achieve best performance. However, there are known
- problems with XS Stash and Perl 5.005_02 and lower. If you wish to use
- these older versions of Perl, please use the regular stash.
+When you install Template Toolkit, you'll get asked various questions about
+features to enable. The defaults are fine, except that it is recommended you
+use the high speed XS Stash of the Template Toolkit, in order to achieve
+best performance. However, there are known problems with XS Stash and Perl
+5.005_02 and lower. If you wish to use these older versions of Perl, please
+use the regular stash.
_________________________________________________________________
4.1.6. HTTP Server
- You have a freedom of choice here - Apache, Netscape or any other
- server on UNIX would do. You can run the web server on a different
- machine than MySQL, but need to adjust the MySQL "bugs" user
- permissions accordingly.
+You have a freedom of choice here - Apache, Netscape or any other server on
+UNIX would do. You can run the web server on a different machine than MySQL,
+but need to adjust the MySQL "bugs" user permissions accordingly.
Note
4.1.7. Bugzilla
- You should untar the Bugzilla files into a directory that you're
- willing to make writable by the default web server user (probably
- "nobody"). You may decide to put the files in the main web space for
- your web server or perhaps in /usr/local with a symbolic link in the
- web space that points to the Bugzilla directory.
+You should untar the Bugzilla files into a directory that you're willing to
+make writable by the default web server user (probably "nobody"). You may
+decide to put the files in the main web space for your web server or perhaps
+in /usr/local with a symbolic link in the web space that points to the
+Bugzilla directory.
Tip
4.1.8. Setting Up the MySQL Database
- After you've gotten all the software installed and working you're
- ready to start preparing the database for its life as the back end to
- a high quality bug tracker.
+After you've gotten all the software installed and working you're ready to
+start preparing the database for its life as the back end to a high quality
+bug tracker.
- First, you'll want to fix MySQL permissions to allow access from
- Bugzilla. For the purpose of this Installation section, the Bugzilla
- username will be "bugs", and will have minimal permissions.
+First, you'll want to fix MySQL permissions to allow access from Bugzilla.
+For the purpose of this Installation section, the Bugzilla username will be
+"bugs", and will have minimal permissions.
- Begin by giving the MySQL root user a password. MySQL passwords are
- limited to 16 characters.
+Begin by giving the MySQL root user a password. MySQL passwords are limited
+to 16 characters.
- bash# mysql -u root mysql
+bash# mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD('<new_password>') WHERE
user='root';
- mysql> FLUSH PRIVILEGES;
+mysql> FLUSH PRIVILEGES;
From this point on, if you need to access MySQL as the MySQL root
user, you will need to use mysql -u root -p and enter <new_password>.
4.1.9. checksetup.pl
- Next, run the magic checksetup.pl script. (Many thanks to Holger
- Schurig for writing this script!) This script is designed to make sure
- your MySQL database and other configuration options are consistent
- with the Bugzilla CGI files. It will make sure Bugzilla files and
- directories have reasonable permissions, set up the data directory,
- and create all the MySQL tables.
+Next, run the magic checksetup.pl script. (Many thanks to Holger Schurig for
+writing this script!) This script is designed to make sure your MySQL
+database and other configuration options are consistent with the Bugzilla
+CGI files. It will make sure Bugzilla files and directories have reasonable
+permissions, set up the data directory, and create all the MySQL tables.
- bash# ./checksetup.pl
+bash# ./checksetup.pl
The first time you run it, it will create a file called localconfig.
4.1.10. Configuring Bugzilla
- You should run through the parameters on the Edit Parameters page
- (link in the footer) and set them all to appropriate values. They key
- parameters are documented in Section 5.1.
+You should run through the parameters on the Edit Parameters page (link in
+the footer) and set them all to appropriate values. They key parameters are
+documented in Section 5.1.
_________________________________________________________________
4.2. Optional Additional Configuration
4.2.1. Dependency Charts
- As well as the text-based dependency graphs, Bugzilla also supports
- dependency graphing, using a package called 'dot'. Exactly how this
- works is controlled by the 'webdotbase' parameter, which can have one
- of three values:
+As well as the text-based dependency graphs, Bugzilla also supports
+dependency graphing, using a package called 'dot'. Exactly how this works is
+controlled by the 'webdotbase' parameter, which can have one of three
+values:
1. A complete file path to the command 'dot' (part of GraphViz) will
generate the graphs locally
4.2.2. Bug Graphs
- As long as you installed the GD and Graph::Base Perl modules you might
- as well turn on the nifty Bugzilla bug reporting graphs.
+As long as you installed the GD and Graph::Base Perl modules you might as
+well turn on the nifty Bugzilla bug reporting graphs.
- Add a cron entry like this to run collectstats.pl daily at 5 after
- midnight:
+Add a cron entry like this to run collectstats.pl daily at 5 after midnight:
- bash# crontab -e
- 5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
+bash# crontab -e
+5 0 * * * cd <your-bugzilla-directory> ; ./collectstats.pl
After two days have passed you'll be able to view bug graphs from the
Bug Reports page.
4.2.3. The Whining Cron
- By now you have a fully functional Bugzilla, but what good are bugs if
- they're not annoying? To help make those bugs more annoying you can
- set up Bugzilla's automatic whining system to complain at engineers
- which leave their bugs in the NEW state without triaging them.
+By now you have a fully functional Bugzilla, but what good are bugs if
+they're not annoying? To help make those bugs more annoying you can set up
+Bugzilla's automatic whining system to complain at engineers which leave
+their bugs in the NEW state without triaging them.
- This can be done by adding the following command as a daily crontab
- entry (for help on that see that crontab man page):
+This can be done by adding the following command as a daily crontab entry
+(for help on that see that crontab man page):
- cd <your-bugzilla-directory> ; ./whineatnews.pl
+cd <your-bugzilla-directory> ; ./whineatnews.pl
Tip
4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code
- It is possible for a Bugzilla to execute malicious Javascript code.
- Due to internationalization concerns, we are unable to incorporate the
- code changes necessary to fulfill the CERT advisory requirements
- mentioned in
- http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3.
- Executing the following code snippet from a UNIX command shell will
- rectify the problem if your Bugzilla installation is intended for an
- English-speaking audience. As always, be sure your Bugzilla
- installation has a good backup before making changes, and I recommend
- you understand what the script is doing before executing it.
+It is possible for a Bugzilla to execute malicious Javascript code. Due to
+internationalization concerns, we are unable to incorporate the code changes
+necessary to fulfill the CERT advisory requirements mentioned in
+http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. Executing
+the following code snippet from a UNIX command shell will rectify the
+problem if your Bugzilla installation is intended for an English-speaking
+audience. As always, be sure your Bugzilla installation has a good backup
+before making changes, and I recommend you understand what the script is
+doing before executing it.
bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; char
set=ISO-8859-1/i" *.cgi *.pl
4.2.6. .htaccess files and security
- To enhance the security of your Bugzilla installation, Bugzilla's
- checksetup.pl script will generate .htaccess files which the Apache
- webserver can use to restrict access to the bugzilla data 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.
+To enhance the security of your Bugzilla installation, Bugzilla's
+checksetup.pl script will generate .htaccess files which the Apache
+webserver can use to restrict access to the bugzilla data 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.
Note
4.2.7. mod_throttle and Security
- It is possible for a user, by mistake or on purpose, to access the
- database many times in a row which can result in very slow access
- speeds for other users. If your Bugzilla installation is experiencing
- this problem , you may install the Apache module mod_throttle which
- can limit connections by ip-address. You may download this module at
- http://www.snert.com/Software/mod_throttle/ Follow the instructions to
- install into your Apache install. This module only functions with the
- Apache web server! You may use the ThrottleClientIP command provided
- by this module to accomplish this goal. See the Module Instructions
- for more information.
+It is possible for a user, by mistake or on purpose, to access the database
+many times in a row which can result in very slow access speeds for other
+users. If your Bugzilla installation is experiencing this problem , you may
+install the Apache module mod_throttle which can limit connections by
+ip-address. You may download this module at
+http://www.snert.com/Software/mod_throttle/ Follow the instructions to
+install into your Apache install. This module only functions with the Apache
+web server! You may use the ThrottleClientIP command provided by this module
+to accomplish this goal. See the Module Instructions for more information.
_________________________________________________________________
4.3. Win32 Installation Notes
- This section covers installation on Microsoft Windows. Bugzilla has
- been made to work on Win32 platforms, but the Bugzilla team wish to
- emphasise that The easiest way to install Bugzilla on
- Intel-archiecture machines is to install some variant of GNU/Linux,
- then follow the UNIX installation instructions in this Guide. If you
- have any influence in the platform choice for running this system,
- please choose GNU/Linux instead of Microsoft Windows.
+This section covers installation on Microsoft Windows. Bugzilla has been
+made to work on Win32 platforms, but the Bugzilla team wish to emphasise
+that The easiest way to install Bugzilla on Intel-archiecture machines is to
+install some variant of GNU/Linux, then follow the UNIX installation
+instructions in this Guide. If you have any influence in the platform choice
+for running this system, please choose GNU/Linux instead of Microsoft
+Windows.
Warning
source code and implementing some advanced utilities. What follows is
the recommended installation procedure for Win32; additional
suggestions are provided in Appendix A .
+
1. Install Apache Web Server for Windows, and copy the Bugzilla files
somewhere Apache can serve them. Please follow all the
instructions referenced in Bugzilla Installation regarding your
If attempting to run Bugzilla 2.12 or older, you will need to remove
encrypt() calls from the Perl source. This is not necessary for
Bugzilla 2.13 and later, which includes the current release, Bugzilla
- 2.16.3.
+ 2.16.4.
Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12
or earlier
4.4. Mac OS X Installation Notes
- There are a lot of common libraries and utilities out there that Apple
- did not include with Mac OS X, but which run perfectly well on it. The
- GD library, which Bugzilla needs to do bug graphs, is one of these.
-
- The easiest way to get a lot of these is with a program called Fink,
- which is similar in nature to the CPAN installer, but installs common
- GNU utilities. Fink is available from
- <http://sourceforge.net/projects/fink/>.
-
- Follow the instructions for setting up Fink. Once it's installed,
- you'll want to run the following as root: fink install gd
-
- It will prompt you for a number of dependencies, type 'y' and hit
- enter to install all of the dependencies. Then watch it work.
-
- To prevent creating conflicts with the software that Apple installs by
- default, Fink creates its own directory tree at /sw where it installs
- most of the software that it installs. This means your libraries and
- headers for libgd will be at /sw/lib and /sw/include instead of
- /usr/lib and /usr/local/include. Because of these changed locations
- for the libraries, the Perl GD module will not install directly via
- CPAN, because it looks for the specific paths instead of getting them
- from your environment. But there's a way around that :-)
-
- Instead of typing "install GD" at the cpan> prompt, type look GD. This
- should go through the motions of downloading the latest version of the
- GD module, then it will open a shell and drop you into the build
- directory. Apply this patch to the Makefile.PL file (save the patch
- into a file and use the command patch < patchfile.)
-
- Then, run these commands to finish the installation of the GD module:
-
- perl Makefile.PL
- make
- make test
- make install
- And don't forget to run exit to get back to CPAN.
+There are a lot of common libraries and utilities out there that Apple did
+not include with Mac OS X, but which run perfectly well on it. The GD
+library, which Bugzilla needs to do bug graphs, is one of these.
+
+The easiest way to get a lot of these is with a program called Fink, which
+is similar in nature to the CPAN installer, but installs common GNU
+utilities. Fink is available from <http://sourceforge.net/projects/fink/>.
+
+Follow the instructions for setting up Fink. Once it's installed, you'll
+want to run the following as root: fink install gd
+
+It will prompt you for a number of dependencies, type 'y' and hit enter to
+install all of the dependencies. Then watch it work.
+
+To prevent creating conflicts with the software that Apple installs by
+default, Fink creates its own directory tree at /sw where it installs most
+of the software that it installs. This means your libraries and headers for
+libgd will be at /sw/lib and /sw/include instead of /usr/lib and
+/usr/local/include. Because of these changed locations for the libraries,
+the Perl GD module will not install directly via CPAN, because it looks for
+the specific paths instead of getting them from your environment. But
+there's a way around that :-)
+
+Instead of typing "install GD" at the cpan> prompt, type look GD. This
+should go through the motions of downloading the latest version of the GD
+module, then it will open a shell and drop you into the build directory.
+Apply this patch to the Makefile.PL file (save the patch into a file and use
+the command patch < patchfile.)
+
+Then, run these commands to finish the installation of the GD module:
+
+perl Makefile.PL
+make
+make test
+make install
+And don't forget to run exit to get back to CPAN.
_________________________________________________________________
4.5. Troubleshooting
- This section gives solutions to common Bugzilla installation problems.
+This section gives solutions to common Bugzilla installation problems.
_________________________________________________________________
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
- Try executing perl -MCPAN -e 'install CPAN' and then continuing.
+Try executing perl -MCPAN -e 'install CPAN' and then continuing.
- Certain older versions of the CPAN toolset were somewhat naive about
- how to upgrade Perl modules. When a couple of modules got rolled into
- the core Perl distribution for 5.6.1, CPAN thought that the best way
- to get those modules up to date was to haul down the Perl distribution
- itself and build it. Needless to say, this has caused headaches for
- just about everybody. Upgrading to a newer version of CPAN with the
- commandline above should fix things.
+Certain older versions of the CPAN toolset were somewhat naive about how to
+upgrade Perl modules. When a couple of modules got rolled into the core Perl
+distribution for 5.6.1, CPAN thought that the best way to get those modules
+up to date was to haul down the Perl distribution itself and build it.
+Needless to say, this has caused headaches for just about everybody.
+Upgrading to a newer version of CPAN with the commandline above should fix
+things.
_________________________________________________________________
4.5.2. DBD::Sponge::db prepare failed
- The following error message may appear due to a bug in DBD::mysql
- (over which the Bugzilla team have no control):
+The following error message may appear due to a bug in DBD::mysql (over
+which the Bugzilla team have no control):
+
DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site
/lib/DBD/mysql.pm line 248.
SV = NULL(0x0) at 0x20fc444
4.5.3. cannot chdir(/var/spool/mqueue)
- If you are installing Bugzilla on SuSE Linux, or some other
- distributions with "paranoid" security options, it is possible that
- the checksetup.pl script may fail with the error:
- cannot chdir(/var/spool/mqueue): Permission denied
+If you are installing Bugzilla on SuSE Linux, or some other distributions
+with "paranoid" security options, it is possible that the checksetup.pl
+script may fail with the error:
+
+cannot chdir(/var/spool/mqueue): Permission denied
This is because your /var/spool/mqueue directory has a mode of
"drwx------". Type chmod 755 /var/spool/mqueue as root to fix this
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
- This is caused by a bug in the version of File::Temp that is
- distributed with perl 5.6.0. Many minor variations of this error have
- been reported. Examples can be found in Figure 4-1.
+This is caused by a bug in the version of File::Temp that is distributed
+with perl 5.6.0. Many minor variations of this error have been reported.
+Examples can be found in Figure 4-1.
Figure 4-1. Other File::Temp error messages
Your vendor has not defined Fcntl macro O_NOINHERIT, used
5.1. Bugzilla Configuration
- Bugzilla is configured by changing various parameters, accessed from
- the "Edit parameters" link in the page footer. Here are some of the
- key parameters on that page. You should run down this list and set
- them appropriately after installing Bugzilla.
+Bugzilla is configured by changing various parameters, accessed from the
+"Edit parameters" link in the page footer. Here are some of the key
+parameters on that page. You should run down this list and set them
+appropriately after installing Bugzilla.
+
1. maintainer: The maintainer parameter is the email address of the
person responsible for maintaining this Bugzilla installation. The
address need not be that of a valid Bugzilla account.
5.2.1. Creating the Default User
- When you first run checksetup.pl after installing Bugzilla, it will
- prompt you for the administrative username (email address) and
- password for this "super user". If for some reason you delete the
- "super user" account, re-running checksetup.pl will again prompt you
- for this username and password.
+When you first run checksetup.pl after installing Bugzilla, it will prompt
+you for the administrative username (email address) and password for this
+"super user". If for some reason you delete the "super user" account,
+re-running checksetup.pl will again prompt you for this username and
+password.
Tip
5.2.2.1. Creating new users
- Your users can create their own user accounts by clicking the "New
- Account" link at the bottom of each page (assuming they aren't logged
- in as someone else already.) However, should you desire to create user
- accounts ahead of time, here is how you do it.
+Your users can create their own user accounts by clicking the "New Account"
+link at the bottom of each page (assuming they aren't logged in as someone
+else already.) However, should you desire to create user accounts ahead of
+time, here is how you do it.
1. After logging in, click the "Users" link at the footer of the
query page, and then click "Add a new user".
5.2.2.2. Modifying Users
- To see a specific user, search for their login name in the box
- provided on the "Edit Users" page. To see all users, leave the box
- blank.
+To see a specific user, search for their login name in the box provided on
+the "Edit Users" page. To see all users, leave the box blank.
- You can search in different ways the listbox to the right of the text
- entry box. You can match by case-insensitive substring (the default),
- regular expression, or a reverse regular expression match, which finds
- every user name which does NOT match the regular expression. (Please
- see the man regexp manual page for details on regular expression
- syntax.)
+You can search in different ways the listbox to the right of the text entry
+box. You can match by case-insensitive substring (the default), regular
+expression, or a reverse regular expression match, which finds every user
+name which does NOT match the regular expression. (Please see the man regexp
+manual page for details on regular expression syntax.)
- Once you have found your user, you can change the following fields:
+Once you have found your user, you can change the following fields:
* Login Name: This is generally the user's full email address.
However, if you have are using the emailsuffix Param, this may
5.3.1. Products
- Products are the broadest category in Bugzilla, and tend to represent
- real-world shipping products. E.g. if your company makes computer
- games, you should have one product per game, perhaps a "Common"
- product for units of technology used in multiple games, and maybe a
- few special products (Website, Administration...)
+Products are the broadest category in Bugzilla, and tend to represent
+real-world shipping products. E.g. if your company makes computer games, you
+should have one product per game, perhaps a "Common" product for units of
+technology used in multiple games, and maybe a few special products
+(Website, Administration...)
- Many of Bugzilla's settings are configurable on a per-product basis.
- The number of "votes" available to users is set per-product, as is the
- number of votes required to move a bug automatically from the
- UNCONFIRMED status to the NEW status.
+Many of Bugzilla's settings are configurable on a per-product basis. The
+number of "votes" available to users is set per-product, as is the number of
+votes required to move a bug automatically from the UNCONFIRMED status to
+the NEW status.
- To create a new product:
+To create a new product:
1. Select "products" from the footer
2. Select the "Add" link in the bottom right
5.3.2. Components
- Components are subsections of a Product. E.g. the computer game you
- are designing may have a "UI" component, an "API" component, a "Sound
- System" component, and a "Plugins" component, each overseen by a
- different programmer. It often makes sense to divide Components in
- Bugzilla according to the natural divisions of responsibility within
- your Product or company.
+Components are subsections of a Product. E.g. the computer game you are
+designing may have a "UI" component, an "API" component, a "Sound System"
+component, and a "Plugins" component, each overseen by a different
+programmer. It often makes sense to divide Components in Bugzilla according
+to the natural divisions of responsibility within your Product or company.
- Each component has a owner and (if you turned it on in the
- parameters), a QA Contact. The owner should be the primary person who
- fixes bugs in that component. The QA Contact should be the person who
- will ensure these bugs are completely fixed. The Owner, QA Contact,
- and Reporter will get email when new bugs are created in this
- Component and when these bugs change. Default Owner and Default QA
- Contact fields only dictate the default assignments; these can be
- changed on bug submission, or at any later point in a bug's life.
+Each component has a owner and (if you turned it on in the parameters), a QA
+Contact. The owner should be the primary person who fixes bugs in that
+component. The QA Contact should be the person who will ensure these bugs
+are completely fixed. The Owner, QA Contact, and Reporter will get email
+when new bugs are created in this Component and when these bugs change.
+Default Owner and Default QA Contact fields only dictate the default
+assignments; these can be changed on bug submission, or at any later point
+in a bug's life.
- To create a new Component:
+To create a new Component:
1. Select the "Edit components" link from the "Edit product" page
2. Select the "Add" link in the bottom right.
5.3.3. Versions
- Versions are the revisions of the product, such as "Flinders 3.1",
- "Flinders 95", and "Flinders 2000". Version is not a multi-select
- field; the usual practice is to select the most recent version with
- the bug.
+Versions are the revisions of the product, such as "Flinders 3.1", "Flinders
+95", and "Flinders 2000". Version is not a multi-select field; the usual
+practice is to select the most recent version with the bug.
- To create and edit Versions:
+To create and edit Versions:
1. From the "Edit product" screen, select "Edit Versions"
2. You will notice that the product already has the default version
5.3.4. Milestones
- Milestones are "targets" that you plan to get a bug fixed by. For
- example, you have a bug that you plan to fix for your 3.0 release, it
- would be assigned the milestone of 3.0.
+Milestones are "targets" that you plan to get a bug fixed by. For example,
+you have a bug that you plan to fix for your 3.0 release, it would be
+assigned the milestone of 3.0.
Note
5.4. Voting
- Voting allows users to be given a pot of votes which they can allocate
- to bugs, to indicate that they'd like them fixed. This allows
- developers to gauge user need for a particular enhancement or bugfix.
- By allowing bugs with a certain number of votes to automatically move
- from "UNCONFIRMED" to "NEW", users of the bug system can help
- high-priority bugs garner attention so they don't sit for a long time
- awaiting triage.
+Voting allows users to be given a pot of votes which they can allocate to
+bugs, to indicate that they'd like them fixed. This allows developers to
+gauge user need for a particular enhancement or bugfix. By allowing bugs
+with a certain number of votes to automatically move from "UNCONFIRMED" to
+"NEW", users of the bug system can help high-priority bugs garner attention
+so they don't sit for a long time awaiting triage.
- To modify Voting settings:
+To modify Voting settings:
1. Navigate to the "Edit product" screen for the Product you wish to
modify
5.5. Groups and Group Security
- Groups allow the administrator to isolate bugs or products that should
- only be seen by certain people. There are two types of group - Generic
- Groups, and Product-Based Groups.
+Groups allow the administrator to isolate bugs or products that should only
+be seen by certain people. There are two types of group - Generic Groups,
+and Product-Based Groups.
- Product-Based Groups are matched with products, and allow you to
- restrict access to bugs on a per-product basis. They are enabled using
- the usebuggroups Param. Turning on the usebuggroupsentry Param will
- mean bugs automatically get added to their product group when filed.
+Product-Based Groups are matched with products, and allow you to restrict
+access to bugs on a per-product basis. They are enabled using the
+usebuggroups Param. Turning on the usebuggroupsentry Param will mean bugs
+automatically get added to their product group when filed.
- Generic Groups have no special relationship to products; you create
- them, and put bugs in them as required. One example of the use of
- Generic Groups is Mozilla's "Security" group, into which
- security-sensitive bugs are placed until fixed. Only the Mozilla
- Security Team are members of this group.
+Generic Groups have no special relationship to products; you create them,
+and put bugs in them as required. One example of the use of Generic Groups
+is Mozilla's "Security" group, into which security-sensitive bugs are placed
+until fixed. Only the Mozilla Security Team are members of this group.
- To create Generic Groups:
+To create Generic Groups:
1. Select the "groups" link in the footer.
2. Take a moment to understand the instructions on the "Edit Groups"
5.6.1. TCP/IP Ports
- TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only
- needs 1... 2 if you need to use features that require e-mail such as
- bug moving or the e-mail interface from contrib. You should audit your
- server and make sure that you aren't listening on any ports you don't
- need to be. You may also wish to use some kind of firewall software to
- be sure that trafic can only be recieved on ports you specify.
+TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only needs
+1... 2 if you need to use features that require e-mail such as bug moving or
+the e-mail interface from contrib. You should audit your server and make
+sure that you aren't listening on any ports you don't need to be. You may
+also wish to use some kind of firewall software to be sure that trafic can
+only be recieved on ports you specify.
_________________________________________________________________
5.6.2. MySQL
- MySQL ships by default with many settings that should be changed. By
- defaults it allows anybody to connect from localhost without a
- password and have full administrative capabilities. It also defaults
- to not have a root password (this is not the same as the system root).
- Also, many installations default to running mysqld as the system root.
+MySQL ships by default with many settings that should be changed. By
+defaults it allows anybody to connect from localhost without a password and
+have full administrative capabilities. It also defaults to not have a root
+password (this is not the same as the system root). Also, many installations
+default to running mysqld as the system root.
1. Make sure you are running at least version 3.22.32 of MySQL as
earlier versions had notable security holes.
5.6.3. Daemon Accounts
- Many daemons, such as Apache's httpd and MySQL's mysqld default to
- running as either "root" or "nobody". Running as "root" introduces
- obvious security problems, but the problems introduced by running
- everything as "nobody" may not be so obvious. Basically, if you're
- running every daemon as "nobody" and one of them gets comprimised,
- they all get comprimised. For this reason it is recommended that you
- create a user account for each daemon.
+Many daemons, such as Apache's httpd and MySQL's mysqld default to running
+as either "root" or "nobody". Running as "root" introduces obvious security
+problems, but the problems introduced by running everything as "nobody" may
+not be so obvious. Basically, if you're running every daemon as "nobody" and
+one of them gets comprimised, they all get comprimised. For this reason it
+is recommended that you create a user account for each daemon.
Note
5.6.4. Web Server Access Controls
- There are many files that are placed in the Bugzilla directory area
- that should not be accessable from the web. Because of the way
- Bugzilla is currently layed out, the list of what should and should
- not be accessible is rather complicated. A new installation method is
- currently in the works which should solve this by allowing files that
- shouldn't be accessible from the web to be placed in directory outside
- the webroot. See bug 44659 for more information.
+There are many files that are placed in the Bugzilla directory area that
+should not be accessable from the web. Because of the way Bugzilla is
+currently layed out, the list of what should and should not be accessible is
+rather complicated. A new installation method is currently in the works
+which should solve this by allowing files that shouldn't be accessible from
+the web to be placed in directory outside the webroot. See bug 44659 for
+more information.
* In the main Bugzilla directory, you should:
+ Block: *.pl, *localconfig*, runtests.sh, processmail,
5.7. Template Customisation
- One of the large changes for 2.16 was the templatisation of the entire
- user-facing UI, using the Template Toolkit. Administrators can now
- configure the look and feel of Bugzilla without having to edit Perl
- files or face the nightmare of massive merge conflicts when they
- upgrade to a newer version in the future.
+One of the large changes for 2.16 was the templatisation of the entire
+user-facing UI, using the Template Toolkit. Administrators can now configure
+the look and feel of Bugzilla without having to edit Perl files or face the
+nightmare of massive merge conflicts when they upgrade to a newer version in
+the future.
- Templatisation also makes localised versions of Bugzilla possible, for
- the first time. In the future, a Bugzilla installation may have
- templates installed for multiple localisations, and select which ones
- to use based on the user's browser language setting.
+Templatisation also makes localised versions of Bugzilla possible, for the
+first time. In the future, a Bugzilla installation may have templates
+installed for multiple localisations, and select which ones to use based on
+the user's browser language setting.
_________________________________________________________________
5.7.1. What to Edit
- There are two different ways of editing of Bugzilla's templates, and
- which you use depends mainly on how you upgrade Bugzilla. The template
- directory structure is that there's a top level directory, template,
- which contains a directory for each installed localisation. The
- default English templates are therefore in en. Underneath that, there
- is the default directory and optionally the custom directory. The
- default directory contains all the templates shipped with Bugzilla,
- whereas the custom directory does not exist at first and must be
- created if you want to use it.
-
- The first method of making customisations is to directly edit the
- templates in template/en/default. This is probably the best method for
- small changes if you are going to use the CVS method of upgrading,
- because if you then execute a cvs update, any template fixes will get
- automagically merged into your modified versions.
-
- If you use this method, your installation will break if CVS conflicts
- occur.
-
- The other method is to copy the templates into a mirrored directory
- structure under template/en/custom. The templates in this directory
- automatically override those in default. This is the technique you
- need to use if you use the overwriting method of upgrade, because
- otherwise your changes will be lost. This method is also better if you
- are using the CVS method of upgrading and are going to make major
- changes, because it is guaranteed that the contents of this directory
- will not be touched during an upgrade, and you can then decide whether
- to continue using your own templates, or make the effort to merge your
- changes into the new versions by hand.
-
- If you use this method, your installation may break if incompatible
- changes are made to the template interface. If such changes are made
- they will be documented in the release notes, provided you are using a
- stable release of Bugzilla. If you use using unstable code, you will
- need to deal with this one yourself, although if possible the changes
- will be mentioned before they occur in the deprecations section of the
- previous stable release's release notes.
+There are two different ways of editing of Bugzilla's templates, and which
+you use depends mainly on how you upgrade Bugzilla. The template directory
+structure is that there's a top level directory, template, which contains a
+directory for each installed localisation. The default English templates are
+therefore in en. Underneath that, there is the default directory and
+optionally the custom directory. The default directory contains all the
+templates shipped with Bugzilla, whereas the custom directory does not exist
+at first and must be created if you want to use it.
+
+The first method of making customisations is to directly edit the templates
+in template/en/default. This is probably the best method for small changes
+if you are going to use the CVS method of upgrading, because if you then
+execute a cvs update, any template fixes will get automagically merged into
+your modified versions.
+
+If you use this method, your installation will break if CVS conflicts occur.
+
+The other method is to copy the templates into a mirrored directory
+structure under template/en/custom. The templates in this directory
+automatically override those in default. This is the technique you need to
+use if you use the overwriting method of upgrade, because otherwise your
+changes will be lost. This method is also better if you are using the CVS
+method of upgrading and are going to make major changes, because it is
+guaranteed that the contents of this directory will not be touched during an
+upgrade, and you can then decide whether to continue using your own
+templates, or make the effort to merge your changes into the new versions by
+hand.
+
+If you use this method, your installation may break if incompatible changes
+are made to the template interface. If such changes are made they will be
+documented in the release notes, provided you are using a stable release of
+Bugzilla. If you use using unstable code, you will need to deal with this
+one yourself, although if possible the changes will be mentioned before they
+occur in the deprecations section of the previous stable release's release
+notes.
Note
Don't directly edit the compiled templates in data/template/* - your
changes will be lost when Template Toolkit recompiles them.
+
+ Note
+
+ It is recommended that you run ./checksetup.pl after any template
+ edits, especially if you've created a new file in the custom
+ directory.
_________________________________________________________________
5.7.2. How To Edit Templates
- The syntax of the Template Toolkit language is beyond the scope of
- this guide. It's reasonably easy to pick up by looking at the current
- templates; or, you can read the manual, available on the Template
- Toolkit home page. However, you should particularly remember (for
- security reasons) to always HTML filter things which come from the
- database or user input, to prevent cross-site scripting attacks.
-
- However, one thing you should take particular care about is the need
- to properly HTML filter data that has been passed into the template.
- This means that if the data can possibly contain special HTML
- characters such as <, and the data was not intended to be HTML, they
- need to be converted to entity form, ie <. You use the 'html'
- filter in the Template Toolkit to do this. If you fail to do this, you
- may open up your installation to cross-site scripting attacks.
-
- Also note that Bugzilla adds a few filters of its own, that are not in
- standard Template Toolkit. In particular, the 'url_quote' filter can
- convert characters that are illegal or have special meaning in URLs,
- such as &, to the encoded form, ie %26. This actually encodes most
- characters (but not the common ones such as letters and numbers and so
- on), including the HTML-special characters, so there's never a need to
- HTML filter afterwards.
-
- Editing templates is a good way of doing a "poor man's custom fields".
- For example, if you don't use the Status Whiteboard, but want to have
- a free-form text entry box for "Build Identifier", then you can just
- edit the templates to change the field labels. It's still be called
- status_whiteboard internally, but your users don't need to know that.
+The syntax of the Template Toolkit language is beyond the scope of this
+guide. It's reasonably easy to pick up by looking at the current templates;
+or, you can read the manual, available on the Template Toolkit home page.
+However, you should particularly remember (for security reasons) to always
+HTML filter things which come from the database or user input, to prevent
+cross-site scripting attacks.
+
+However, one thing you should take particular care about is the need to
+properly HTML filter data that has been passed into the template. This means
+that if the data can possibly contain special HTML characters such as <, and
+the data was not intended to be HTML, they need to be converted to entity
+form, ie <. You use the 'html' filter in the Template Toolkit to do this.
+If you fail to do this, you may open up your installation to cross-site
+scripting attacks.
+
+Also note that Bugzilla adds a few filters of its own, that are not in
+standard Template Toolkit. In particular, the 'url_quote' filter can convert
+characters that are illegal or have special meaning in URLs, such as &, to
+the encoded form, ie %26. This actually encodes most characters (but not the
+common ones such as letters and numbers and so on), including the
+HTML-special characters, so there's never a need to HTML filter afterwards.
+
+Editing templates is a good way of doing a "poor man's custom fields". For
+example, if you don't use the Status Whiteboard, but want to have a
+free-form text entry box for "Build Identifier", then you can just edit the
+templates to change the field labels. It's still be called status_whiteboard
+internally, but your users don't need to know that.
Note
5.7.3. Template Formats
- Some CGIs have the ability to use more than one template. For example,
- buglist.cgi can output bug lists as RDF or two different forms of HTML
- (complex and simple). (Try this out by appending &format=simple to a
- buglist.cgi URL on your Bugzilla installation.) This mechanism, called
- template 'formats', is extensible.
-
- To see if a CGI supports multiple output formats, grep the CGI for
- "ValidateOutputFormat". If it's not present, adding multiple format
- support isn't too hard - see how it's done in other CGIs.
-
- To make a new format template for a CGI which supports this, open a
- current template for that CGI and take note of the INTERFACE comment
- (if present.) This comment defines what variables are passed into this
- template. If there isn't one, I'm afraid you'll have to read the
- template and the code to find out what information you get.
-
- Write your template in whatever markup or text style is appropriate.
-
- You now need to decide what content type you want your template served
- as. Open up the localconfig file and find the $contenttypes variable.
- If your content type is not there, add it. Remember the three- or
- four-letter tag assigned to you content type. This tag will be part of
- the template filename.
-
- Save the template as <stubname>-<formatname>.<contenttypetag>.tmpl.
- Try out the template by calling the CGI as
- <cginame>.cgi?format=<formatname> .
+Some CGIs have the ability to use more than one template. For example,
+buglist.cgi can output bug lists as RDF or two different forms of HTML
+(complex and simple). (Try this out by appending &format=simple to a
+buglist.cgi URL on your Bugzilla installation.) This mechanism, called
+template 'formats', is extensible.
+
+To see if a CGI supports multiple output formats, grep the CGI for
+"ValidateOutputFormat". If it's not present, adding multiple format support
+isn't too hard - see how it's done in other CGIs.
+
+To make a new format template for a CGI which supports this, open a current
+template for that CGI and take note of the INTERFACE comment (if present.)
+This comment defines what variables are passed into this template. If there
+isn't one, I'm afraid you'll have to read the template and the code to find
+out what information you get.
+
+Write your template in whatever markup or text style is appropriate.
+
+You now need to decide what content type you want your template served as.
+Open up the localconfig file and find the $contenttypes variable. If your
+content type is not there, add it. Remember the three- or four-letter tag
+assigned to you content type. This tag will be part of the template
+filename.
+
+Save the template as <stubname>-<formatname>.<contenttypetag>.tmpl. Try out
+the template by calling the CGI as <cginame>.cgi?format=<formatname> .
_________________________________________________________________
5.7.4. Particular Templates
- There are a few templates you may be particularly interested in
- customising for your installation.
-
- index.html.tmpl: This is the Bugzilla front page.
-
- global/header.html.tmpl: This defines the header that goes on all
- Bugzilla pages. The header includes the banner, which is what appears
- to users and is probably what you want to edit instead. However the
- header also includes the HTML HEAD section, so you could for example
- add a stylesheet or META tag by editing the header.
-
- global/banner.html.tmpl: This contains the "banner", the part of the
- header that appears at the top of all Bugzilla pages. The default
- banner is reasonably barren, so you'll probably want to customise this
- to give your installation a distinctive look and feel. It is
- recommended you preserve the Bugzilla version number in some form so
- the version you are running can be determined, and users know what
- docs to read.
-
- global/footer.html.tmpl: This defines the footer that goes on all
- Bugzilla pages. Editing this is another way to quickly get a
- distinctive look and feel for your Bugzilla installation.
-
- bug/create/user-message.html.tmpl: This is a message that appears near
- the top of the bug reporting page. By modifying this, you can tell
- your users how they should report bugs.
-
- bug/create/create.html.tmpl and bug/create/comment.txt.tmpl: You may
- wish to get bug submitters to give certain bits of structured
- information, each in a separate input widget, for which there is not a
- field in the database. The bug entry system has been designed in an
- extensible fashion to enable you to define arbitrary fields and
- widgets, and have their values appear formatted in the initial
- Description, rather than in database fields. An example of this is the
- mozilla.org guided bug submission form.
-
- To make this work, create a custom template for enter_bug.cgi (the
- default template, on which you could base it, is create.html.tmpl),
- and either call it create.html.tmpl or use a format and call it
- create-<formatname>.html.tmpl. Put it in the custom/bug/create
- directory. In it, add widgets for each piece of information you'd like
- collected - such as a build number, or set of steps to reproduce.
-
- Then, create a template like custom/bug/create/comment.txt.tmpl, also
- named after your format if you are using one, which references the
- form fields you have created. When a bug report is submitted, the
- initial comment attached to the bug report will be formatted according
- to the layout of this template.
-
- For example, if your enter_bug template had a field
- <input type="text" name="buildid" size="30">
-
- and then your comment.txt.tmpl had
+There are a few templates you may be particularly interested in customising
+for your installation.
+
+index.html.tmpl: This is the Bugzilla front page.
+
+global/header.html.tmpl: This defines the header that goes on all Bugzilla
+pages. The header includes the banner, which is what appears to users and is
+probably what you want to edit instead. However the header also includes the
+HTML HEAD section, so you could for example add a stylesheet or META tag by
+editing the header.
+
+global/banner.html.tmpl: This contains the "banner", the part of the header
+that appears at the top of all Bugzilla pages. The default banner is
+reasonably barren, so you'll probably want to customise this to give your
+installation a distinctive look and feel. It is recommended you preserve the
+Bugzilla version number in some form so the version you are running can be
+determined, and users know what docs to read.
+
+global/footer.html.tmpl: This defines the footer that goes on all Bugzilla
+pages. Editing this is another way to quickly get a distinctive look and
+feel for your Bugzilla installation.
+
+bug/create/user-message.html.tmpl: This is a message that appears near the
+top of the bug reporting page. By modifying this, you can tell your users
+how they should report bugs.
+
+bug/create/create.html.tmpl and bug/create/comment.txt.tmpl: You may wish to
+get bug submitters to give certain bits of structured information, each in a
+separate input widget, for which there is not a field in the database. The
+bug entry system has been designed in an extensible fashion to enable you to
+define arbitrary fields and widgets, and have their values appear formatted
+in the initial Description, rather than in database fields. An example of
+this is the mozilla.org guided bug submission form.
+
+To make this work, create a custom template for enter_bug.cgi (the default
+template, on which you could base it, is create.html.tmpl), and either call
+it create.html.tmpl or use a format and call it
+create-<formatname>.html.tmpl. Put it in the custom/bug/create directory. In
+it, add widgets for each piece of information you'd like collected - such as
+a build number, or set of steps to reproduce.
+
+Then, create a template like custom/bug/create/comment.txt.tmpl, also named
+after your format if you are using one, which references the form fields you
+have created. When a bug report is submitted, the initial comment attached
+to the bug report will be formatted according to the layout of this
+template.
+
+For example, if your enter_bug template had a field
+
+<input type="text" name="buildid" size="30">
+
+and then your comment.txt.tmpl had
+
BuildID: [% form.buildid %]
then
5.8. Upgrading to New Releases
- Upgrading Bugzilla is something we all want to do from time to time,
- be it to get new features or pick up the latest security fix. How easy
- it is to update depends on a few factors.
+Upgrading Bugzilla is something we all want to do from time to time, be it
+to get new features or pick up the latest security fix. How easy it is to
+update depends on a few factors.
* If the new version is a revision or a new point release
* How many, if any, local changes have been made
5.9.1. Bonsai
- Bonsai is a web-based tool for managing CVS, the Concurrent Versioning
- System . Using Bonsai, administrators can control open/closed status
- of trees, query a fast relational database back-end for change,
- branch, and comment information, and view changes made since the last
- time the tree was closed. Bonsai also integrates with Tinderbox, the
- Mozilla automated build management system.
+Bonsai is a web-based tool for managing CVS, the Concurrent Versioning
+System . Using Bonsai, administrators can control open/closed status of
+trees, query a fast relational database back-end for change, branch, and
+comment information, and view changes made since the last time the tree was
+closed. Bonsai also integrates with Tinderbox, the Mozilla automated build
+management system.
_________________________________________________________________
5.9.2. CVS
- CVS integration is best accomplished, at this point, using the
- Bugzilla Email Gateway.
+CVS integration is best accomplished, at this point, using the Bugzilla
+Email Gateway.
- Follow the instructions in this Guide for enabling Bugzilla e-mail
- integration. Ensure that your check-in script sends an email to your
- Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
- have CVS check-in comments append to your Bugzilla bug. If you want to
- have the bug be closed automatically, you'll have to modify the
- contrib/bugzilla_email_append.pl script.
+Follow the instructions in this Guide for enabling Bugzilla e-mail
+integration. Ensure that your check-in script sends an email to your
+Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can have
+CVS check-in comments append to your Bugzilla bug. If you want to have the
+bug be closed automatically, you'll have to modify the
+contrib/bugzilla_email_append.pl script.
- There is also a CVSZilla project, based upon somewhat dated Bugzilla
- code, to integrate CVS and Bugzilla through CVS' ability to email.
- Check it out at: http://homepages.kcbbs.gen.nz/~tonyg/.
+There is also a CVSZilla project, based upon somewhat dated Bugzilla code,
+to integrate CVS and Bugzilla through CVS' ability to email. Check it out
+at: http://homepages.kcbbs.gen.nz/~tonyg/.
_________________________________________________________________
5.9.3. Perforce SCM
- You can find the project page for Bugzilla and Teamtrack Perforce
- integration (p4dti) at: http://www.ravenbrook.com/project/p4dti .
- "p4dti" is now an officially supported product from Perforce, and you
- can find the "Perforce Public Depot" p4dti page at
- http://public.perforce.com/public/perforce/p4dti/index.html .
-
- Integration of Perforce with Bugzilla, once patches are applied, is
- seamless. Perforce replication information will appear below the
- comments of each bug. Be certain you have a matching set of patches
- for the Bugzilla version you are installing. p4dti is designed to
- support multiple defect trackers, and maintains its own documentation
- for it. Please consult the pages linked above for further information.
+You can find the project page for Bugzilla and Teamtrack Perforce
+integration (p4dti) at: http://www.ravenbrook.com/project/p4dti . "p4dti" is
+now an officially supported product from Perforce, and you can find the
+"Perforce Public Depot" p4dti page at
+http://public.perforce.com/public/perforce/p4dti/index.html .
+
+Integration of Perforce with Bugzilla, once patches are applied, is
+seamless. Perforce replication information will appear below the comments of
+each bug. Be certain you have a matching set of patches for the Bugzilla
+version you are installing. p4dti is designed to support multiple defect
+trackers, and maintains its own documentation for it. Please consult the
+pages linked above for further information.
_________________________________________________________________
5.9.4. Tinderbox/Tinderbox2
- We need Tinderbox integration information.
+We need Tinderbox integration information.
_________________________________________________________________
Appendix A. The Bugzilla FAQ
- This FAQ includes questions not covered elsewhere in the Guide.
+This FAQ includes questions not covered elsewhere in the Guide.
1. General Questions
A.7.5. How do I change a keyword in Bugzilla, once some bugs are
using it?
+ A.7.6. Why can't I close bugs from the "Change Several Bugs at
+ Once" page?
+
8. Bugzilla Hacking
A.8.1. What bugs are in Bugzilla right now?
A.1.5. Who maintains Bugzilla?
- A core team, led by Dave Miller (justdave@netscape.com).
+ A core team, led by Dave Miller (justdave@bugzilla.org).
A.1.6. How does Bugzilla stack up against other bug-tracking
databases?
replace the old keyword name with a new one. This will cause a problem
with the keyword cache. Run sanitycheck.cgi to fix it.
+ A.7.6. Why can't I close bugs from the "Change Several Bugs at Once"
+ page?
+
+ The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
+ You can mass-CLOSE bugs from the change several bugs at once page.
+ but, every bug listed on the page has to be in VERIFIED state before
+ the control to do it will show up on the form. You can also
+ mass-VERIFY, but every bug listed has to be RESOLVED in order for the
+ control to show up on the form. The logic behind this is that if you
+ pick one of the bugs that's not VERIFIED and try to CLOSE it, the bug
+ change will fail miserably (thus killing any changes in the list after
+ it while doing the bulk change) so it doesn't even give you the
+ choice.
+
8. Bugzilla Hacking
A.8.1. What bugs are in Bugzilla right now?
B.2. MySQL Bugzilla Database Introduction
- This information comes straight from my life. I was forced to learn
- how Bugzilla organizes database because of nitpicky requests from
- users for tiny changes in wording, rather than having people
- re-educate themselves or figure out how to work our procedures around
- the tool. It sucks, but it can and will happen to you, so learn how
- the schema works and deal with it when it comes.
-
- So, here you are with your brand-new installation of Bugzilla. You've
- got MySQL set up, Apache working right, Perl DBI and DBD talking to
- the database flawlessly. Maybe you've even entered a few test bugs to
- make sure email's working; people seem to be notified of new bugs and
- changes, and you can enter and edit bugs to your heart's content.
- Perhaps you've gone through the trouble of setting up a gateway for
- people to submit bugs to your database via email, have had a few
- people test it, and received rave reviews from your beta testers.
-
- What's the next thing you do? Outline a training strategy for your
- development team, of course, and bring them up to speed on the new
- tool you've labored over for hours.
-
- Your first training session starts off very well! You have a captive
- audience which seems enraptured by the efficiency embodied in this
- thing called "Bugzilla". You are caught up describing the nifty
- features, how people can save favorite queries in the database, set
- them up as headers and footers on their pages, customize their
- layouts, generate reports, track status with greater efficiency than
- ever before, leap tall buildings with a single bound and rescue Jane
- from the clutches of Certain Death!
-
- But Certain Death speaks up -- a tiny voice, from the dark corners of
- the conference room. "I have a concern," the voice hisses from the
- darkness, "about the use of the word 'verified'.
-
- The room, previously filled with happy chatter, lapses into
- reverential silence as Certain Death (better known as the Vice
- President of Software Engineering) continues. "You see, for two years
- we've used the word 'verified' to indicate that a developer or quality
- assurance engineer has confirmed that, in fact, a bug is valid. I
- don't want to lose two years of training to a new software product.
- You need to change the bug status of 'verified' to 'approved' as soon
- as possible. To avoid confusion, of course."
-
- Oh no! Terror strikes your heart, as you find yourself mumbling "yes,
- yes, I don't think that would be a problem," You review the changes
- with Certain Death, and continue to jabber on, "no, it's not too big a
- change. I mean, we have the source code, right? You know, 'Use the
- Source, Luke' and all that... no problem," All the while you quiver
- inside like a beached jellyfish bubbling, burbling, and boiling on a
- hot Jamaican sand dune...
-
- Thus begins your adventure into the heart of Bugzilla. You've been
- forced to learn about non-portable enum() fields, varchar columns, and
- tinyint definitions. The Adventure Awaits You!
+This information comes straight from my life. I was forced to learn how
+Bugzilla organizes database because of nitpicky requests from users for tiny
+changes in wording, rather than having people re-educate themselves or
+figure out how to work our procedures around the tool. It sucks, but it can
+and will happen to you, so learn how the schema works and deal with it when
+it comes.
+
+So, here you are with your brand-new installation of Bugzilla. You've got
+MySQL set up, Apache working right, Perl DBI and DBD talking to the database
+flawlessly. Maybe you've even entered a few test bugs to make sure email's
+working; people seem to be notified of new bugs and changes, and you can
+enter and edit bugs to your heart's content. Perhaps you've gone through the
+trouble of setting up a gateway for people to submit bugs to your database
+via email, have had a few people test it, and received rave reviews from
+your beta testers.
+
+What's the next thing you do? Outline a training strategy for your
+development team, of course, and bring them up to speed on the new tool
+you've labored over for hours.
+
+Your first training session starts off very well! You have a captive
+audience which seems enraptured by the efficiency embodied in this thing
+called "Bugzilla". You are caught up describing the nifty features, how
+people can save favorite queries in the database, set them up as headers and
+footers on their pages, customize their layouts, generate reports, track
+status with greater efficiency than ever before, leap tall buildings with a
+single bound and rescue Jane from the clutches of Certain Death!
+
+But Certain Death speaks up -- a tiny voice, from the dark corners of the
+conference room. "I have a concern," the voice hisses from the darkness,
+"about the use of the word 'verified'.
+
+The room, previously filled with happy chatter, lapses into reverential
+silence as Certain Death (better known as the Vice President of Software
+Engineering) continues. "You see, for two years we've used the word
+'verified' to indicate that a developer or quality assurance engineer has
+confirmed that, in fact, a bug is valid. I don't want to lose two years of
+training to a new software product. You need to change the bug status of
+'verified' to 'approved' as soon as possible. To avoid confusion, of
+course."
+
+Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
+don't think that would be a problem," You review the changes with Certain
+Death, and continue to jabber on, "no, it's not too big a change. I mean, we
+have the source code, right? You know, 'Use the Source, Luke' and all
+that... no problem," All the while you quiver inside like a beached
+jellyfish bubbling, burbling, and boiling on a hot Jamaican sand dune...
+
+Thus begins your adventure into the heart of Bugzilla. You've been forced to
+learn about non-portable enum() fields, varchar columns, and tinyint
+definitions. The Adventure Awaits You!
_________________________________________________________________
B.2.1. Bugzilla Database Basics
- If you were like me, at this point you're totally clueless about the
- internals of MySQL, and if it weren't for this executive order from
- the Vice President you couldn't care less about the difference between
- a "bigint" and a "tinyint" entry in MySQL. I recommend you refer to
- the MySQL documentation, available at MySQL.com . Below are the basics
- you need to know about the Bugzilla database. Check the chart above
- for more details.
+If you were like me, at this point you're totally clueless about the
+internals of MySQL, and if it weren't for this executive order from the Vice
+President you couldn't care less about the difference between a "bigint" and
+a "tinyint" entry in MySQL. I recommend you refer to the MySQL
+documentation, available at MySQL.com . Below are the basics you need to
+know about the Bugzilla database. Check the chart above for more details.
1. To connect to your database:
bash# mysql -u root
B.2.1.1. Bugzilla Database Tables
- Imagine your MySQL database as a series of spreadsheets, and you won't
- be too far off. If you use this command:
+Imagine your MySQL database as a series of spreadsheets, and you won't be
+too far off. If you use this command:
- mysql> show tables from bugs;
+mysql> show tables from bugs;
- you'll be able to see the names of all the "spreadsheets" (tables) in
- your database.
+you'll be able to see the names of all the "spreadsheets" (tables) in your
+database.
+
+From the command issued above, ou should have some output that looks like
+this:
- From the command issued above, ou should have some output that looks
- like this:
+-------------------+
| Tables in bugs |
+-------------------+
Appendix C. Useful Patches and Utilities for Bugzilla
- Are you looking for a way to put your Bugzilla into overdrive? Catch
- some of the niftiest tricks here in this section.
+Are you looking for a way to put your Bugzilla into overdrive? Catch some of
+the niftiest tricks here in this section.
_________________________________________________________________
C.1. Apache mod_rewrite magic
- Apache's mod_rewrite module lets you do some truly amazing things with
- URL rewriting. Here are a couple of examples of what you can do.
+Apache's mod_rewrite module lets you do some truly amazing things with URL
+rewriting. Here are a couple of examples of what you can do.
1. Make it so if someone types http://www.foo.com/12345 , Bugzilla
spits back http://www.foo.com/show_bug.cgi?id=12345. Try setting
C.2. Command-line Bugzilla Queries
- There are a suite of Unix utilities for querying Bugzilla from the
- command line. They live in the contrib/cmdline directory. However,
- they have not yet been updated to work with 2.16
- (post-templatisation.). There are three files - query.conf, buglist
- and bugs.
-
- query.conf contains the mapping from options to field names and
- comparison types. Quoted option names are "grepped" for, so it should
- be easy to edit this file. Comments (#) have no effect; you must make
- sure these lines do not contain any quoted "option".
-
- buglist is a shell script which submits a Bugzilla query and writes
- the resulting HTML page to stdout. It supports both short options,
- (such as "-Afoo" or "-Rbar") and long options (such as
- "--assignedto=foo" or "--reporter=bar"). If the first character of an
- option is not "-", it is treated as if it were prefixed with
- "--default=".
-
- The column list is taken from the COLUMNLIST environment variable.
- This is equivalent to the "Change Columns" option when you list bugs
- in buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
- in your cookies file to see your current COLUMNLIST setting.
-
- bugs is a simple shell script which calls buglist and extracts the bug
- numbers from the output. Adding the prefix
- "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list
- into a working link if any bugs are found. Counting bugs is easy. Pipe
- the results through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
-
- Akkana Peck says she has good results piping buglist output through
- w3m -T text/html -dump
+There are a suite of Unix utilities for querying Bugzilla from the command
+line. They live in the contrib/cmdline directory. However, they have not yet
+been updated to work with 2.16 (post-templatisation.). There are three files
+- query.conf, buglist and bugs.
+
+query.conf contains the mapping from options to field names and comparison
+types. Quoted option names are "grepped" for, so it should be easy to edit
+this file. Comments (#) have no effect; you must make sure these lines do
+not contain any quoted "option".
+
+buglist is a shell script which submits a Bugzilla query and writes the
+resulting HTML page to stdout. It supports both short options, (such as
+"-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or
+"--reporter=bar"). If the first character of an option is not "-", it is
+treated as if it were prefixed with "--default=".
+
+The column list is taken from the COLUMNLIST environment variable. This is
+equivalent to the "Change Columns" option when you list bugs in buglist.cgi.
+If you have already used Bugzilla, grep for COLUMNLIST in your cookies file
+to see your current COLUMNLIST setting.
+
+bugs is a simple shell script which calls buglist and extracts the bug
+numbers from the output. Adding the prefix
+"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into a
+working link if any bugs are found. Counting bugs is easy. Pipe the results
+through sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'
+
+Akkana Peck says she has good results piping buglist output through w3m -T
+text/html -dump
_________________________________________________________________
Appendix D. Bugzilla Variants and Competitors
- I created this section to answer questions about Bugzilla competitors
- and variants, then found a wonderful site which covers an awful lot of
- what I wanted to discuss. Rather than quote it in its entirety, I'll
- simply refer you here: http://linas.org/linux/pm.html
+I created this section to answer questions about Bugzilla competitors and
+variants, then found a wonderful site which covers an awful lot of what I
+wanted to discuss. Rather than quote it in its entirety, I'll simply refer
+you here: http://linas.org/linux/pm.html
_________________________________________________________________
D.1. Red Hat Bugzilla
- Red Hat's old fork of Bugzilla which was based on version 2.8 is now
- obsolete. The newest version in use is based on version 2.17.1 and is
- in the process of being integrated into the main Bugzilla source tree.
- The back-end is modified to work with PostgreSQL instead of MySQL and
- they have custom templates to get their desired look and feel, but
- other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put
- forth a great deal of effort to make sure that the changes he made
- could be integrated back into the main tree. Bug 98304 exists to track
- this integration.
+Red Hat's old fork of Bugzilla which was based on version 2.8 is now
+obsolete. The newest version in use is based on version 2.17.1 and is in the
+process of being integrated into the main Bugzilla source tree. The back-end
+is modified to work with PostgreSQL instead of MySQL and they have custom
+templates to get their desired look and feel, but other than that it is
+Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of effort
+to make sure that the changes he made could be integrated back into the main
+tree. Bug 98304 exists to track this integration.
- URL: http://bugzilla.redhat.com/bugzilla/
+URL: http://bugzilla.redhat.com/bugzilla/
- This section last updated 24 Dec 2002
+This section last updated 24 Dec 2002
_________________________________________________________________
D.2. Loki Bugzilla (Fenris)
- Fenris was a fork from Bugzilla made by Loki Games; when Loki went
- into receivership, it died. While Loki's other code lives on, its
- custodians recommend Bugzilla for future bug-tracker deployments.
+Fenris was a fork from Bugzilla made by Loki Games; when Loki went into
+receivership, it died. While Loki's other code lives on, its custodians
+recommend Bugzilla for future bug-tracker deployments.
- This section last updated 27 Jul 2002
+This section last updated 27 Jul 2002
_________________________________________________________________
D.3. Issuezilla
- Issuezilla was another fork from Bugzilla, made by collab.net and
- hosted at tigris.org. It is also dead; the primary focus of
- bug-tracking at tigris.org is their Java-based bug-tracker, Section
- D.4.
+Issuezilla was another fork from Bugzilla, made by collab.net and hosted at
+tigris.org. It is also dead; the primary focus of bug-tracking at tigris.org
+is their Java-based bug-tracker, Section D.4.
- This section last updated 27 Jul 2002
+This section last updated 27 Jul 2002
_________________________________________________________________
D.4. Scarab
- Scarab is a new open source bug-tracking system built using Java
- Servlet technology. It is currently at version 1.0 beta 13.
+Scarab is a new open source bug-tracking system built using Java Servlet
+technology. It is currently at version 1.0 beta 13.
- URL: http://scarab.tigris.org
+URL: http://scarab.tigris.org
- This section last updated 18 Jan 2003
+This section last updated 18 Jan 2003
_________________________________________________________________
D.5. Perforce SCM
- Although Perforce isn't really a bug tracker, it can be used as such
- through the "jobs" functionality.
+Although Perforce isn't really a bug tracker, it can be used as such through
+the "jobs" functionality.
- URL: http://www.perforce.com/perforce/technotes/note052.html
+URL: http://www.perforce.com/perforce/technotes/note052.html
- This section last updated 27 Jul 2002
+This section last updated 27 Jul 2002
_________________________________________________________________
D.6. SourceForge
- SourceForge is a way of coordinating geographically distributed free
- software and open source projects over the Internet. It has a built-in
- bug tracker, but it's not highly thought of.
+SourceForge is a way of coordinating geographically distributed free
+software and open source projects over the Internet. It has a built-in bug
+tracker, but it's not highly thought of.
- URL: http://www.sourceforge.net
+URL: http://www.sourceforge.net
- This section last updated 27 Jul 2002
+This section last updated 27 Jul 2002
_________________________________________________________________
Appendix E. GNU Free Documentation License
- Version 1.1, March 2000
+Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy
0. PREAMBLE
- The purpose of this License is to make a manual, textbook, or other
- written document "free" in the sense of freedom: to assure everyone
- the effective freedom to copy and redistribute it, with or without
- modifying it, either commercially or noncommercially. Secondarily,
- this License preserves for the author and publisher a way to get
- credit for their work, while not being considered responsible for
- modifications made by others.
-
- This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft
- license designed for free software.
-
- We have designed this License in order to use it for manuals for free
- software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals; it
- can be used for any textual work, regardless of subject matter or
- whether it is published as a printed book. We recommend this License
- principally for works whose purpose is instruction or reference.
+The purpose of this License is to make a manual, textbook, or other written
+document "free" in the sense of freedom: to assure everyone the effective
+freedom to copy and redistribute it, with or without modifying it, either
+commercially or noncommercially. Secondarily, this License preserves for the
+author and publisher a way to get credit for their work, while not being
+considered responsible for modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative works of
+the document must themselves be free in the same sense. It complements the
+GNU General Public License, which is a copyleft license designed for free
+software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free program
+should come with manuals providing the same freedoms that the software does.
+But this License is not limited to software manuals; it can be used for any
+textual work, regardless of subject matter or whether it is published as a
+printed book. We recommend this License principally for works whose purpose
+is instruction or reference.
_________________________________________________________________
1. APPLICABILITY AND DEFINITIONS
- This License applies to any manual or other work that contains a
- notice placed by the copyright holder saying it can be distributed
- under the terms of this License. The "Document", below, refers to any
- such manual or work. Any member of the public is a licensee, and is
- addressed as "you".
-
- A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.
-
- A "Secondary Section" is a named appendix or a front-matter section of
- the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall
- subject (or to related matters) and contains nothing that could fall
- directly within that overall subject. (For example, if the Document is
- in part a textbook of mathematics, a Secondary Section may not explain
- any mathematics.) The relationship could be a matter of historical
- connection with the subject or with related matters, or of legal,
- commercial, philosophical, ethical or political position regarding
- them.
-
- The "Invariant Sections" are certain Secondary Sections whose titles
- are designated, as being those of Invariant Sections, in the notice
- that says that the Document is released under this License.
-
- The "Cover Texts" are certain short passages of text that are listed,
- as Front-Cover Texts or Back-Cover Texts, in the notice that says that
- the Document is released under this License.
-
- A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the
- general public, whose contents can be viewed and edited directly and
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or
- for automatic translation to a variety of formats suitable for input
- to text formatters. A copy made in an otherwise Transparent file
- format whose markup has been designed to thwart or discourage
- subsequent modification by readers is not Transparent. A copy that is
- not "Transparent" is called "Opaque".
-
- Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML
- or XML using a publicly available DTD, and standard-conforming simple
- HTML designed for human modification. Opaque formats include
- PostScript, PDF, proprietary formats that can be read and edited only
- by proprietary word processors, SGML or XML for which the DTD and/or
- processing tools are not generally available, and the
- machine-generated HTML produced by some word processors for output
- purposes only.
-
- The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in
- formats which do not have any title page as such, "Title Page" means
- the text near the most prominent appearance of the work's title,
- preceding the beginning of the body of the text.
+This License applies to any manual or other work that contains a notice
+placed by the copyright holder saying it can be distributed under the terms
+of this License. The "Document", below, refers to any such manual or work.
+Any member of the public is a licensee, and is addressed as "you".
+
+A "Modified Version" of the Document means any work containing the Document
+or a portion of it, either copied verbatim, or with modifications and/or
+translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of the
+Document that deals exclusively with the relationship of the publishers or
+authors of the Document to the Document's overall subject (or to related
+matters) and contains nothing that could fall directly within that overall
+subject. (For example, if the Document is in part a textbook of mathematics,
+a Secondary Section may not explain any mathematics.) The relationship could
+be a matter of historical connection with the subject or with related
+matters, or of legal, commercial, philosophical, ethical or political
+position regarding them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles are
+designated, as being those of Invariant Sections, in the notice that says
+that the Document is released under this License.
+
+The "Cover Texts" are certain short passages of text that are listed, as
+Front-Cover Texts or Back-Cover Texts, in the notice that says that the
+Document is released under this License.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the general
+public, whose contents can be viewed and edited directly and
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or for
+automatic translation to a variety of formats suitable for input to text
+formatters. A copy made in an otherwise Transparent file format whose markup
+has been designed to thwart or discourage subsequent modification by readers
+is not Transparent. A copy that is not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain ASCII
+without markup, Texinfo input format, LaTeX input format, SGML or XML using
+a publicly available DTD, and standard-conforming simple HTML designed for
+human modification. Opaque formats include PostScript, PDF, proprietary
+formats that can be read and edited only by proprietary word processors,
+SGML or XML for which the DTD and/or processing tools are not generally
+available, and the machine-generated HTML produced by some word processors
+for output purposes only.
+
+The "Title Page" means, for a printed book, the title page itself, plus such
+following pages as are needed to hold, legibly, the material this License
+requires to appear in the title page. For works in formats which do not have
+any title page as such, "Title Page" means the text near the most prominent
+appearance of the work's title, preceding the beginning of the body of the
+text.
_________________________________________________________________
2. VERBATIM COPYING
- You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies
- to the Document are reproduced in all copies, and that you add no
- other conditions whatsoever to those of this License. You may not use
- technical measures to obstruct or control the reading or further
- copying of the copies you make or distribute. However, you may accept
- compensation in exchange for copies. If you distribute a large enough
- number of copies you must also follow the conditions in section 3.
-
- You may also lend copies, under the same conditions stated above, and
- you may publicly display copies.
+You may copy and distribute the Document in any medium, either commercially
+or noncommercially, provided that this License, the copyright notices, and
+the license notice saying this License applies to the Document are
+reproduced in all copies, and that you add no other conditions whatsoever to
+those of this License. You may not use technical measures to obstruct or
+control the reading or further copying of the copies you make or distribute.
+However, you may accept compensation in exchange for copies. If you
+distribute a large enough number of copies you must also follow the
+conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and you
+may publicly display copies.
_________________________________________________________________
3. COPYING IN QUANTITY
- If you publish printed copies of the Document numbering more than 100,
- and the Document's license notice requires Cover Texts, you must
- enclose the copies in covers that carry, clearly and legibly, all
- these Cover Texts: Front-Cover Texts on the front cover, and
- Back-Cover Texts on the back cover. Both covers must also clearly and
- legibly identify you as the publisher of these copies. The front cover
- must present the full title with all words of the title equally
- prominent and visible. You may add other material on the covers in
- addition. Copying with changes limited to the covers, as long as they
- preserve the title of the Document and satisfy these conditions, can
- be treated as verbatim copying in other respects.
-
- If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit
- reasonably) on the actual cover, and continue the rest onto adjacent
- pages.
-
- If you publish or distribute Opaque copies of the Document numbering
- more than 100, you must either include a machine-readable Transparent
- copy along with each Opaque copy, or state in or with each Opaque copy
- a publicly-accessible computer-network location containing a complete
- Transparent copy of the Document, free of added material, which the
- general network-using public has access to download anonymously at no
- charge using public-standard network protocols. If you use the latter
- option, you must take reasonably prudent steps, when you begin
- distribution of Opaque copies in quantity, to ensure that this
- Transparent copy will remain thus accessible at the stated location
- until at least one year after the last time you distribute an Opaque
- copy (directly or through your agents or retailers) of that edition to
- the public.
-
- It is requested, but not required, that you contact the authors of the
- Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.
+If you publish printed copies of the Document numbering more than 100, and
+the Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover Texts:
+Front-Cover Texts on the front cover, and Back-Cover Texts on the back
+cover. Both covers must also clearly and legibly identify you as the
+publisher of these copies. The front cover must present the full title with
+all words of the title equally prominent and visible. You may add other
+material on the covers in addition. Copying with changes limited to the
+covers, as long as they preserve the title of the Document and satisfy these
+conditions, can be treated as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit legibly,
+you should put the first ones listed (as many as fit reasonably) on the
+actual cover, and continue the rest onto adjacent pages.
+
+If you publish or distribute Opaque copies of the Document numbering more
+than 100, you must either include a machine-readable Transparent copy along
+with each Opaque copy, or state in or with each Opaque copy a
+publicly-accessible computer-network location containing a complete
+Transparent copy of the Document, free of added material, which the general
+network-using public has access to download anonymously at no charge using
+public-standard network protocols. If you use the latter option, you must
+take reasonably prudent steps, when you begin distribution of Opaque copies
+in quantity, to ensure that this Transparent copy will remain thus
+accessible at the stated location until at least one year after the last
+time you distribute an Opaque copy (directly or through your agents or
+retailers) of that edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give them
+a chance to provide you with an updated version of the Document.
_________________________________________________________________
4. MODIFICATIONS
- You may copy and distribute a Modified Version of the Document under
- the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution
- and modification of the Modified Version to whoever possesses a copy
- of it. In addition, you must do these things in the Modified Version:
+You may copy and distribute a Modified Version of the Document under the
+conditions of sections 2 and 3 above, provided that you release the Modified
+Version under precisely this License, with the Modified Version filling the
+role of the Document, thus licensing distribution and modification of the
+Modified Version to whoever possesses a copy of it. In addition, you must do
+these things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
5. COMBINING DOCUMENTS
- You may combine the Document with other documents released under this
- License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and
- list them all as Invariant Sections of your combined work in its
- license notice.
-
- The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single
- copy. If there are multiple Invariant Sections with the same name but
- different contents, make the title of each such section unique by
- adding at the end of it, in parentheses, the name of the original
- author or publisher of that section if known, or else a unique number.
- Make the same adjustment to the section titles in the list of
- Invariant Sections in the license notice of the combined work.
-
- In the combination, you must combine any sections entitled "History"
- in the various original documents, forming one section entitled
- "History"; likewise combine any sections entitled "Acknowledgements",
- and any sections entitled "Dedications". You must delete all sections
- entitled "Endorsements."
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified versions,
+provided that you include in the combination all of the Invariant Sections
+of all of the original documents, unmodified, and list them all as Invariant
+Sections of your combined work in its license notice.
+
+The combined work need only contain one copy of this License, and multiple
+identical Invariant Sections may be replaced with a single copy. If there
+are multiple Invariant Sections with the same name but different contents,
+make the title of each such section unique by adding at the end of it, in
+parentheses, the name of the original author or publisher of that section if
+known, or else a unique number. Make the same adjustment to the section
+titles in the list of Invariant Sections in the license notice of the
+combined work.
+
+In the combination, you must combine any sections entitled "History" in the
+various original documents, forming one section entitled "History"; likewise
+combine any sections entitled "Acknowledgements", and any sections entitled
+"Dedications". You must delete all sections entitled "Endorsements."
_________________________________________________________________
6. COLLECTIONS OF DOCUMENTS
- You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual
- copies of this License in the various documents with a single copy
- that is included in the collection, provided that you follow the rules
- of this License for verbatim copying of each of the documents in all
- other respects.
-
- You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a
- copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in the
+collection, provided that you follow the rules of this License for verbatim
+copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute it
+individually under this License, provided you insert a copy of this License
+into the extracted document, and follow this License in all other respects
+regarding verbatim copying of that document.
_________________________________________________________________
7. AGGREGATION WITH INDEPENDENT WORKS
- A compilation of the Document or its derivatives with other separate
- and independent documents or works, in or on a volume of a storage or
- distribution medium, does not as a whole count as a Modified Version
- of the Document, provided no compilation copyright is claimed for the
- compilation. Such a compilation is called an "aggregate", and this
- License does not apply to the other self-contained works thus compiled
- with the Document, on account of their being thus compiled, if they
- are not themselves derivative works of the Document.
-
- If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one quarter
- of the entire aggregate, the Document's Cover Texts may be placed on
- covers that surround only the Document within the aggregate. Otherwise
- they must appear on covers around the whole aggregate.
+A compilation of the Document or its derivatives with other separate and
+independent documents or works, in or on a volume of a storage or
+distribution medium, does not as a whole count as a Modified Version of the
+Document, provided no compilation copyright is claimed for the compilation.
+Such a compilation is called an "aggregate", and this License does not apply
+to the other self-contained works thus compiled with the Document, on
+account of their being thus compiled, if they are not themselves derivative
+works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these copies of
+the Document, then if the Document is less than one quarter of the entire
+aggregate, the Document's Cover Texts may be placed on covers that surround
+only the Document within the aggregate. Otherwise they must appear on covers
+around the whole aggregate.
_________________________________________________________________
8. TRANSLATION
- Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include
- translations of some or all Invariant Sections in addition to the
- original versions of these Invariant Sections. You may include a
- translation of this License provided that you also include the
- original English version of this License. In case of a disagreement
- between the translation and the original English version of this
- License, the original English version will prevail.
+Translation is considered a kind of modification, so you may distribute
+translations of the Document under the terms of section 4. Replacing
+Invariant Sections with translations requires special permission from their
+copyright holders, but you may include translations of some or all Invariant
+Sections in addition to the original versions of these Invariant Sections.
+You may include a translation of this License provided that you also include
+the original English version of this License. In case of a disagreement
+between the translation and the original English version of this License,
+the original English version will prevail.
_________________________________________________________________
9. TERMINATION
- You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided for under this License. Any other attempt
- to copy, modify, sublicense or distribute the Document is void, and
- will automatically terminate your rights under this License. However,
- parties who have received copies, or rights, from you under this
- License will not have their licenses terminated so long as such
- parties remain in full compliance.
+You may not copy, modify, sublicense, or distribute the Document except as
+expressly provided for under this License. Any other attempt to copy,
+modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License. However, parties who
+have received copies, or rights, from you under this License will not have
+their licenses terminated so long as such parties remain in full compliance.
_________________________________________________________________
10. FUTURE REVISIONS OF THIS LICENSE
- The Free Software Foundation may publish new, revised versions of the
- GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- http://www.gnu.org/copyleft/ .
-
- Each version of the License is given a distinguishing version number.
- If the Document specifies that a particular numbered version of this
- License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or
- of any later version that has been published (not as a draft) by the
- Free Software Foundation. If the Document does not specify a version
- number of this License, you may choose any version ever published (not
- as a draft) by the Free Software Foundation.
+The Free Software Foundation may publish new, revised versions of the GNU
+Free Documentation License from time to time. Such new versions will be
+similar in spirit to the present version, but may differ in detail to
+address new problems or concerns. See http://www.gnu.org/copyleft/ .
+
+Each version of the License is given a distinguishing version number. If the
+Document specifies that a particular numbered version of this License "or
+any later version" applies to it, you have the option of following the terms
+and conditions either of that specified version or of any later version that
+has been published (not as a draft) by the Free Software Foundation. If the
+Document does not specify a version number of this License, you may choose
+any version ever published (not as a draft) by the Free Software Foundation.
_________________________________________________________________
How to use this License for your documents
- To use this License in a document you have written, include a copy of
- the License in the document and put the following copyright and
- license notices just after the title page:
+To use this License in a document you have written, include a copy of the
+License in the document and put the following copyright and license notices
+just after the title page:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
distribute and/or modify this document under the terms of the GNU
projects / thirdparty / bugzilla.git / commitdiff
