This is the documentation for Bugzilla, the mozilla.org
@@ -504,21 +495,15 @@ HREF="#upgrade-patches"
CLASS="chapter"
>
Chapter 1. About This Guide
Chapter 1. About This Guide
1.1. Copyright Information
1.1. Copyright Information
1.2. Disclaimer
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.
@@ -624,9 +607,7 @@ CLASS="section"
>
1.3. New Versions
1.3. New Versions
This is the 2.17.5 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
@@ -685,9 +666,7 @@ CLASS="section"
>
1.4. Credits
1.4. Credits
The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
@@ -811,17 +790,13 @@ CLASS="section"
>
1.5. Document Conventions
1.5. Document Conventions
This document uses the following conventions:
Chapter 2. Introduction
Chapter 2. Introduction
2.1. What is Bugzilla?
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
@@ -1265,9 +1236,7 @@ CLASS="section"
>
2.2. Why Should We Use Bugzilla?
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
@@ -1339,17 +1308,13 @@ TARGET="_top"
CLASS="chapter"
>
Chapter 3. Using Bugzilla
Chapter 3. Using Bugzilla
3.1. How do I use Bugzilla?
3.1. How do I use Bugzilla?
This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
@@ -1368,9 +1333,7 @@ CLASS="section"
>
3.1.1. Create a Bugzilla Account
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
@@ -1438,9 +1401,7 @@ CLASS="section"
>
3.1.2. Anatomy of a Bug
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.
@@ -1705,9 +1666,7 @@ CLASS="section"
>
3.1.3. Searching for Bugs
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
@@ -1735,9 +1694,7 @@ CLASS="section"
>
3.1.4. Bug Lists
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
@@ -1809,9 +1766,7 @@ CLASS="section"
>
3.1.5. Filing Bugs
3.1.5. Filing Bugs
Years of bug writing experience has been distilled for your
reading pleasure into the
@@ -1864,15 +1819,163 @@ TARGET="_top"
>
Viewing and reviewing patches in Bugzilla is often difficult due to
+ lack of context, improper format and the inherent readability issues that
+ raw patches present. Patch Viewer is an enhancement to Bugzilla designed
+ to fix that by offering increased context, linking to sections, and
+ integrating with Bonsai, LXR and CVS.
Patch viewer allows you to:
View patches in color, with side-by-side view rather than trying
+ to interpret the contents of the patch.
See the difference between two patches.
Get more context in a patch.
Collapse and expand sections of a patch for easy
+ reading.
Link to a particular section of a patch for discussion or
+ review
Go to Bonsai or LXR to see more context, blame, and
+ cross-references for the part of the patch you are looking at
Create a rawtext unified format diff out of any patch, no
+ matter what format it came from
The main way to view a patch in patch viewer is to click on the
+ "Diff" link next to a patch in the Attachments list on a bug. You may
+ also do this within the edit window by clicking the "View Attachment As
+ Diff" button in the Edit Attachment screen.
To see the difference between two patches, you must first view the
+ newer patch in Patch Viewer. Then select the older patch from the
+ dropdown at the top of the page ("Differences between [dropdown] and
+ this patch") and click the "Diff" button. This will show you what
+ is new or changed in the newer patch.
To get more context in a patch, you put a number in the textbox at
+ the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
+ This will give you that many lines of context before and after each
+ change. Alternatively, you can click on the "File" link there and it
+ will show each change in the full context of the file. This feature only
+ works against files that were diffed using "cvs diff".
To view only a certain set of files in a patch (for example, if a
+ patch is absolutely huge and you want to only review part of it at a
+ time), you can click the "(+)" and "(-)" links next to each file (to
+ expand it or collapse it). If you want to collapse all files or expand
+ all files, you can click the "Collapse All" and "Expand All" links at the
+ top of the page.
To link to a section of a patch (for example, if you want to be
+ able to give someone a URL to show them which part you are talking
+ about) you simply click the "Link Here" link on the section header. The
+ resulting URL can be copied and used in discussion. (Copy Link
+ Location in Mozilla works as well.)
To go to Bonsai to get blame for the lines you are interested in,
+ you can click the "Lines XX-YY" link on the section header you are
+ interested in. This works even if the patch is against an old
+ version of the file, since Bonsai stores all versions of the file.
To go to LXR, you click on the filename on the file header
+ (unfortunately, since LXR only does the most recent version, line
+ numbers are likely to rot).
If the patch is not in a format that you like, you can turn it
+ into a unified diff format by clicking the "Raw Unified" link at the top
+ of the page.
3.2. Hints and Tips
3.2. Hints and Tips
This section distills some Bugzilla tips and best practices
that have been developed.
3.2.1. Autolinkification
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.
@@ -1946,9 +2047,7 @@ CLASS="section"
>
3.2.2. Quicksearch
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
@@ -1979,9 +2078,7 @@ CLASS="section"
>
3.2.3. Comments
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.
@@ -2003,9 +2100,7 @@ CLASS="section"
>
3.2.4. Attachments
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
@@ -2029,9 +2124,7 @@ CLASS="section"
>
3.2.5. Filing Bugs
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
@@ -2055,9 +2148,7 @@ CLASS="section"
>
3.3. User Preferences
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.
@@ -2067,9 +2158,7 @@ CLASS="section"
>
3.3.1. Account Settings
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
@@ -2092,9 +2181,7 @@ CLASS="section"
>
3.3.2. Email Settings
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
@@ -2141,9 +2228,7 @@ CLASS="section"
>
3.3.3. Page Footer
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.
@@ -2155,9 +2240,7 @@ CLASS="section"
>
3.3.4. Permissions
3.3.4. Permissions
This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
@@ -2170,17 +2253,13 @@ NAME="permissionsettings"
CLASS="chapter"
>
Chapter 4. Installation
Chapter 4. Installation
4.1. Step-by-step Install
4.1. Step-by-step Install
Bugzilla has been successfully installed under many different
operating systems including almost all Unix clones and
@@ -2334,9 +2413,7 @@ CLASS="section"
>
4.1.1. MySQL
4.1.1. MySQL
Visit the MySQL homepage at
Figure 4-1. Set Max Packet Size in MySQL
4.1.2. Perl
4.1.2. Perl
Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
4.1.3. Perl Modules
4.1.3. Perl Modules
Perl modules can be found using
Example 4-1. Installing perl modules with CPAN
4.1.3.1. Bundle::Bugzilla
4.1.3.1. Bundle::Bugzilla
If you are running at least perl 5.6.1, you can save yourself a lot
of time by using Bundle::Bugzilla. This bundle contains every module
@@ -2956,9 +3023,7 @@ CLASS="section"
>
4.1.3.2. AppConfig (1.52)
4.1.3.2. AppConfig (1.52)
Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
@@ -2969,9 +3034,7 @@ CLASS="section"
>
4.1.3.3. CGI (2.88)
4.1.3.3. CGI (2.88)
The CGI module parses form elements and cookies and does many
other usefule things. It come as a part of recent perl distributions, but
@@ -3002,9 +3065,7 @@ CLASS="section"
>
4.1.3.4. Data::Dumper (any)
4.1.3.4. Data::Dumper (any)
The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
@@ -3036,9 +3097,7 @@ CLASS="section"
>
4.1.3.5. TimeDate modules (2.21)
4.1.3.5. TimeDate modules (2.21)
Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
@@ -3071,9 +3130,7 @@ CLASS="section"
>
4.1.3.6. DBI (1.32)
4.1.3.6. DBI (1.32)
The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
@@ -3105,9 +3162,7 @@ CLASS="section"
>
4.1.3.7. MySQL-related modules
4.1.3.7. MySQL-related modules
The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
@@ -3150,9 +3205,7 @@ CLASS="section"
>
4.1.3.8. File::Spec (0.82)
4.1.3.8. File::Spec (0.82)
File::Spec is a perl module that allows file operations, such as
generating full path names, to work cross platform.
@@ -3182,9 +3235,7 @@ CLASS="section"
>
4.1.3.9. File::Temp (any)
4.1.3.9. File::Temp (any)
File::Temp is used to generate a temporary filename that is
guaranteed to be unique. It comes as a standard part of perl
@@ -3214,9 +3265,7 @@ CLASS="section"
>
4.1.3.10. Template Toolkit (2.08)
4.1.3.10. Template Toolkit (2.08)
When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
@@ -3248,9 +3297,7 @@ CLASS="section"
>
4.1.3.11. Text::Wrap (2001.0131)
4.1.3.11. Text::Wrap (2001.0131)
Text::Wrap is designed to proved intelligent text wrapping.
4.1.3.12. GD (1.20) [optional]
4.1.3.12. GD (1.20) [optional]
The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
@@ -3384,9 +3429,7 @@ CLASS="section"
>
4.1.3.13. Chart::Base (0.99c) [optional]
4.1.3.13. Chart::Base (0.99c) [optional]
The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
@@ -3413,9 +3456,7 @@ CLASS="section"
>
4.1.3.14. XML::Parser (any) [Optional]
4.1.3.14. XML::Parser (any) [Optional]
XML::Parser is used by the
4.1.3.15. GD::Graph (any) [Optional]
4.1.3.15. GD::Graph (any) [Optional]
In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
@@ -3480,9 +3519,7 @@ CLASS="section"
>
4.1.3.16. GD::Text::Align (any) [Optional]
4.1.3.16. GD::Text::Align (any) [Optional]
GD::Text::Align, as the name implies, is used to draw aligned
strings of text. It is needed by the reporting interface.
@@ -3512,9 +3549,7 @@ CLASS="section"
>
4.1.3.17. MIME::Parser (any) [Optional]
4.1.3.17. MIME::Parser (any) [Optional]
MIME::Parser is only needed if you want to use the e-mail interface
located in the
4.1.3.18. PatchReader (0.9.1) [Optional]
4.1.3.18. PatchReader (0.9.1) [Optional]
PatchReader is only needed if you want to use Patch Viewer, a
Bugzilla feature to format patches in a pretty HTML fashion. There are a
@@ -3585,9 +3618,7 @@ CLASS="section"
>
4.1.4. HTTP Server
4.1.4. HTTP Server
You have freedom of choice here, pretty much any web server that
is capable of running
4.1.5. Bugzilla
4.1.5. Bugzilla
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
@@ -3757,9 +3786,7 @@ CLASS="section"
>
4.1.6. Setting Up the MySQL Database
4.1.6. 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
@@ -3914,9 +3941,7 @@ CLASS="section"
>
4.1.7. 4.1.7. checksetup.pl
4.1.8. Configuring Bugzilla
4.1.8. Configuring Bugzilla
You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
@@ -4082,17 +4105,13 @@ CLASS="section"
>
4.2. Optional Additional Configuration
4.2. Optional Additional Configuration
4.2.1. Dependency Charts
4.2.1. Dependency Charts
As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
@@ -4154,9 +4173,7 @@ CLASS="section"
>
4.2.2. Bug Graphs
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.
4.2.3. The Whining Cron
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
@@ -4302,9 +4317,7 @@ CLASS="section"
>
4.2.4. LDAP Authentication
4.2.4. LDAP Authentication
loginmethod
loginmethod
This parameter should be set to
LDAPserver
LDAPserver
This parameter should be set to the name (and optionally the
@@ -4476,9 +4485,7 @@ CLASS="QUOTE"
>
LDAPbinddn [Optional]
LDAPbinddn [Optional]
Some LDAP servers will not allow an anonymous bind to search
@@ -4494,9 +4501,7 @@ CLASS="QUOTE"
>
LDAPBaseDN
LDAPBaseDN
The LDAPBaseDN parameter should be set to the location in
@@ -4511,9 +4516,7 @@ CLASS="QUOTE"
>
LDAPuidattribute
LDAPuidattribute
The LDAPuidattribute parameter should be set to the attribute
@@ -4529,9 +4532,7 @@ CLASS="QUOTE"
>
LDAPmailattribute
LDAPmailattribute
The LDAPmailattribute parameter should be the name of the
@@ -4552,9 +4553,7 @@ CLASS="section"
>
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
It is possible for a Bugzilla to execute malicious Javascript
@@ -4658,9 +4657,7 @@ CLASS="section"
>
4.2.6. 4.2.6. directoryindex for the Bugzilla default page.
Many aspects of the Bugzilla installation can be affected by the
the operating system you choose to install it on. Sometimes it can be made
@@ -4776,9 +4767,7 @@ CLASS="section"
>
4.3.1. Microsoft Windows
4.3.1. Microsoft Windows
Making Bugzilla work on windows is still a very painful processes.
The Bugzilla Team is working to make it easier, but that goal is not
@@ -4802,9 +4791,7 @@ CLASS="section"
>
4.3.1.1. Win32 Perl
4.3.1.1. Win32 Perl
Perl for Windows can be obtained from
4.3.1.2. Perl Modules on Win32
4.3.1.2. Perl Modules on Win32
Bugzilla on Windows requires the same perl modules found in
4.3.1.3. Code changes required to run on win32
4.3.1.3. Code changes required to run on win32
Unfortunately, Bugzilla still doesn't run "out of the box" on
Windows. There is work in progress to make this easier, but until that
@@ -4955,9 +4938,7 @@ CLASS="section"
>
4.3.1.3.1. Changes to 4.3.1.3.1. Changes to checksetup.pl
4.3.1.3.2. Changes to 4.3.1.3.2. Changes to BugMail.pm
4.3.1.4. Serving the web pages
4.3.1.4. Serving the web pages
As is the case on Unix based systems, any web server should be
able to handle Bugzilla; however, the Bugzilla Team still recommends
@@ -5184,9 +5161,7 @@ CLASS="section"
>
4.3.2. 4.3.2. Mac OS X
4.3.3. Linux-Mandrake 8.0
4.3.3. Linux-Mandrake 8.0
Linux-Mandrake 8.0 includes every required and optional library
for Bugzilla. The easiest way to install them is by using the
@@ -5478,9 +5451,7 @@ CLASS="section"
>
4.4. HTTP Server Configuration
4.4. HTTP Server Configuration
The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
that can be configured to run
4.4.1. Apache 4.4.1. Apache httpd
Example 4-2.
4.4.2. Microsoft 4.4.2. Microsoft Internet Information Services
4.4.3. AOL Server
4.4.3. AOL Server
Ben FrantzDale reported success using AOL Server with Bugzilla. He
reported his experience and what appears below is based on that.
@@ -6041,9 +6004,7 @@ CLASS="section"
>
4.5. Troubleshooting
4.5. Troubleshooting
This section gives solutions to common Bugzilla installation
problems.
@@ -6053,9 +6014,7 @@ CLASS="section"
>
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
Try executing
4.5.2. DBD::Sponge::db prepare failed
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):
@@ -6164,9 +6121,7 @@ CLASS="section"
>
4.5.3. cannot chdir(/var/spool/mqueue)
4.5.3. cannot chdir(/var/spool/mqueue)
If you are installing Bugzilla on SuSE Linux, or some other
distributions with
@@ -6222,9 +6177,7 @@ CLASS="section"
>
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
This is caused by a bug in the version of
Figure 4-2. Other File::Temp error messages
Figure 4-3. Patch for File::Temp in Perl 5.6.0
Chapter 5. Administering Bugzilla
Chapter 5. Administering Bugzilla
5.1. Bugzilla Configuration
5.1. Bugzilla Configuration
Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
@@ -6620,17 +6565,13 @@ CLASS="section"
>
5.2. User Administration
5.2. User Administration
5.2.1. Creating the Default User
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
@@ -6673,17 +6614,13 @@ CLASS="section"
>
5.2.2. Managing Other Users
5.2.2. Managing Other Users
5.2.2.1. Creating new users
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
@@ -6754,9 +6691,7 @@ CLASS="section"
>
5.2.2.2. Modifying Users
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,
@@ -6985,17 +6920,13 @@ CLASS="section"
>
5.3. Product, Component, Milestone, and Version Administration
5.3. Product, Component, Milestone, and Version Administration
5.3.1. Products
5.3.1. Products
5.3.2. Components
5.3.2. Components
Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
@@ -7104,9 +7033,7 @@ CLASS="section"
>
5.3.3. Versions
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
@@ -7140,9 +7067,7 @@ CLASS="section"
>
5.3.4. Milestones
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
@@ -7243,9 +7168,7 @@ CLASS="section"
>
5.4. Voting
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.
@@ -7305,9 +7228,7 @@ CLASS="section"
>
5.5. Groups and Group Security
5.5. Groups and Group Security
Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
@@ -7487,9 +7408,7 @@ CLASS="section"
>
5.6. Bugzilla Security
5.6. Bugzilla Security
5.6.1. TCP/IP Ports
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
@@ -7606,9 +7523,7 @@ CLASS="section"
>
5.6.2. MySQL
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
@@ -7735,9 +7650,7 @@ CLASS="section"
>
5.6.3. Daemon Accounts
5.6.3. Daemon Accounts
Many daemons, such as Apache's httpd and MySQL's mysqld default to
running as either
5.6.4. Web Server Access Controls
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
@@ -8138,9 +8049,7 @@ CLASS="section"
>
5.7. Template Customization
5.7. Template Customization
One of the large changes for 2.16 was the templatization of the
entire user-facing UI, using the
@@ -8168,9 +8077,7 @@ CLASS="section"
>
5.7.1. What to Edit
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
@@ -8318,9 +8225,7 @@ CLASS="section"
>
5.7.2. How To Edit Templates
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
@@ -8400,9 +8305,7 @@ CLASS="section"
>
5.7.3. Template Formats
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
@@ -8462,9 +8365,7 @@ CLASS="section"
>
5.7.4. Particular Templates
5.7.4. Particular Templates
There are a few templates you may be particularly interested in
customizing for your installation.
@@ -8651,9 +8552,7 @@ CLASS="section"
>
5.7.5. Configuring Bugzilla to Detect the User's Language
5.7.5. Configuring Bugzilla to Detect the User's Language
Begining in version 2.18 (first introduced in version
2.17.4), it's now possible to have the users web browser tell Bugzilla
@@ -8694,9 +8593,7 @@ CLASS="section"
>
5.8. Change Permission Customization
5.8. Change Permission Customization
5.9. Upgrading to New Releases
5.9. Upgrading to New Releases
Example 5-1. Upgrading using CVS
Example 5-2. Upgrading using the tarball
Example 5-3. Upgrading using patches
5.10. Integrating Bugzilla with Third-Party Tools
5.10. Integrating Bugzilla with Third-Party Tools
5.10.1. Bonsai
5.10.1. Bonsai
Bonsai is a web-based tool for managing
5.10.2. CVS
5.10.2. CVS
CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.
5.10.3. Perforce SCM
5.10.3. Perforce SCM
You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
@@ -9505,9 +9386,7 @@ CLASS="section"
>
5.10.4. Tinderbox/Tinderbox2
5.10.4. Tinderbox/Tinderbox2
We need Tinderbox integration information.
Appendix A. The Bugzilla FAQ
Appendix A. The Bugzilla FAQ
This FAQ includes questions not covered elsewhere in the Guide.
How do I change a keyword in Bugzilla, once some bugs are using it?
A.1.6.
How does Bugzilla stack up against other bug-tracking databases?
@@ -10236,9 +10105,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.7.
Why doesn't Bugzilla offer this or that feature or compatibility
@@ -10276,9 +10143,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.8.
Why MySQL? I'm interested in seeing Bugzilla run on
@@ -10321,9 +10186,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.9.
What is
A.1.10.
My perl is not located at
A.1.11.
Is there an easy way to change the Bugzilla cookie name?
@@ -10435,9 +10294,7 @@ CLASS="answer"
CLASS="qandadiv"
>
2. Managerial Questions
2. Managerial Questions
A.2.1.
Is Bugzilla web-based, or do you have to have specific software or
@@ -10500,9 +10355,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.2.
Can Bugzilla integrate with
@@ -10526,9 +10379,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.3.
Does Bugzilla allow the user to track multiple projects?
@@ -10551,9 +10402,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.4.
If I am on many projects, and search for all bugs assigned to me, will
@@ -10576,9 +10425,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.5.
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
@@ -10605,9 +10452,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.6.
Does Bugzilla allow us to define our own priorities and levels? Do we
@@ -10642,9 +10487,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.7.
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
@@ -10680,9 +10523,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.8.
Is there email notification and if so, what do you see when you get an
@@ -10707,9 +10548,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.9.
Can email notification be set up to send to multiple
@@ -10732,9 +10571,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.10.
Do users have to have any particular
@@ -10791,9 +10628,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.11.
Does Bugzilla allow data to be imported and exported? If I had outsiders
@@ -10853,9 +10688,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.12.
Has anyone converted Bugzilla to another language to be used in other
@@ -10891,9 +10724,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.13.
Can a user create and save reports? Can they do this in Word format?
@@ -10916,9 +10747,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.14.
Does Bugzilla have the ability to search by word, phrase, compound
@@ -10942,9 +10771,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.15.
Does Bugzilla provide record locking when there is simultaneous access
@@ -10969,9 +10796,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.16.
Are there any backup features provided?
@@ -10999,9 +10824,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.17.
Can users be on the system while a backup is in progress?
@@ -11025,9 +10848,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.18.
What type of human resources are needed to be on staff to install and
@@ -11060,9 +10881,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.19.
What time frame are we looking at if we decide to hire people to install
@@ -11093,9 +10912,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.20.
Is there any licensing fee or other fees for using Bugzilla? Any
@@ -11118,18 +10935,14 @@ CLASS="answer"
CLASS="qandadiv"
>
3. Bugzilla Security
3. Bugzilla Security
A.3.1.
How do I completely disable MySQL security if it's giving me problems
@@ -11156,9 +10969,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.3.2.
Are there any security problems with Bugzilla?
@@ -11184,9 +10995,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.3.3.
I've implemented the security fixes mentioned in Chris Yeh's security
@@ -11211,18 +11020,14 @@ CLASS="answer"
CLASS="qandadiv"
>
4. Bugzilla Email
4. Bugzilla Email
A.4.1.
I have a user who doesn't want to receive any more email from Bugzilla.
@@ -11250,9 +11055,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.2.
I'm evaluating/testing Bugzilla, and don't want it to send email to
@@ -11276,9 +11079,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.3.
I want whineatnews.pl to whine at something more, or other than, only new
@@ -11309,9 +11110,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.4.
I don't like/want to use Procmail to hand mail off to bug_email.pl.
@@ -11327,9 +11126,7 @@ CLASS="answer"
You can call bug_email.pl directly from your aliases file, with
an entry like this:
+ 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
8. Bugzilla Hacking
A.8.1.
What kind of style should I use for templatization?
@@ -12098,9 +11884,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.2.
What bugs are in Bugzilla right now?
@@ -12144,9 +11928,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.3.
How can I change the default priority to a null value? For instance, have the default
@@ -12175,9 +11957,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.4.
What's the best way to submit patches? What guidelines should I follow?
@@ -12252,9 +12032,7 @@ TARGET="_top"
CLASS="appendix"
>
Appendix B. The Bugzilla Database
Appendix B. The Bugzilla Database
B.1. Modifying Your Running System
B.1. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively
static information in the
@@ -12337,9 +12113,7 @@ CLASS="section"
>
B.2. MySQL Bugzilla Database Introduction
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
@@ -12399,9 +12173,7 @@ CLASS="section"
>
B.2.1. Bugzilla Database Basics
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
@@ -12513,9 +12285,7 @@ CLASS="section"
>
B.2.1.1. Bugzilla Database Tables
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:
Appendix C. Useful Patches and Utilities for Bugzilla
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.
There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
@@ -12914,9 +12678,7 @@ CLASS="command"
CLASS="appendix"
>
Appendix D. Bugzilla Variants and Competitors
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
@@ -12933,9 +12695,7 @@ CLASS="section"
>
D.1. Red Hat Bugzilla
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
@@ -12967,9 +12727,7 @@ CLASS="section"
>
D.2. Loki Bugzilla (Fenris)
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,
@@ -12983,9 +12741,7 @@ CLASS="section"
>
D.3. Issuezilla
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
@@ -13002,9 +12758,7 @@ CLASS="section"
>
D.4. Scarab
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.
D.5. Perforce SCM
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as
such through the
D.6. SourceForge
D.6. SourceForge
SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
@@ -13070,15 +12820,11 @@ TARGET="_top"
CLASS="appendix"
>
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
@@ -13121,9 +12865,7 @@ CLASS="section"
>
1. APPLICABILITY AND DEFINITIONS
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
@@ -13186,9 +12928,7 @@ CLASS="section"
>
2. VERBATIM COPYING
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
@@ -13208,9 +12948,7 @@ CLASS="section"
>
3. COPYING IN QUANTITY
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
@@ -13252,9 +12990,7 @@ CLASS="section"
>
4. MODIFICATIONS
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
@@ -13390,9 +13126,7 @@ CLASS="section"
>
5. COMBINING DOCUMENTS
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
@@ -13421,9 +13155,7 @@ CLASS="section"
>
6. COLLECTIONS OF DOCUMENTS
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
@@ -13442,9 +13174,7 @@ CLASS="section"
>
7. AGGREGATION WITH INDEPENDENT WORKS
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
@@ -13466,9 +13196,7 @@ CLASS="section"
>
8. TRANSLATION
8. TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
@@ -13486,9 +13214,7 @@ CLASS="section"
>
9. TERMINATION
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
@@ -13503,9 +13229,7 @@ CLASS="section"
>
10. FUTURE REVISIONS OF THIS LICENSE
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
@@ -13531,17 +13255,13 @@ CLASS="section"
>
How to use this License for your documents
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:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
@@ -13568,17 +13288,13 @@ CLASS="BLOCKQUOTE"
CLASS="GLOSSARY"
>
There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
diff --git a/docs/html/conventions.html b/docs/html/conventions.html
index 7b343bd2d..5cdb696e0 100644
--- a/docs/html/conventions.html
+++ b/docs/html/conventions.html
@@ -4,7 +4,8 @@
>Document Conventions
1.5. Document Conventions
1.5. Document Conventions
This document uses the following conventions:
Copyright Information
1.1. Copyright Information
1.1. Copyright Information
Credits
1.4. Credits
1.4. Credits
The people listed below have made enormous contributions to the
creation of this Guide, through their writing, dedicated hacking efforts,
diff --git a/docs/html/cust-change-permissions.html b/docs/html/cust-change-permissions.html
index cb123985d..302695d0b 100644
--- a/docs/html/cust-change-permissions.html
+++ b/docs/html/cust-change-permissions.html
@@ -4,7 +4,8 @@
>Change Permission Customization
5.8. Change Permission Customization
5.8. Change Permission Customization
Template Customization
5.7. Template Customization
5.7. Template Customization
One of the large changes for 2.16 was the templatization of the
entire user-facing UI, using the
@@ -102,9 +101,7 @@ CLASS="section"
>
5.7.1. What to Edit
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
@@ -252,9 +249,7 @@ CLASS="section"
>
5.7.2. How To Edit Templates
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
@@ -334,9 +329,7 @@ CLASS="section"
>
5.7.3. Template Formats
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
@@ -396,9 +389,7 @@ CLASS="section"
>
5.7.4. Particular Templates
5.7.4. Particular Templates
There are a few templates you may be particularly interested in
customizing for your installation.
@@ -585,9 +576,7 @@ CLASS="section"
>
5.7.5. Configuring Bugzilla to Detect the User's Language
5.7.5. Configuring Bugzilla to Detect the User's Language
Begining in version 2.18 (first introduced in version
2.17.4), it's now possible to have the users web browser tell Bugzilla
diff --git a/docs/html/database.html b/docs/html/database.html
index d9bc26c2c..3473e6589 100644
--- a/docs/html/database.html
+++ b/docs/html/database.html
@@ -4,7 +4,8 @@
>The Bugzilla Database
Appendix B. The Bugzilla Database
Appendix B. The Bugzilla Database
MySQL Bugzilla Database Introduction
B.2. MySQL Bugzilla Database Introduction
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
@@ -134,9 +133,7 @@ CLASS="section"
>
B.2.1. Bugzilla Database Basics
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
@@ -248,9 +245,7 @@ CLASS="section"
>
B.2.1.1. Bugzilla Database Tables
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:
Modifying Your Running System
B.1. Modifying Your Running System
B.1. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively
static information in the
diff --git a/docs/html/disclaimer.html b/docs/html/disclaimer.html
index 23e255785..be0eb763e 100644
--- a/docs/html/disclaimer.html
+++ b/docs/html/disclaimer.html
@@ -4,7 +4,8 @@
>Disclaimer
1.2. Disclaimer
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.
diff --git a/docs/html/extraconfig.html b/docs/html/extraconfig.html
index 038b8d282..00886ec59 100644
--- a/docs/html/extraconfig.html
+++ b/docs/html/extraconfig.html
@@ -4,7 +4,8 @@
>Optional Additional Configuration
4.2. Optional Additional Configuration
4.2. Optional Additional Configuration
4.2.1. Dependency Charts
4.2.1. Dependency Charts
As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
@@ -144,9 +141,7 @@ CLASS="section"
>
4.2.2. Bug Graphs
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.
4.2.3. The Whining Cron
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
@@ -292,9 +285,7 @@ CLASS="section"
>
4.2.4. LDAP Authentication
4.2.4. LDAP Authentication
loginmethod
loginmethod
This parameter should be set to
LDAPserver
LDAPserver
This parameter should be set to the name (and optionally the
@@ -466,9 +453,7 @@ CLASS="QUOTE"
>
LDAPbinddn [Optional]
LDAPbinddn [Optional]
Some LDAP servers will not allow an anonymous bind to search
@@ -484,9 +469,7 @@ CLASS="QUOTE"
>
LDAPBaseDN
LDAPBaseDN
The LDAPBaseDN parameter should be set to the location in
@@ -501,9 +484,7 @@ CLASS="QUOTE"
>
LDAPuidattribute
LDAPuidattribute
The LDAPuidattribute parameter should be set to the attribute
@@ -519,9 +500,7 @@ CLASS="QUOTE"
>
LDAPmailattribute
LDAPmailattribute
The LDAPmailattribute parameter should be the name of the
@@ -542,9 +521,7 @@ CLASS="section"
>
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
It is possible for a Bugzilla to execute malicious Javascript
@@ -648,9 +625,7 @@ CLASS="section"
>
4.2.6. 4.2.6. directoryindex for the Bugzilla default page.
A.1.6.
How does Bugzilla stack up against other bug-tracking databases?
@@ -787,9 +778,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.7.
Why doesn't Bugzilla offer this or that feature or compatibility
@@ -827,9 +816,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.8.
Why MySQL? I'm interested in seeing Bugzilla run on
@@ -872,9 +859,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.1.9.
What is
A.1.10.
My perl is not located at
A.1.11.
Is there an easy way to change the Bugzilla cookie name?
@@ -986,9 +967,7 @@ CLASS="answer"
CLASS="qandadiv"
>
2. Managerial Questions
2. Managerial Questions
A.2.1.
Is Bugzilla web-based, or do you have to have specific software or
@@ -1051,9 +1028,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.2.
Can Bugzilla integrate with
@@ -1077,9 +1052,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.3.
Does Bugzilla allow the user to track multiple projects?
@@ -1102,9 +1075,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.4.
If I am on many projects, and search for all bugs assigned to me, will
@@ -1127,9 +1098,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.5.
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
@@ -1156,9 +1125,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.6.
Does Bugzilla allow us to define our own priorities and levels? Do we
@@ -1193,9 +1160,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.7.
Does Bugzilla provide any reporting features, metrics, graphs, etc? You
@@ -1231,9 +1196,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.8.
Is there email notification and if so, what do you see when you get an
@@ -1258,9 +1221,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.9.
Can email notification be set up to send to multiple
@@ -1283,9 +1244,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.10.
Do users have to have any particular
@@ -1342,9 +1301,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.11.
Does Bugzilla allow data to be imported and exported? If I had outsiders
@@ -1404,9 +1361,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.12.
Has anyone converted Bugzilla to another language to be used in other
@@ -1442,9 +1397,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.13.
Can a user create and save reports? Can they do this in Word format?
@@ -1467,9 +1420,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.14.
Does Bugzilla have the ability to search by word, phrase, compound
@@ -1493,9 +1444,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.15.
Does Bugzilla provide record locking when there is simultaneous access
@@ -1520,9 +1469,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.16.
Are there any backup features provided?
@@ -1550,9 +1497,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.17.
Can users be on the system while a backup is in progress?
@@ -1576,9 +1521,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.18.
What type of human resources are needed to be on staff to install and
@@ -1611,9 +1554,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.19.
What time frame are we looking at if we decide to hire people to install
@@ -1644,9 +1585,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.2.20.
Is there any licensing fee or other fees for using Bugzilla? Any
@@ -1669,18 +1608,14 @@ CLASS="answer"
CLASS="qandadiv"
>
3. Bugzilla Security
3. Bugzilla Security
A.3.1.
How do I completely disable MySQL security if it's giving me problems
@@ -1707,9 +1642,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.3.2.
Are there any security problems with Bugzilla?
@@ -1735,9 +1668,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.3.3.
I've implemented the security fixes mentioned in Chris Yeh's security
@@ -1762,18 +1693,14 @@ CLASS="answer"
CLASS="qandadiv"
>
4. Bugzilla Email
4. Bugzilla Email
A.4.1.
I have a user who doesn't want to receive any more email from Bugzilla.
@@ -1801,9 +1728,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.2.
I'm evaluating/testing Bugzilla, and don't want it to send email to
@@ -1827,9 +1752,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.3.
I want whineatnews.pl to whine at something more, or other than, only new
@@ -1860,9 +1783,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.4.4.
I don't like/want to use Procmail to hand mail off to bug_email.pl.
@@ -1878,9 +1799,7 @@ CLASS="answer"
You can call bug_email.pl directly from your aliases file, with
an entry like this:
+ 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
8. Bugzilla Hacking
A.8.1.
What kind of style should I use for templatization?
@@ -2649,9 +2557,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.2.
What bugs are in Bugzilla right now?
@@ -2695,9 +2601,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.3.
How can I change the default priority to a null value? For instance, have the default
@@ -2726,9 +2630,7 @@ CLASS="qandaentry"
CLASS="question"
>
A.8.4.
What's the best way to submit patches? What guidelines should I follow?
diff --git a/docs/html/gfdl-0.html b/docs/html/gfdl-0.html
index 7b7408310..89e5dcdfb 100644
--- a/docs/html/gfdl-0.html
+++ b/docs/html/gfdl-0.html
@@ -4,7 +4,8 @@
>PREAMBLE
0. PREAMBLE
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
diff --git a/docs/html/gfdl-1.html b/docs/html/gfdl-1.html
index 45a1d994a..e02d68114 100644
--- a/docs/html/gfdl-1.html
+++ b/docs/html/gfdl-1.html
@@ -4,7 +4,8 @@
>APPLICABILITY AND DEFINITIONS
1. APPLICABILITY AND DEFINITIONS
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
diff --git a/docs/html/gfdl-10.html b/docs/html/gfdl-10.html
index 080f8b7f8..7ae9965c7 100644
--- a/docs/html/gfdl-10.html
+++ b/docs/html/gfdl-10.html
@@ -4,7 +4,8 @@
>FUTURE REVISIONS OF THIS LICENSE
10. FUTURE REVISIONS OF THIS LICENSE
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
diff --git a/docs/html/gfdl-2.html b/docs/html/gfdl-2.html
index bd6c41c3f..62ccdb554 100644
--- a/docs/html/gfdl-2.html
+++ b/docs/html/gfdl-2.html
@@ -4,7 +4,8 @@
>VERBATIM COPYING
2. VERBATIM COPYING
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
diff --git a/docs/html/gfdl-3.html b/docs/html/gfdl-3.html
index 0db6ed8af..bd5e7cf31 100644
--- a/docs/html/gfdl-3.html
+++ b/docs/html/gfdl-3.html
@@ -4,7 +4,8 @@
>COPYING IN QUANTITY
3. COPYING IN QUANTITY
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
diff --git a/docs/html/gfdl-4.html b/docs/html/gfdl-4.html
index c5d7d5957..75c1f0008 100644
--- a/docs/html/gfdl-4.html
+++ b/docs/html/gfdl-4.html
@@ -4,7 +4,8 @@
>MODIFICATIONS
4. MODIFICATIONS
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
diff --git a/docs/html/gfdl-5.html b/docs/html/gfdl-5.html
index eed6fc5c4..f990ada41 100644
--- a/docs/html/gfdl-5.html
+++ b/docs/html/gfdl-5.html
@@ -4,7 +4,8 @@
>COMBINING DOCUMENTS
5. COMBINING DOCUMENTS
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
diff --git a/docs/html/gfdl-6.html b/docs/html/gfdl-6.html
index 724af41ba..45606b76b 100644
--- a/docs/html/gfdl-6.html
+++ b/docs/html/gfdl-6.html
@@ -4,7 +4,8 @@
>COLLECTIONS OF DOCUMENTS
6. COLLECTIONS OF DOCUMENTS
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
diff --git a/docs/html/gfdl-7.html b/docs/html/gfdl-7.html
index d22a95f7f..db7678717 100644
--- a/docs/html/gfdl-7.html
+++ b/docs/html/gfdl-7.html
@@ -4,7 +4,8 @@
>AGGREGATION WITH INDEPENDENT WORKS
7. AGGREGATION WITH INDEPENDENT WORKS
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
diff --git a/docs/html/gfdl-8.html b/docs/html/gfdl-8.html
index 8b89b2fed..9b9207c0f 100644
--- a/docs/html/gfdl-8.html
+++ b/docs/html/gfdl-8.html
@@ -4,7 +4,8 @@
>TRANSLATION
8. TRANSLATION
8. TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
diff --git a/docs/html/gfdl-9.html b/docs/html/gfdl-9.html
index b23394dc6..5d919bdbd 100644
--- a/docs/html/gfdl-9.html
+++ b/docs/html/gfdl-9.html
@@ -4,7 +4,8 @@
>TERMINATION
9. TERMINATION
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt to
diff --git a/docs/html/gfdl-howto.html b/docs/html/gfdl-howto.html
index 41bb83dda..91ffb1c02 100644
--- a/docs/html/gfdl-howto.html
+++ b/docs/html/gfdl-howto.html
@@ -4,7 +4,8 @@
>How to use this License for your documents
How to use this License for your documents
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:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy,
diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html
index ccff204c4..d95515e04 100644
--- a/docs/html/gfdl.html
+++ b/docs/html/gfdl.html
@@ -4,7 +4,8 @@
>GNU Free Documentation License
Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
diff --git a/docs/html/hintsandtips.html b/docs/html/hintsandtips.html
index c1e66a948..ad8440032 100644
--- a/docs/html/hintsandtips.html
+++ b/docs/html/hintsandtips.html
@@ -4,7 +4,8 @@
>Hints and Tips
3.2. Hints and Tips
3.2. Hints and Tips
This section distills some Bugzilla tips and best practices
that have been developed.
3.2.1. Autolinkification
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.
@@ -148,9 +145,7 @@ CLASS="section"
>
3.2.2. Quicksearch
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
@@ -181,9 +176,7 @@ CLASS="section"
>
3.2.3. Comments
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.
@@ -205,9 +198,7 @@ CLASS="section"
>
3.2.4. Attachments
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
@@ -231,9 +222,7 @@ CLASS="section"
>
3.2.5. Filing Bugs
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
diff --git a/docs/html/how.html b/docs/html/how.html
index 00825059c..fad287977 100644
--- a/docs/html/how.html
+++ b/docs/html/how.html
@@ -4,7 +4,8 @@
>How do I use Bugzilla?
3.1. How do I use Bugzilla?
3.1. How do I use Bugzilla?
This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
@@ -93,9 +92,7 @@ CLASS="section"
>
3.1.1. Create a Bugzilla Account
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
@@ -163,9 +160,7 @@ CLASS="section"
>
3.1.2. Anatomy of a Bug
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.
@@ -430,9 +425,7 @@ CLASS="section"
>
3.1.3. Searching for Bugs
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
@@ -460,9 +453,7 @@ CLASS="section"
>
3.1.4. Bug Lists
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
@@ -534,9 +525,7 @@ CLASS="section"
>
3.1.5. Filing Bugs
3.1.5. Filing Bugs
Years of bug writing experience has been distilled for your
reading pleasure into the
@@ -589,6 +578,156 @@ TARGET="_top"
>
Viewing and reviewing patches in Bugzilla is often difficult due to
+ lack of context, improper format and the inherent readability issues that
+ raw patches present. Patch Viewer is an enhancement to Bugzilla designed
+ to fix that by offering increased context, linking to sections, and
+ integrating with Bonsai, LXR and CVS.
Patch viewer allows you to:
View patches in color, with side-by-side view rather than trying
+ to interpret the contents of the patch.
See the difference between two patches.
Get more context in a patch.
Collapse and expand sections of a patch for easy
+ reading.
Link to a particular section of a patch for discussion or
+ review
Go to Bonsai or LXR to see more context, blame, and
+ cross-references for the part of the patch you are looking at
Create a rawtext unified format diff out of any patch, no
+ matter what format it came from
The main way to view a patch in patch viewer is to click on the
+ "Diff" link next to a patch in the Attachments list on a bug. You may
+ also do this within the edit window by clicking the "View Attachment As
+ Diff" button in the Edit Attachment screen.
To see the difference between two patches, you must first view the
+ newer patch in Patch Viewer. Then select the older patch from the
+ dropdown at the top of the page ("Differences between [dropdown] and
+ this patch") and click the "Diff" button. This will show you what
+ is new or changed in the newer patch.
To get more context in a patch, you put a number in the textbox at
+ the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
+ This will give you that many lines of context before and after each
+ change. Alternatively, you can click on the "File" link there and it
+ will show each change in the full context of the file. This feature only
+ works against files that were diffed using "cvs diff".
To view only a certain set of files in a patch (for example, if a
+ patch is absolutely huge and you want to only review part of it at a
+ time), you can click the "(+)" and "(-)" links next to each file (to
+ expand it or collapse it). If you want to collapse all files or expand
+ all files, you can click the "Collapse All" and "Expand All" links at the
+ top of the page.
To link to a section of a patch (for example, if you want to be
+ able to give someone a URL to show them which part you are talking
+ about) you simply click the "Link Here" link on the section header. The
+ resulting URL can be copied and used in discussion. (Copy Link
+ Location in Mozilla works as well.)
To go to Bonsai to get blame for the lines you are interested in,
+ you can click the "Lines XX-YY" link on the section header you are
+ interested in. This works even if the patch is against an old
+ version of the file, since Bonsai stores all versions of the file.
To go to LXR, you click on the filename on the file header
+ (unfortunately, since LXR only does the most recent version, line
+ numbers are likely to rot).
If the patch is not in a format that you like, you can turn it
+ into a unified diff format by clicking the "Raw Unified" link at the top
+ of the page.
HTTP Server Configuration
4.4. HTTP Server Configuration
4.4. HTTP Server Configuration
The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
that can be configured to run
4.4.1. Apache 4.4.1. Apache httpd
Example 4-2.
4.4.2. Microsoft 4.4.2. Microsoft Internet Information Services
4.4.3. AOL Server
4.4.3. AOL Server
Ben FrantzDale reported success using AOL Server with Bugzilla. He
reported his experience and what appears below is based on that.
diff --git a/docs/html/index.html b/docs/html/index.html
index a606eecb0..e02d6215f 100644
--- a/docs/html/index.html
+++ b/docs/html/index.html
@@ -4,7 +4,8 @@
>The Bugzilla Guide - 2.17.5 Development Release
The Bugzilla Guide - 2.17.5 Development Release
The Bugzilla Guide - 2.17.5 Development Release
Matthew P. Barnson
Matthew P. Barnson
Jacob Steenhagen
Jacob Steenhagen
The Bugzilla Team
This is the documentation for Bugzilla, the mozilla.org
diff --git a/docs/html/installation.html b/docs/html/installation.html
index fb02eeed1..96dd78cf3 100644
--- a/docs/html/installation.html
+++ b/docs/html/installation.html
@@ -4,7 +4,8 @@
>Installation
CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.
5.10.3. Perforce SCM
5.10.3. Perforce SCM
You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
@@ -182,9 +175,7 @@ CLASS="section"
>
5.10.4. Tinderbox/Tinderbox2
5.10.4. Tinderbox/Tinderbox2
We need Tinderbox integration information.
Introduction
Chapter 2. Introduction
Chapter 2. Introduction
New Versions
1.3. New Versions
1.3. New Versions
This is the 2.17.5 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
diff --git a/docs/html/os-specific.html b/docs/html/os-specific.html
index f3d786844..4fb1203fd 100644
--- a/docs/html/os-specific.html
+++ b/docs/html/os-specific.html
@@ -4,7 +4,8 @@
>OS Specific Installation Notes
4.3. OS Specific Installation Notes
4.3. OS Specific Installation Notes
Many aspects of the Bugzilla installation can be affected by the
the operating system you choose to install it on. Sometimes it can be made
@@ -95,9 +94,7 @@ CLASS="section"
>
4.3.1. Microsoft Windows
4.3.1. Microsoft Windows
Making Bugzilla work on windows is still a very painful processes.
The Bugzilla Team is working to make it easier, but that goal is not
@@ -121,9 +118,7 @@ CLASS="section"
>
4.3.1.1. Win32 Perl
4.3.1.1. Win32 Perl
Perl for Windows can be obtained from
4.3.1.2. Perl Modules on Win32
4.3.1.2. Perl Modules on Win32
Bugzilla on Windows requires the same perl modules found in
4.3.1.3. Code changes required to run on win32
4.3.1.3. Code changes required to run on win32
Unfortunately, Bugzilla still doesn't run "out of the box" on
Windows. There is work in progress to make this easier, but until that
@@ -274,9 +265,7 @@ CLASS="section"
>
4.3.1.3.1. Changes to 4.3.1.3.1. Changes to checksetup.pl
4.3.1.3.2. Changes to 4.3.1.3.2. Changes to BugMail.pm
4.3.1.4. Serving the web pages
4.3.1.4. Serving the web pages
As is the case on Unix based systems, any web server should be
able to handle Bugzilla; however, the Bugzilla Team still recommends
@@ -503,9 +488,7 @@ CLASS="section"
>
4.3.2. 4.3.2. Mac OS X
4.3.3. Linux-Mandrake 8.0
4.3.3. Linux-Mandrake 8.0
Linux-Mandrake 8.0 includes every required and optional library
for Bugzilla. The easiest way to install them is by using the
diff --git a/docs/html/parameters.html b/docs/html/parameters.html
index 3cb7af23f..3a43de73c 100644
--- a/docs/html/parameters.html
+++ b/docs/html/parameters.html
@@ -4,7 +4,8 @@
>Bugzilla Configuration
5.1. Bugzilla Configuration
5.1. Bugzilla Configuration
Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
diff --git a/docs/html/patches.html b/docs/html/patches.html
index c2791a34c..64610173b 100644
--- a/docs/html/patches.html
+++ b/docs/html/patches.html
@@ -4,7 +4,8 @@
>Useful Patches and Utilities for Bugzilla
Appendix C. Useful Patches and Utilities for Bugzilla
Appendix C. Useful Patches and Utilities for Bugzilla
Product, Component, Milestone, and Version Administration
5.3. Product, Component, Milestone, and Version Administration
5.3. Product, Component, Milestone, and Version Administration
5.3.1. Products
5.3.1. Products
5.3.2. Components
5.3.2. Components
Components are subsections of a Product. E.g. the computer game
you are designing may have a "UI"
@@ -191,9 +186,7 @@ CLASS="section"
>
5.3.3. Versions
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
@@ -227,9 +220,7 @@ CLASS="section"
>
5.3.4. Milestones
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
diff --git a/docs/html/rewrite.html b/docs/html/rewrite.html
index e986b814e..9fea98fa2 100644
--- a/docs/html/rewrite.html
+++ b/docs/html/rewrite.html
@@ -7,7 +7,8 @@
magic
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
@@ -191,9 +188,7 @@ CLASS="section"
>
5.6.2. MySQL
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
@@ -320,9 +315,7 @@ CLASS="section"
>
5.6.3. Daemon Accounts
5.6.3. Daemon Accounts
Many daemons, such as Apache's httpd and MySQL's mysqld default to
running as either
5.6.4. Web Server Access Controls
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
diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html
index 5734c5259..778ba0f10 100644
--- a/docs/html/stepbystep.html
+++ b/docs/html/stepbystep.html
@@ -4,7 +4,8 @@
>Step-by-step Install
4.1. Step-by-step Install
4.1. Step-by-step Install
Bugzilla has been successfully installed under many different
operating systems including almost all Unix clones and
@@ -228,9 +227,7 @@ CLASS="section"
>
4.1.1. MySQL
4.1.1. MySQL
Visit the MySQL homepage at
Figure 4-1. Set Max Packet Size in MySQL
4.1.2. Perl
4.1.2. Perl
Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from
4.1.3. Perl Modules
4.1.3. Perl Modules
Perl modules can be found using
Example 4-1. Installing perl modules with CPAN
4.1.3.1. Bundle::Bugzilla
4.1.3.1. Bundle::Bugzilla
If you are running at least perl 5.6.1, you can save yourself a lot
of time by using Bundle::Bugzilla. This bundle contains every module
@@ -850,9 +837,7 @@ CLASS="section"
>
4.1.3.2. AppConfig (1.52)
4.1.3.2. AppConfig (1.52)
Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
@@ -863,9 +848,7 @@ CLASS="section"
>
4.1.3.3. CGI (2.88)
4.1.3.3. CGI (2.88)
The CGI module parses form elements and cookies and does many
other usefule things. It come as a part of recent perl distributions, but
@@ -896,9 +879,7 @@ CLASS="section"
>
4.1.3.4. Data::Dumper (any)
4.1.3.4. Data::Dumper (any)
The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
@@ -930,9 +911,7 @@ CLASS="section"
>
4.1.3.5. TimeDate modules (2.21)
4.1.3.5. TimeDate modules (2.21)
Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
@@ -965,9 +944,7 @@ CLASS="section"
>
4.1.3.6. DBI (1.32)
4.1.3.6. DBI (1.32)
The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
@@ -999,9 +976,7 @@ CLASS="section"
>
4.1.3.7. MySQL-related modules
4.1.3.7. MySQL-related modules
The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
@@ -1044,9 +1019,7 @@ CLASS="section"
>
4.1.3.8. File::Spec (0.82)
4.1.3.8. File::Spec (0.82)
File::Spec is a perl module that allows file operations, such as
generating full path names, to work cross platform.
@@ -1076,9 +1049,7 @@ CLASS="section"
>
4.1.3.9. File::Temp (any)
4.1.3.9. File::Temp (any)
File::Temp is used to generate a temporary filename that is
guaranteed to be unique. It comes as a standard part of perl
@@ -1108,9 +1079,7 @@ CLASS="section"
>
4.1.3.10. Template Toolkit (2.08)
4.1.3.10. Template Toolkit (2.08)
When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
@@ -1142,9 +1111,7 @@ CLASS="section"
>
4.1.3.11. Text::Wrap (2001.0131)
4.1.3.11. Text::Wrap (2001.0131)
Text::Wrap is designed to proved intelligent text wrapping.
4.1.3.12. GD (1.20) [optional]
4.1.3.12. GD (1.20) [optional]
The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
@@ -1278,9 +1243,7 @@ CLASS="section"
>
4.1.3.13. Chart::Base (0.99c) [optional]
4.1.3.13. Chart::Base (0.99c) [optional]
The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
@@ -1307,9 +1270,7 @@ CLASS="section"
>
4.1.3.14. XML::Parser (any) [Optional]
4.1.3.14. XML::Parser (any) [Optional]
XML::Parser is used by the
4.1.3.15. GD::Graph (any) [Optional]
4.1.3.15. GD::Graph (any) [Optional]
In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
@@ -1374,9 +1333,7 @@ CLASS="section"
>
4.1.3.16. GD::Text::Align (any) [Optional]
4.1.3.16. GD::Text::Align (any) [Optional]
GD::Text::Align, as the name implies, is used to draw aligned
strings of text. It is needed by the reporting interface.
@@ -1406,9 +1363,7 @@ CLASS="section"
>
4.1.3.17. MIME::Parser (any) [Optional]
4.1.3.17. MIME::Parser (any) [Optional]
MIME::Parser is only needed if you want to use the e-mail interface
located in the
4.1.3.18. PatchReader (0.9.1) [Optional]
4.1.3.18. PatchReader (0.9.1) [Optional]
PatchReader is only needed if you want to use Patch Viewer, a
Bugzilla feature to format patches in a pretty HTML fashion. There are a
@@ -1479,9 +1432,7 @@ CLASS="section"
>
4.1.4. HTTP Server
4.1.4. HTTP Server
You have freedom of choice here, pretty much any web server that
is capable of running
4.1.5. Bugzilla
4.1.5. Bugzilla
You should untar the Bugzilla files into a directory that you're
willing to make writable by the default web server user (probably
@@ -1651,9 +1600,7 @@ CLASS="section"
>
4.1.6. Setting Up the MySQL Database
4.1.6. 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
@@ -1808,9 +1755,7 @@ CLASS="section"
>
4.1.7. 4.1.7. checksetup.pl
4.1.8. Configuring Bugzilla
4.1.8. Configuring Bugzilla
You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
diff --git a/docs/html/troubleshooting.html b/docs/html/troubleshooting.html
index 7ac5856fd..e3de155e5 100644
--- a/docs/html/troubleshooting.html
+++ b/docs/html/troubleshooting.html
@@ -4,7 +4,8 @@
>Troubleshooting
4.5. Troubleshooting
4.5. Troubleshooting
This section gives solutions to common Bugzilla installation
problems.
@@ -84,9 +83,7 @@ CLASS="section"
>
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1
Try executing
4.5.2. DBD::Sponge::db prepare failed
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):
@@ -195,9 +190,7 @@ CLASS="section"
>
4.5.3. cannot chdir(/var/spool/mqueue)
4.5.3. cannot chdir(/var/spool/mqueue)
If you are installing Bugzilla on SuSE Linux, or some other
distributions with
@@ -253,9 +246,7 @@ CLASS="section"
>
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT
This is caused by a bug in the version of
Figure 4-2. Other File::Temp error messages
Figure 4-3. Patch for File::Temp in Perl 5.6.0
Upgrading to New Releases
5.9. Upgrading to New Releases
5.9. Upgrading to New Releases
Example 5-1. Upgrading using CVS
Example 5-2. Upgrading using the tarball
Example 5-3. Upgrading using patches
User Administration
5.2. User Administration
5.2. User Administration
5.2.1. Creating the Default User
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
@@ -125,17 +122,13 @@ CLASS="section"
>
5.2.2. Managing Other Users
5.2.2. Managing Other Users
5.2.2.1. Creating new users
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
@@ -206,9 +199,7 @@ CLASS="section"
>
5.2.2.2. Modifying Users
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,
diff --git a/docs/html/userpreferences.html b/docs/html/userpreferences.html
index d6bbde5d0..d242af104 100644
--- a/docs/html/userpreferences.html
+++ b/docs/html/userpreferences.html
@@ -4,7 +4,8 @@
>User Preferences
3.3. User Preferences
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.
@@ -84,9 +83,7 @@ CLASS="section"
>
3.3.1. Account Settings
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
@@ -109,9 +106,7 @@ CLASS="section"
>
3.3.2. Email Settings
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
@@ -158,9 +153,7 @@ CLASS="section"
>
3.3.3. Page Footer
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.
@@ -172,9 +165,7 @@ CLASS="section"
>
3.3.4. Permissions
3.3.4. Permissions
This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
diff --git a/docs/html/using.html b/docs/html/using.html
index 8041e3a34..af8d24425 100644
--- a/docs/html/using.html
+++ b/docs/html/using.html
@@ -4,7 +4,8 @@
>Using Bugzilla
Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
diff --git a/docs/html/variant-issuezilla.html b/docs/html/variant-issuezilla.html
index 599b04a7e..b3e4df1e9 100644
--- a/docs/html/variant-issuezilla.html
+++ b/docs/html/variant-issuezilla.html
@@ -4,7 +4,8 @@
>Issuezilla
D.3. Issuezilla
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
diff --git a/docs/html/variant-perforce.html b/docs/html/variant-perforce.html
index 7f90944f7..cc8293ec2 100644
--- a/docs/html/variant-perforce.html
+++ b/docs/html/variant-perforce.html
@@ -4,7 +4,8 @@
>Perforce SCM
D.5. Perforce SCM
D.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used as
such through the Red Hat Bugzilla
D.1. Red Hat Bugzilla
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
diff --git a/docs/html/variant-scarab.html b/docs/html/variant-scarab.html
index d7684ed26..071eaafb4 100644
--- a/docs/html/variant-scarab.html
+++ b/docs/html/variant-scarab.html
@@ -4,7 +4,8 @@
>Scarab
D.4. Scarab
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.
SourceForge
D.6. SourceForge
D.6. SourceForge
SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
diff --git a/docs/html/variants.html b/docs/html/variants.html
index 731738863..da31e3a56 100644
--- a/docs/html/variants.html
+++ b/docs/html/variants.html
@@ -4,7 +4,8 @@
>Bugzilla Variants and Competitors
Appendix D. Bugzilla Variants and Competitors
Appendix D. Bugzilla Variants and Competitors
Voting
5.4. Voting
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.
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index e92d899a3..9621bf09a 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -4,7 +4,8 @@
>What is Bugzilla?
2.1. What is Bugzilla?
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
diff --git a/docs/html/why.html b/docs/html/why.html
index d1e3b813e..06100733c 100644
--- a/docs/html/why.html
+++ b/docs/html/why.html
@@ -4,7 +4,8 @@
>Why Should We Use Bugzilla?