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 issue-tracking for hundreds of organizations around the world, tracking millions of bugs.
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.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in Appendix E. | ||
--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 Bugzilla Team.
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.
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 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 Bugzilla Guide is currently only available in English. If you would like to volunteer to translate it, please contact Dave Miller.
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:
for the Herculaean task of pulling together the Bugzilla Guide and shepherding it to 2.14.
for initially writing Bugzilla and creating the README upon which the UNIX installation documentation is largely based.
for keeping Bugzilla development going strong after Terry left mozilla.org and for running landfill.
for providing insight into the key differences between Red Hat's customized Bugzilla, and being largely responsible for Section D.1.
for being a hacker extraordinaire and putting up with Matthew's incessant questions and arguments on irc.mozilla.org in #mozwebtools
for taking over documentation during the 2.17 development period and backporting relevent docs changes to this 2.16 branch.
Last but not least, all the members of the news://news.mozilla.org/netscape/public/mozilla/webtools newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
Thanks also go to the following people for significant contributions to this documentation (in alphabetical order): Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption .
This document uses the following conventions:
Descriptions | Appearance | ||
---|---|---|---|
Use caution |
| ||
Hint |
| ||
Notes |
| ||
Warnings |
| ||
File Names | filename | ||
Directory Names | directory | ||
Commands to be typed | command | ||
Applications Names | application | ||
Prompt of users command under bash shell | bash$ | ||
Prompt of root users command under bash shell | bash# | ||
Prompt of user command under tcsh shell | tcsh$ | ||
Environment Variables | VARIABLE | ||
Emphasized word | word | ||
Term found in the glossary | Bugzilla | ||
Code Example |
|
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
Full change history
Inter-bug dependency tracking and graphing
Excellent attachment management
Integrated, product-based, granular security schema
Fully security-audited, and runs under Perl's taint mode
A robust, stable RDBMS back-end
Web, XML, email and console interfaces
Completely customisable and/or localisable web user interface
Extensive configurability
Smooth upgrade pathway between versions
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.
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.
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/
Click the "Open a new Bugzilla account" link, enter your email address and, optionally, your name in the spaces provided, then click "Create Account" .
Within moments, you should receive an email to the address you provided above, which contains your login name (generally the same as the email address), and a password you can use to access your account. This password is randomly generated, and can be changed to something more memorable.
Click the "Log In" link in the yellow area at the bottom of the page in your browser, enter your email address and password into the spaces provided, and click "Login".
You are now logged in. Bugzilla uses cookies for authentication so, unless your IP address changes, you should not have to log in again.
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.
Product and Component: Bugs are divided up by Product and Component, with a Product having one or more Components in it. For example, bugzilla.mozilla.org's "Bugzilla" Product is composed of several Components:
Administration: Administration of a Bugzilla installation. |
Bugzilla-General: Anything that doesn't fit in the other components, or spans multiple components. |
Creating/Changing Bugs: Creating, changing, and viewing bugs. |
Documentation: The Bugzilla documentation, including The Bugzilla Guide. |
Email: Anything to do with email sent by Bugzilla. |
Installation: The installation process of Bugzilla. |
Query/Buglist: Anything to do with searching for bugs and viewing the buglists. |
Reporting/Charting: Getting reports from Bugzilla. |
User Accounts: Anything about managing a user account from the user's perspective. Saved queries, creating accounts, changing passwords, logging in, etc. |
User Interface: General issues having to do with the user interface cosmetics (not functionality) including cosmetic issues, HTML templates, etc. |
Status and Resolution: These define exactly what state the bug is in - from not even being confirmed as a bug, through to being fixed and the fix confirmed by Quality Assurance. The different possible values for Status and Resolution on your installation should be documented in the context-sensitive help for those items.
Assigned To: The person responsible for fixing the bug.
*URL: A URL associated with the bug, if any.
Summary: A one-sentence summary of the problem.
*Status Whiteboard: (a.k.a. Whiteboard) A free-form text area for adding short notes and tags to a bug.
*Keywords: The administrator can define keywords which you can use to tag and categorise bugs - e.g. The Mozilla Project has keywords like crash and regression.
Platform and OS: These indicate the computing environment where the bug was found.
Version: The "Version" field is usually used for versions of a product which have been released, and is set to indicate which versions of a Component have the particular problem the bug report is about.
Priority: The bug assignee uses this field to prioritise his or her bugs. It's a good idea not to change this on other people's bugs.
Severity: This indicates how severe the problem is - from blocker ("application unusable") to trivial ("minor cosmetic issue"). You can also use this field to indicate whether a bug is an enhancement request.
*Target: (a.k.a. Target Milestone) A future version by which the bug is to be fixed. e.g. The Bugzilla Project's milestones for future Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not restricted to numbers, thought - you can use any text strings, such as dates.
Reporter: The person who filed the bug.
CC list: A list of people who get mail when the bug changes.
Attachments: You can attach files (e.g. testcases or patches) to bugs. If there are any attachments, they are listed in this section.
*Dependencies: If this bug cannot be fixed unless other bugs are fixed (depends on), or this bug stops other bugs being fixed (blocks), their numbers are recorded here.
*Votes: Whether this bug has any votes.
Additional Comments: You can add your two cents to the bug discussion here, if you have something worthwhile to say.
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.
Highly advanced querying is done using Boolean Charts, which have their own context-sensitive help .
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:
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 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. |
Send mail to bug owners: Sends mail to the owners of all bugs on the list. |
Edit this query: If you didn't get exactly the results you were looking for, you can return to the Query page through this link and make small revisions to the query you just made so you get more accurate results. |
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:
Go to Landfill in your browser and click Enter a new bug report.
Select a product - any one will do.
Fill in the fields. Bugzilla should have made reasonable guesses, based upon your browser, for the "Platform" and "OS" drop-down boxes. If they are wrong, change them.
Select "Commit" and send in your bug report.
This section distills some Bugzilla tips and best practices that have been developed.
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 convenience of others.
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.
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.
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.
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.
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.
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.
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:
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 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.
![]() | The ability to watch other users may not be available in all Bugzilla installations. If you can't see it, ask your administrator. |
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.
![]() | If you are running the very most recent version of Perl and MySQL (both the executables and development libraries) on your system, you can skip these manual installation steps for the Perl modules by using Bundle::Bugzilla; see Using Bundle::Bugzilla instead of manually installing Perl modules. |
The software packages necessary for the proper running of Bugzilla (with download links) are:
MySQL database server (3.22.5 or greater)
Perl (5.005 or greater, 5.6.1 is recommended if you wish to use Bundle::Bugzilla)
Perl Modules (minimum version):
Template (v2.07)
AppConfig (v1.52)
Text::Wrap (v2001.0131)
File::Spec (v0.8.2)
Data::Dumper (any)
DBD::mysql (v1.2209)
DBI (v1.13)
Date::Parse (any)
CGI::Carp (any)
GD (v1.19) for bug charting
Chart::Base (v0.99c) for bug charting
XML::Parser (any) for the XML interface
MIME::Parser (any) for the email interface
The web server of your choice. Apache is highly recommended.
![]() | It is a good idea, while installing Bugzilla, to ensure that there is some kind of firewall between you and the rest of the Internet, because your machine may be insecure for periods during the install. Many installation steps require an active Internet connection to complete, but you must take care to ensure that at no point is your machine vulnerable to an attack. |
![]() | Linux-Mandrake 8.0 includes every required and optional library for Bugzilla. The easiest way to install them is by using the urpmi utility. If you follow these commands, you should have everything you need for Bugzilla, and checksetup.pl should not complain about any missing libraries. You may already have some of these installed.
|
Visit the MySQL homepage at www.mysql.com to grab and install the latest stable release of the server.
![]() | Many of the binary versions of MySQL store their data files in /var. On some Unix systems, this is part of a smaller root partition, and may not have room for your bug database. You can set the data directory as an option to configure if you build MySQL from source yourself. |
If you install from something other than an RPM or Debian package, you will need to add mysqld to your init scripts so the server daemon will come back up whenever your machine reboots. Further discussion of UNIX init sequences are beyond the scope of this guide.
Change your init script to start mysqld with the ability to accept large packets. By default, mysqld only accepts packets up to 64K long. This limits the size of attachments you may put on bugs. If you add -O max_allowed_packet=1M to the command that starts mysqld (or safe_mysqld), then you will be able to have attachments up to about 1 megabyte. There is a Bugzilla parameter for maximum attachment size; you should configure it to match the value you choose here.
If you plan on running Bugzilla and MySQL on the same machine, consider using the --skip-networking option in the init script. This enhances security by preventing network access to MySQL.
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.
![]() | You can skip the following Perl module installation steps by installing Bundle::Bugzilla from CPAN, which installs all required modules for you. bash# perl -MCPAN -e 'install "Bundle::Bugzilla"' Bundle::Bugzilla doesn't include GD, Chart::Base, or MIME::Parser, which are not essential to a basic Bugzilla install. If installing this bundle fails, you should install each module individually to isolate the problem. |
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:
bash# perl -MCPAN -e 'install "<modulename>"'
To do it the hard way:
Untar the module tarball -- it should create its own directory
CD to the directory just created, and enter the following commands:
bash# perl Makefile.PL
bash# make
bash# make test
bash# make install
![]() | Many people complain that Perl modules will not install for them. Most times, the error messages complain that they are missing a file in "@INC". Virtually every time, this error is due to permissions being set too restrictively for you to compile Perl modules or not having the necessary Perl development libraries installed on your system. Consult your local UNIX systems administrator for help solving these permissions issues; if you are the local UNIX sysadmin, please consult the newsgroup/mailing list for further assistance or hire someone to help you out. |
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 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 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.
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.
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 Perl GD library requires some other libraries that may or may not be installed on your system, including libpng and libgd. The full requirements are listed in the Perl GD library README. If compiling GD fails, it's probably because you're missing a required library. |
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.
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.
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.
![]() | We strongly recommend Apache as the web server to use. The Bugzilla Guide installation instructions, in general, assume you are using Apache. If you have got Bugzilla working using another webserver, please share your experiences with us. |
You'll want to make sure that your web server will run any file with the .cgi extension as a CGI and not just display it. If you're using Apache that means uncommenting the following line in the httpd.conf file:
AddHandler cgi-script .cgi |
With Apache you'll also want to make sure that within the httpd.conf file the line:
Options ExecCGI AllowOverride Limit |
![]() | AllowOverride Limit allows the use of a Deny statement in the .htaccess file generated by checksetup.pl Users of older versions of Apache may find the above lines in the srm.conf and access.conf files, respecitvely. |
![]() | There are important files and directories that should not be a served by the HTTP server - most files in the "data" and "shadow" directories and the "localconfig" file. You should configure your HTTP server to not serve these files. Failure to do so will expose critical passwords and other data. Please see .htaccess files and security for details on how to do this for Apache; the checksetup.pl script should create appropriate .htaccess files for you. |
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.
![]() | If you symlink the bugzilla directory into your Apache's HTML heirarchy, you may receive Forbidden errors unless you add the "FollowSymLinks" directive to the <Directory> entry for the HTML root in httpd.conf. |
Once all the files are in a web accessible directory, make that directory writable by your webserver's user. This is a temporary step until you run the post-install checksetup.pl script, which locks down your installation.
Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl for the correct location of your Perl executable (probably /usr/bin/perl). Otherwise you must hack all the .cgi files to change where they look for Perl. This can be done using the following Perl one-liner, but I suggest using the symlink approach to avoid upgrade hassles.
perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb |
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.
Begin by giving the MySQL root user a password. MySQL passwords are limited to 16 characters.
bash# mysql -u root mysql |
mysql> UPDATE user SET Password=PASSWORD('<new_password>') WHERE user='root'; |
mysql> FLUSH PRIVILEGES; |
Next, we use an SQL GRANT command to create a "bugs" user, and grant sufficient permissions for checksetup.pl, which we'll use later, to work its magic. This also restricts the "bugs" user to operations within a database called "bugs", and only allows the account to connect from "localhost". Modify it to reflect your setup if you will be connecting from another machine or as a different user.
Remember to set <bugs_password> to some unique password.
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY '<bugs_password>'; |
mysql> FLUSH PRIVILEGES; |
![]() | If you are using MySQL 4, the bugs user also needs to be granted the LOCK TABLES and CREATE TEMPORARY TABLES permissions. |
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 |
This file contains a variety of settings you may need to tweak including how Bugzilla should connect to the MySQL database.
The connection settings include:
server's host: just use "localhost" if the MySQL server is local
database name: "bugs" if you're following these directions
MySQL username: "bugs" if you're following these directions
Password for the "bugs" MySQL account; (<bugs_password>) above
Once you are happy with the settings, su to the user your web server runs as, and re-run checksetup.pl. (Note: on some security-conscious systems, you may need to change the login shell for the webserver account before you can do this.) On this second run, it will create the database and an administrator account for which you will be prompted to provide information.
![]() | The checksetup.pl script is designed so that you can run it at any time without causing harm. You should run it after any upgrade to 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.
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:
A complete file path to the command 'dot' (part of GraphViz) will generate the graphs locally
A URL prefix pointing to an installation of the webdot package will generate the graphs remotely
A blank value will disable dependency graphing.
So, to get this working, install GraphViz. If you do that, you need to enable server-side image maps in Apache. Alternatively, you could set up a webdot server, or use the AT&T public webdot server (the default for the webdotbase param). Note that AT&T's server won't work if Bugzilla is only accessible using HTTPS.
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:
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.
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):
cd <your-bugzilla-directory> ; ./whineatnews.pl |
![]() | Depending on your system, crontab may have several manpages. The following command should lead you to the most useful page for this purpose:
|
![]() | This information on using the LDAP authentication options with Bugzilla is old, and the authors do not know of anyone who has tested it. Approach with caution. |
The existing authentication scheme for Bugzilla uses email addresses as the primary user ID, and a password to authenticate that user. All places within Bugzilla where you need to deal with user ID (e.g assigning a bug) use the email address. The LDAP authentication builds on top of this scheme, rather than replacing it. The initial log in is done with a username and password for the LDAP directory. This then fetches the email address from LDAP and authenticates seamlessly in the standard Bugzilla authentication scheme using this email address. If an account for this address already exists in your Bugzilla system, it will log in to that account. If no account for that email address exists, one is created at the time of login. (In this case, Bugzilla will attempt to use the "displayName" or "cn" attribute to determine the user's full name.) After authentication, all other user-related tasks are still handled by email address, not LDAP username. You still assign bugs by email address, query on users by email address, etc.
Using LDAP for Bugzilla authentication requires the Mozilla::LDAP (aka PerLDAP) Perl module. The Mozilla::LDAP module in turn requires Netscape's Directory SDK for C. After you have installed the SDK, then install the PerLDAP module. Mozilla::LDAP and the Directory SDK for C are both available for download from mozilla.org.
Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP directory for authentication. Be very careful when setting up this parameter; if you set LDAP authentication, but do not have a valid LDAP directory set up, you will not be able to log back in to Bugzilla once you log out. (If this happens, you can get back in by manually editing the data/params file, and setting useLDAP back to 0.)
If using LDAP, you must set the three additional parameters: Set LDAPserver to the name (and optionally port) of your LDAP server. If no port is specified, it defaults to the default port of 389. (e.g "ldap.mycompany.com" or "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids must be unique under the DN specified here. Set LDAPmailattribute to the name of the attribute in your LDAP directory which contains the primary email address. On most directory servers available, this is "mail", but you may need to change this.
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\; charset=ISO-8859-1/i" *.cgi *.pl |
All this one-liner command does is search for all instances of "Content-type: text/html" and replaces it with "Content-Type: text/html; charset=ISO-8859-1" . This specification prevents possible Javascript attacks on the browser, and is suggested for all English-speaking sites. For non-English-speaking Bugzilla sites, I suggest changing "ISO-8859-1", above, to "UTF-8".
Note: using <meta> tags to set the charset is not recommended, as there's a bug in Netscape 4.x which causes pages marked up in this way to load twice.
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.
![]() | If you are using an alternate provider of webdot services for graphing (as described when viewing editparams.cgi in your web browser), you will need to change the ip address in data/webdot/.htaccess to the ip address of the webdot server that you are using. |
The default .htaccess file may not provide adequate access restrictions, depending on your web server configuration. Be sure to check the <Directory> entries for your Bugzilla directory so that the .htaccess file is allowed to override web server defaults. For instance, let's assume your installation of Bugzilla is installed to /usr/local/bugzilla . You should have this <Directory> entry in your httpd.conf file:
<Directory /usr/local/bugzilla/> Options +FollowSymLinks +Indexes +Includes +ExecCGI AllowOverride All </Directory> |
The important part above is "AllowOverride All" . Without that, the .htaccess file created by checksetup.pl will not have sufficient permissions to protect your Bugzilla installation.
If you are using Internet Information Server (IIS) or another web server which does not observe .htaccess conventions, you can disable their creation by editing localconfig and setting the $create_htaccess variable to 0.
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.
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.
![]() | After that warning, here's the situation for 2.16 and Windows. It doesn't work at all out of the box. You are almost certainly better off getting the 2.17 version from CVS (after consultation with the Bugzilla Team to make sure you are pulling on a stable day) because we'll be doing a load of work to make the Win32 experience more pleasant than it is now. |
If you still want to try this, to have any hope of getting it to work, you'll need to apply the mail patch from bug 124174. After that, you'll need to read the (outdated) installation instructions below, some (probably a lot better) more recent ones kindly provided by Toms Baugis and Jean-Sebastien Guay, and also check the Bugzilla 2.16 Win32 update page . If we get time, we'll write some better installation instructions for 2.16 and put them up there. But no promises.
![]() | You should be familiar with, and cross-reference, the rest of the Bugzilla Installation section while performing your Win32 installation. Making Bugzilla work on Microsoft Windows is no picnic. Support for Win32 has improved dramatically in the last few releases, but, if you choose to proceed, you should be a very skilled Windows Systems Administrator with strong troubleshooting abilities, a high tolerance for pain, and moderate perl skills. Bugzilla on NT requires hacking source code and implementing some advanced utilities. What follows is the recommended installation procedure for Win32; additional suggestions are provided in Appendix A . |
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 Apache configuration, particularly instructions regarding the "AddHandler" parameter and "ExecCGI" .
![]() | You may also use Internet Information Server or Personal Web Server for this purpose. However, setup is quite different. If ActivePerl doesn't seem to handle your file associations correctly (for .cgi and .pl files), please consult Appendix A . If you are going to use IIS, if on Windows NT you must be updated to at least Service Pack 4. Windows 2000 ships with a sufficient version of IIS. |
Install ActivePerl for Windows. Check http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a current compiled binary.
Please also check the following links to fully understand the status of ActivePerl on Win32: Perl Porting , and Perl on Win32 FAQ
Use ppm from your perl\bin directory to install the following packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD, AppConfig, and Template. You may need to extract them from .zip format using Winzip or other unzip program first. Most of these additional ppm modules can be downloaded from ActiveState, but AppConfig and Template should be obtained from OpenInteract using the instructions on the Template Toolkit web site .
![]() | You can find a list of modules at http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or http://www.activestate.com/PPMPackages/5.6plus |
The syntax for ppm is: C:> ppm <modulename>
Example 4-1. Installing ActivePerl ppd Modules on Microsoft Windows
C:> ppm DBD-Mysql
Watch your capitalization!
ActiveState's 5.6Plus directory also contains an AppConfig ppm, so you might see the following error when trying to install the version at OpenInteract:
Error installing package 'AppConfig': Read a PPD for 'AppConfig', but it is not intended for this build of Perl (MSWin32-x86-multi-thread)
If so, download both the tarball and the ppd directly from OpenInteract, then run ppm from within the same directory to which you downloaded those files and install the package by referencing the ppd file explicitly via in the install command, f.e.:
Install MySQL for NT.
![]() | You can download MySQL for Windows NT from MySQL.com . Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. |
Setup MySQL
C:> C:\mysql\bin\mysql -u root mysql
mysql> DELETE FROM user WHERE Host='localhost' AND User='';
mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE user='root';
"new_password" , above, indicates whatever password you wish to use for your "root" user.
mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost IDENTIFIED BY 'bugs_password';
"bugs_password" , above, indicates whatever password you wish to use for your "bugs" user.
mysql> FLUSH PRIVILEGES;
mysql> create database bugs;
mysql> exit;
C:> C:\mysql\bin\mysqladmin -u root -p reload
Edit checksetup.pl in your Bugzilla directory. Change this line:
my $webservergid = getgrnam($my_webservergroup); |
to
my $webservergid = $my_webservergroup; |
my $webservergid = 'Administrators' |
Run checksetup.pl from the Bugzilla directory.
Edit localconfig to suit your requirements. Set $db_pass to your "bugs_password" from step 5.d , and $webservergroup to "8" .
![]() | Not sure on the "8" for $webservergroup above. If it's wrong, please send corrections. |
Edit defparams.pl to suit your requirements. Particularly, set DefParam("maintainer") and DefParam("urlbase") to match your install.
![]() | This is yet another step I'm not sure of, since the maintainer of this documentation does not maintain Bugzilla on NT. If you can confirm or deny that this step is required, please let me know. |
![]() | There are several alternatives to Sendmail that will work on Win32. The one mentioned here is a suggestion , not a requirement. Some other mail packages that can work include BLAT , Windmail , Mercury Sendmail , and the CPAN Net::SMTP Perl module (available in .ppm). Every option requires some hacking of the Perl scripts for Bugzilla to make it work. The option here simply requires the least. |
Download NTsendmail, available from www.ntsendmail.com . You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
Put ntsendmail.pm into your .\perl\lib directory.
Add to globals.pl:
# these settings configure the NTsendmail process use NTsendmail; $ENV{"NTsendmail"}="your.smtpserver.box"; $ENV{"NTsendmail_debug"}=1; $ENV{"NTsendmail_max_tries"}=5; |
![]() | Some mention to also edit $db_pass in globals.pl to be your "bugs_password" . Although this may get you around some problem authenticating to your database, since globals.pl is not normally restricted by .htaccess , your database password is exposed to whoever uses your web server. |
Find and comment out all occurences of " open(SENDMAIL " in your Bugzilla directory. Then replace them with:
# new sendmail functionality my $mail=new NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my $to=$login; my $subject=$urlbase; $mail->send($from,$to,$subject,$msg); |
![]() | Some have found success using the commercial product, Windmail . You could try replacing your sendmail calls with:
|
Change all references in all files from processmail to processmail.pl , and rename processmail to processmail.pl .
![]() | Many think this may be a change we want to make for main-tree Bugzilla. It's painless for the UNIX folks, and will make the Win32 people happier. |
![]() | Some people have suggested using the Net::SMTP Perl module instead of NTsendmail or the other options listed here. You can change processmail.pl to make this work.
|
![]() | This step is optional if you are using IIS or another web server which only decides on an interpreter based upon the file extension (.pl), rather than the "shebang" line (#/usr/bonsaitools/bin/perl) |
Modify the path to perl on the first line (#!) of all files to point to your Perl installation, and add "perl" to the beginning of all Perl system calls that use a perl script as an argument. This may take you a while. There is a "setperl.csh" utility to speed part of this procedure, available in the Useful Patches and Utilities for Bugzilla section of The Bugzilla Guide. However, it requires the Cygwin GNU-compatible environment for Win32 be set up in order to work. See http://www.cygwin.com/ for details on obtaining Cygwin.
Modify the invocation of all system() calls in all perl scripts in your Bugzilla directory. You should specify the full path to perl for each system() call. For instance, change this line in processmail:
system ("./processmail",@ARGLIST); </programlisting> to <programlisting> system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST); |
Add binmode() calls so attachments will work ( bug 62000 ).
Because Microsoft Windows based systems handle binary files different than Unix based systems, you need to add the following lines to createattachment.cgi and showattachment.cgi before the require 'CGI.pl'; line.
binmode(STDIN); binmode(STDOUT); |
![]() | According to bug 62000 , the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting binmode() at the beginning of the attachment files, there should be logic to determine if binmode() is needed or not. |
![]() | If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as:
|
![]() |
|
![]() | 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.4. |
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. |
This section gives solutions to common Bugzilla installation problems.
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.
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 REFCNT = 1 FLAGS = (PADBUSY,PADMY) |
To fix this, go to <path-to-perl>/lib/DBD/sponge.pm in your Perl installation and replace
my $numFields; if ($attribs->{'NUM_OF_FIELDS'}) { $numFields = $attribs->{'NUM_OF_FIELDS'}; } elsif ($attribs->{'NAME'}) { $numFields = @{$attribs->{NAME}}; |
by
my $numFields; if ($attribs->{'NUM_OF_FIELDS'}) { $numFields = $attribs->{'NUM_OF_FIELDS'}; } elsif ($attribs->{'NAMES'}) { $numFields = @{$attribs->{NAMES}}; |
(note the S added to NAME.)
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 problem.
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 at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 208. Your vendor has not defined Fcntl macro O_EXLOCK, used at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 210. Your vendor has not defined Fcntl macro O_TEMPORARY, used at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. |
Numerous people have reported that upgrading to version 5.6.1 or higher solved the problem for them. A less involved fix is to apply the patch in Figure 4-2. The patch is also available as a patch file.
Figure 4-2. Patch for File::Temp in Perl 5.6.0
--- File/Temp.pm.orig Thu Feb 6 16:26:00 2003 +++ File/Temp.pm Thu Feb 6 16:26:23 2003 @@ -205,6 +205,7 @@ # eg CGI::Carp local $SIG{__DIE__} = sub {}; local $SIG{__WARN__} = sub {}; + local *CORE::GLOBAL::die = sub {}; $bit = &$func(); 1; }; @@ -226,6 +227,7 @@ # eg CGI::Carp local $SIG{__DIE__} = sub {}; local $SIG{__WARN__} = sub {}; + local *CORE::GLOBAL::die = sub {}; $bit = &$func(); 1; }; |
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.
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.
urlbase: This parameter defines the fully qualified domain name and web server path to your Bugzilla installation.
For example, if your Bugzilla query page is http://www.foo.com/bugzilla/query.cgi, set your "urlbase" to http://www.foo.com/bugzilla/.
usebuggroups: This dictates whether or not to implement group-based security for Bugzilla. If set, Bugzilla bugs can have an associated 'group', defining which users are allowed to see and edit the bug.
Set "usebuggroups" to "on" only if you may wish to restrict access to particular bugs to certain groups of users. I suggest leaving this parameter off while initially testing your Bugzilla.
usebuggroupsentry: Bugzilla Products can have a group associated with them, so that certain users can only see bugs in certain products. When this parameter is set to "on", this places all newly-created bugs in the group for their product immediately.
shadowdb: You run into an interesting problem when Bugzilla reaches a high level of continuous activity. MySQL supports only table-level write locking. What this means is that if someone needs to make a change to a bug, they will lock the entire table until the operation is complete. Locking for write also blocks reads until the write is complete. The "shadowdb" parameter was designed to get around this limitation. While only a single user is allowed to write to a table at a time, reads can continue unimpeded on a read-only shadow copy of the database. Although your database size will double, a shadow database can cause an enormous performance improvement when implemented on extremely high-traffic Bugzilla databases.
As a guide, mozilla.org began needing "shadowdb" when they reached around 40,000 Bugzilla users with several hundred Bugzilla bug changes and comments per day.
The value of the parameter defines the name of the shadow bug database. Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a *very* large installation of Bugzilla.
![]() | Enabling "shadowdb" can adversely affect the stability of your installation of Bugzilla. You should regularly check that your database is in sync. It is often advisable to force a shadow database sync nightly via "cron". |
If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb" option on as well. Otherwise you are replicating data into a shadow database for no reason!
shutdownhtml: If you need to shut down Bugzilla to perform administration, enter some descriptive HTML here and anyone who tries to use Bugzilla will receive a page to that effect. Obviously, editparams.cgi will still be accessible so you can remove the HTML and re-enable Bugzilla. :-)
passwordmail: Every time a user creates an account, the text of this parameter (with substitutions) is sent to the new user along with their password message.
Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a quick training blurb about how to use Bugzilla at your site.
useqacontact: This allows you to define an email address for each component, in addition to that of the default owner, who will be sent carbon copies of incoming bugs.
usestatuswhiteboard: This defines whether you wish to have a free-form, overwritable field associated with each bug. The advantage of the Status Whiteboard is that it can be deleted or modified with ease, and provides an easily-searchable field for indexing some bugs that have some trait in common.
whinedays: Set this to the number of days you want to let bugs go in the NEW or REOPENED state before notifying people they have untouched new bugs. If you do not plan to use this feature, simply do not set up the whining cron job described in the installation instructions, or set this value to "0" (never whine).
commenton*: All these fields allow you to dictate what changes can pass without comment, and which must have a comment from the person who changed them. Often, administrators will allow users to add themselves to the CC list, accept bugs, or change the Status Whiteboard without adding a comment as to their reasons for the change, yet require that most other changes come with an explanation.
Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, reassign, or reopen bugs at the very least.
![]() | It is generally far better to require a developer comment when resolving bugs than not. Few things are more annoying to bug database users than having a developer mark a bug "fixed" without any comment as to what the fix was (or even that it was truly fixed!) |
supportwatchers: Turning on this option allows users to ask to receive copies of all a particular other user's bug email. This is, of course, subject to the groupset restrictions on the bug; if the "watcher" would not normally be allowed to view a bug, the watcher cannot get around the system by setting herself up to watch the bugs of someone with bugs outside her privileges. They would still only receive email updates for those bugs she could normally view.
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.
![]() | If you wish to add more administrative users, you must use the MySQL interface. Run "mysql" from the command line, and use these commands:
Yes, that is fourteen "f" 's. A whole lot of f-ing going on if you want to create a new administator. |
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.
After logging in, click the "Users" link at the footer of the query page, and then click "Add a new user".
Fill out the form presented. This page is self-explanatory. When done, click "Submit".
![]() | Adding a user this way will not send an email informing them of their username and password. While useful for creating dummy accounts (watchers which shuttle mail to another system, for instance, or email addresses which are a mailing list), in general it is preferable to log out and use the "New Account" button to create users, as it will pre-populate all the required fields and also notify the user of her account name and password. |
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.)
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 just be the user's login name. Note that users can now change their login names themselves (to any valid email address.)
Real Name: The user's real name. Note that Bugzilla does not require this to create an account.
Password: You can change the user's password here. Users can automatically request a new password, so you shouldn't need to do this often. If you want to disable an account, see Disable Text below.
Disable Text: If you type anything in this box, including just a space, the user is prevented from logging in, or making any changes to bugs via the web interface. The HTML you type in this box is presented to the user when they attempt to perform these actions, and should explain why the account was disabled.
![]() | Don't disable the administrator account! |
![]() | The user can still submit bugs via the e-mail gateway, if you set it up, even if the disabled text field is filled in. The e-mail gateway should not be enabled for secure installations of Bugzilla. |
<groupname>: If you have created some groups, e.g. "securitysensitive", then checkboxes will appear here to allow you to add users to, or remove them from, these groups.
canconfirm: This field is only used if you have enabled the "unconfirmed" status. If you enable this for a user, that user can then move bugs from "Unconfirmed" to a "Confirmed" status (e.g.: "New" status).
creategroups: This option will allow a user to create and destroy groups in Bugzilla.
editbugs: Unless a user has this bit set, they can only edit those bugs for which they are the assignee or the reporter. Even if this option is unchecked, users can still add comments to bugs.
editcomponents: This flag allows a user to create new products and components, as well as modify and destroy those that have no bugs associated with them. If a product or component has bugs associated with it, those bugs must be moved to a different product or component before Bugzilla will allow them to be destroyed.
editkeywords: If you use Bugzilla's keyword functionality, enabling this feature allows a user to create and destroy keywords. As always, the keywords for existing bugs containing the keyword the user wishes to destroy must be changed before Bugzilla will allow it to die.
editusers: This flag allows a user to do what you're doing right now: edit other users. This will allow those with the right to do so to remove administrator privileges from other users or grant them to themselves. Enable with care.
tweakparams: This flag allows a user to change Bugzilla's Params (using editparams.cgi.)
<productname>: This allows an administrator to specify the products in which a user can see bugs. The user must still have the "editbugs" privilege to edit bugs in these 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...)
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:
Select "products" from the footer
Select the "Add" link in the bottom right
Enter the name of the product and a description. The Description field may contain HTML.
Don't worry about the "Closed for bug entry", "Maximum Votes per person", "Maximum votes a person can put on a single bug", "Number of votes a bug in this Product needs to automatically get out of the UNCOMFIRMED state", and "Version" options yet. We'll cover those in a few moments.
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.
To create a new Component:
Select the "Edit components" link from the "Edit product" page
Select the "Add" link in the bottom right.
Fill out the "Component" field, a short "Description", the "Initial Owner" and "Initial QA Contact" (if enabled.) The Component and Description fields may contain HTML; the "Initial Owner" field must be a login name already existing in the database.
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:
From the "Edit product" screen, select "Edit Versions"
You will notice that the product already has the default version "undefined". Click the "Add" link in the bottom right.
Enter the name of the Version. This field takes text only. Then click the "Add" button.
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.
![]() | Milestone options will only appear for a Product if you turned on the "usetargetmilestone" Param in the "Edit Parameters" screen. |
To create new Milestones, set Default Milestones, and set Milestone URL:
Select "Edit milestones" from the "Edit product" page.
Select "Add" in the bottom right corner. text
Enter the name of the Milestone in the "Milestone" field. You can optionally set the "sortkey", which is a positive or negative number (-255 to 255) that defines where in the list this particular milestone appears. This is because milestones often do not occur in alphanumeric order For example, "Future" might be after "Release 1.2". Select "Add".
From the Edit product screen, you can enter the URL of a page which gives information about your milestones and what they mean.
![]() | If you want your milestone document to be restricted so that it can only be viewed by people in a particular Bugzilla group, the best way is to attach the document to a bug in that group, and make the URL the URL of that attachment. |
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:
Navigate to the "Edit product" screen for the Product you wish to modify
Maximum Votes per person: Setting this field to "0" disables voting.
Maximum Votes a person can put on a single bug": It should probably be some number lower than the "Maximum votes per person". Don't set this field to "0" if "Maximum votes per person" is non-zero; that doesn't make any sense.
Number of votes a bug in this product needs to automatically get out of the UNCONFIRMED state: Setting this field to "0" disables the automatic move of bugs from UNCONFIRMED to NEW.
Once you have adjusted the values to your preference, click "Update".
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.
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:
Select the "groups" link in the footer.
Take a moment to understand the instructions on the "Edit Groups" screen, then select the "Add Group" link.
Fill out the "New Name", "New Description", and "New User RegExp" fields. "New User RegExp" allows you to automatically place all users who fulfill the Regular Expression into the new group. When you have finished, click "Add".
To use Product-Based Groups:
Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.
![]() | XXX is this still true? "usebuggroupsentry" has the capacity to prevent the administrative user from directly altering bugs because of conflicting group permissions. If you plan on using "usebuggroupsentry", you should plan on restricting administrative account usage to administrative duties only. In other words, manage bugs with an unpriveleged user account, and manage users, groups, Products, etc. with the administrative account. |
In future, when you create a Product, a matching group will be automatically created. If you need to add a Product Group to a Product which was created before you turned on usebuggroups, then simply create a new group, as outlined above, with the same name as the Product.
![]() | Bugzilla currently has a limit of 64 groups per installation. If you have more than about 50 products, you should consider running multiple Bugzillas. Ask in the newsgroup for other suggestions for working around this restriction. |
Note that group permissions are such that you need to be a member of all the groups a bug is in, for whatever reason, to see that bug.
![]() | Poorly-configured MySQL and Bugzilla installations have given attackers full access to systems in the past. Please take these guidelines seriously, even for Bugzilla machines hidden away behind your firewall. 80% of all computer trespassers are insiders, not anonymous crackers. |
![]() | These instructions must, of necessity, be somewhat vague since Bugzilla runs on so many different platforms. If you have refinements of these directions, please submit a bug to Bugzilla. |
![]() | This is not meant to be a comprehensive list of every possible security issue regarding the tools mentioned in this section. There is no subsitute for reading the information written by the authors of any software running on your system. |
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.
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.
Make sure you are running at least version 3.22.32 of MySQL as earlier versions had notable security holes.
Consult the documentation that came with your system for information on making mysqld run as an unprivleged user.
You should also be sure to disable the anonymous user account and set a password for the root user. This is accomplished using the following commands:
bash$ mysql mysql mysql> DELETE FROM user WHERE user = ''; mysql> UPDATE user SET password = password('new_password') WHERE user = 'root'; mysql> FLUSH PRIVILEGES; |
From this point forward you will need to use mysql -u root -p and enter new_password when prompted when using the mysql client.
If you run MySQL on the same machine as your httpd server, you should consider disabling networking from within MySQL by adding the following to your /etc/my.conf:
[myslqd] # Prevent network access to MySQL. skip-networking |
You may also consider running MySQL, or even all of Bugzilla in a chroot jail; however, instructions for doing that are beyond the scope of this document.
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.
![]() | You will need to set the webservergroup to the group you created for your webserver to run as in localconfig. This will allow ./checksetup.pl to better adjust the file permissions on your Bugzilla install so as to not require making anything world-writable. |
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, syncshadowdb
But allow: localconfig.js, localconfig.rdf
In data:
Block everything
But allow: duplicates.rdf
In data/webdot:
If you use a remote webdot server:
Block everything
But allow *.dot only for the remote webdot server
Otherwise, if you use a local GraphViz:
Block everything
But allow: *.png, *.gif, *.jpg, *.map
And if you don't use any dot:
Block everything
In Bugzilla:
Block everything
In template:
Block everything
![]() | Bugzilla ships with the ability to generate .htaccess files instructing Apache which files should and should not be accessible. |
You should test to make sure that the files mentioned above are not accessible from the Internet, especially your localconfig file which contains your database password. To test, simply point your web browser at the file; for example, to test mozilla.org's installation, we'd try to access http://bugzilla.mozilla.org/localconfig. You should get a 403 Forbidden error.
![]() | Not following the instructions in this section, including testing, may result in sensitive information being globally accessible. |
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.
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.
![]() | Don't directly edit the compiled templates in data/template/* - your changes will be lost when Template Toolkit recompiles them. |
![]() | It is recommended that you run ./checksetup.pl after any template edits, especially if you've created a new file in the custom directory. |
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.
![]() | If you are making template changes that you intend on submitting back for inclusion in standard Bugzilla, you should read the relevant sections of the Developers' Guide. |
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> .
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"> |
BuildID: [% form.buildid %] |
BuildID: 20020303 |
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
There are also three different methods to upgrade your installation.
Using CVS (Example 5-1)
Downloading a new tarball (Example 5-2)
Applying the relevant patches (Example 5-3)
Which options are available to you may depend on how large a jump you are making and/or your network configuration.
Revisions are normally released to fix security vulnerabilities and are distinguished by an increase in the third number. For example, when 2.16.2 was released, it was a revision to 2.16.1.
Point releases are normally released when the Bugzilla team feels that there has been a significant amount of progress made between the last point release and the current time. These are often proceeded by a stabilization period and release candidates, however the use of development versions or release candidates is beyond the scope of this document. Point releases can be distinguished by an increase in the second number, or minor version. For example, 2.16.2 is a newer point release than 2.14.5.
The examples in this section are written as if you were updating to version 2.16.2. The procedures are the same regardless if you are updating to a new point release or a new revision. However, the chance of running into trouble increases when upgrading to a new point release, escpecially if you've made local changes.
These examples also assume that your Bugzilla installation is at /var/www/html/bugzilla. If that is not the case, simply substitute the proper paths where appropriate.
Example 5-1. Upgrading using CVS
Every release of Bugzilla, whether it is a revision or a point release, is tagged in CVS. Also, every tarball we have distributed on't "CENTER" VALIG >yren methoading usi. ondidates, h, point not re sure that y availabtwork agra-nto a gzilla.mozilcieved o point 240 2.1 then UL >
![]() | ) |
/var/www/html/bugzB>./checkseanP " c skseanP nd" >skseanP wha/ _lease txtanP r_bug template/en/d/rogr/notpse>.htmanges.en> |
/P >
![]() | cvs updateanges.en beg con bugs t bugs any, local ch si d, iun availab to prort to confd the can of use your Bug(isioan just ng at ituteug roed when usexistle)is tag wiusd-writable. A >) |
![]() | , now net you run ./checksetup.pl eated befoat your Bugds to ups tag wiHTML (tritable. A >) |
Exam2le 5-1. Upgrading se inrade-tng CVS
Do ck up the lnrade-t. This is can just three patnWhich udir tmedits, especially not made local changes.en>/var/wwgzB>dag thew/html/bu-rsion 2nra.gzgzB>not |
/P >
![]() |
![]() | - your made your installatthe caitable. A >) |
Exam3le 5-1. Upgrading grade-png CVS
are avai feel for rRevibe ioh come fros ca
r This iIt is recomm and easobably wh'you will
enshuphippeder ithodguteudgutn the Bugz. If tere houl
afteminor veu will
Tmake tou should Toitto usethree patnthods to upision in the future.en>
/P
>/var/www/html/bugzB>dag thew/html/bu-rsion1-to-rsion 2thre.gzgzB>not
)Example 5-1
priate.
HREF="hpur dc.perdge .eck/Lur dc/perdge /p4dti/nd" >indeog" >an thenl
duiguide of inform This ould abeot hhangeckin csort ise us for/ht/TBto give cely not hmradeupgrr, or sevant padgetusiriate.ading Bugon't "CE If yo your is/wa p4dtio etag assignwhich sriate. muldefASSodmi>.haracradependis conrs of is doinformdgeto use it.P or reltrupatnttutevl chis/.s tioned dgetfurand e more informTmakeFAQ also incqussnstrucis ice thomm lsepaths ision i use i
Waths d yoIee andde of inform care ading Bu?vs" >ense="_t>
Waatu >enseo ading Bug have distructure? i " >
>
Waatu make is ani-patureASjASSpamhs is currg UI, n the Bu i /ht-dmi>.UI,? i " >
Waoependis conn the Bu? i " >
>
.UI, an in das?
i
"
>Way ondere ading BugoffL filtpaturusexis new f ke is ati the a
i deal with dmi>.UI, soft so?
i
"
>Way MySQL? t onelarly interesharddisaading Bugt yoal w >Omi>le/Syn da/Msql/PostgreSQL/MSSQL.
i
"
>Way os wits Der sasonably
*.pl IThis hs wnonablyother wes to changading Bugtaokie"text?
i
"
>/DDmma IThading Bugida-by renumbedoely not want tsits, ee soft sotabas >asits, ee to nfipgrentry sond thenmadeupe?
i
"
> Cahe main Bug athgonfet deaas >Perdge (SCM soft so)?
i
"
> Dle ading BugaNot hhang ing ing h muleASjASSp?
i
"
> If Iea sond
>HoleASjASSpations, arde/Tisiotag ugser tag assignming iyou >ading Bugt bu hanmtalledreleasaNot hrom tisug uishLASjASS,tss, he abetc?
i
"
> Dle ading BugaNot hmment in cs (type,ts eenshoSpatng ibetc)?iableempla >ad befohs wny cters thaNOTgaNot ed?
i
"
> Dle ading BugaNot hu it du to dsing youeAiorerabieleasa tops?1Dlgidla >s you TML (tr dome wes to changfield or strary field of inte m,oae be >hangehoich pietworpious stheir ?
i
"
> Dle ading Bugotes, p wny e bug repot new fe,r thricformaaphe edtc?/A
n >user,hhangntentr setuf
>. Ifdanageeveloplat it ard. :)
i
"
> IThis hs em youis a signform ncreatS. know wely ard wer", theicklyl w >em yo?
i
"
> Caheem youis a signformbanguar picoult ysignm mu w >peor exaer inosion iTo Li To CC Li To BCC Li Tbetc?
i
"
> Dll your u not want ts>Holey be partbe >htentr sem youwheliignfor?
i
"
> Dle ading BugaNot hilter nded meug e perioexeug e ?1If Ieplatares, p app >w uphato the bug ru are u MS Wordoutpufault temp tteed the tempu w > meug e pnning"mradeupg"strary ?1If Ie, buattache, or mak, may or sa,quso,la >arioexeug tteedilter ndMS Excelmp I os wat?
i
"
> H, itnyit's convn the Bugzohis is anolkit lan nded ure pash la >cant rabi?1ITh Toolled zous ?
i
"
> Caheag Then, crons,t tse bug s?1Cahetforeil to dpashWordo of in?la >Excelo of in?la >&
"
> Dle ading Bug CGIs have the abili, arde/ish pa, phrt reb TMLant be >, arde?la >&
"
> Dle ading Bugotes, p It irstall.UI, eased whch thesim ane prery to ac >hos wits theutp?1Dle wits
sDeveosiickly is acoftteed titutpu dpash, bec >llend oad beforeis a sed?
i
"
> Ad befohs wny ttinu et new feaotes, pr?
i
"
> Cahe your binosion ientry swhT
> ttinu e dpashnt of pr?
i
"
> Waatuhtentr shum you ssinc pamhs nn proc nded osion f
>oo your ioae be >pendis cnn the Bu? Sts, ee omat,ywaatuhtentr sskicaThdle witDeveosiver a nee > CGI?1I, now nede to fineatweif youte iohipped with Bugzilatuhtens scop e tis, ualke tou swe, now nehir cronsnd omed -w tteedc ca
vr bu
>Appyl w >"Out-of- wi-Box"aerlges/ca
i
"
> Waatuhiich c thectione up by lookieatweied to d nehir cpeor e
>oo your ila >ariopendis cnhangading Bu?1IThisiilla is sometteed also h one1lleweeksa nee > your ioae ugtaun examph one1he pweeksignmendis cninedet to czf ke iThisiila >anm -weeks your io These nolprer fucanniichjobtalle1tDeveos, 21peor ex w >etc?
i
"
> IThis hs wnyu
>ensrepot f ke is ant fsmethoading ading Bu?1An,la >out-of-pll.eedc ca
dhahetfo bodabienn procitteuild Ide tioned?
i
"
>/DDmma (I'ed dgNot edetfo g the instructionsyo your ignformtions sectioni this)?
i
"
> Ad befohs wny o fix secnd ilemihipped with Bu?
i
"
> I'ed rmat=e docum wits
st securi chsl be mentaggehri Yeh'sr (for secu >advisdirecti5/10/20001advis,nwrat isnet yoMySQLt16.2ootationsam of runnincu >nd ilemihippedMySQLtno upto rung netwo irn't dia
i
"
>/DDmma I not h who ondere , but war I'm etheinfipg/tes repd with Bugzionsusers , but be lt ysem you fla >aryit'slemsent > I , butweupeatnewskse be weupeookila is someo us, ke is andhahgzo lL, twla > ugst > I users plat/f you want tPAScm yot wantriopenlgoffc ndeug_em yokse.cu >Waatualard iistis
il Ie CGI?
i
"
>> Eroce also FOREVERt war< forich comeading Bug--t". Ifextlarlpecwot .cu >Waaturs tr?
i
"
> > /DDmma I'ed he standard Buleases cure pippedOmi>le?
i
"
> Itusink my an in datmightg wiHTrrupttd, ke idis cninvfor he buila pWaatcu >il Iedf?
i
"
> I , butignmethe cannt toer ine builataggmy an in dat > Itusink I'ed guar piMySQLtpbe d submso irn't dieblemsndard Bul It's eas'tcu > idn't a
i
"
>> in in das?
i
"
>/DDmma W. If thchseeasilabyother wt yoading BugormWin32 (Win98+/NT/2K)?
i
"
> IThis hs wox fndle::ading Bu" notvfodiffdgetWin32?
i
"
> CGI'pamhs f yoUI, ebugs t"la is somuglis>This ia vfor hWindows
> >wheliignfor" o a g1Way?
i
"
> I'm CGsometinto trships witper
a ulfsmethoNTrs ill y looavailabur ku fla >hos witan in dat
i
"
>/DDmma Twitquso, p langualso, /locadingd feport is hs woormat=another wayso,?
i
"
> I'm /locadeguishtfo be CGske I"tworpi=blemtguidmP
>ISnd on tID: [%cu >Way ondere toa tag d titutpuignmd wer",Ietworpioit?
i
"
> Iteas'tr p
>Do arys someinhos witan in daevia1
>I"Chen, cAment in cect >is/..#1Waatuam IedfUI, eron,?
i
"
>> /DDmma W. If ugsef yo cnn the Bu rightgn .UI,-eAioreryisting"
>> eAioreryg wi"---"b edit i sc "P2"?
i
"
>.UI,-erade-patch> W. I'shtfo beabyother wl sevant p?#1Waaturthislis de they sI dgNot ?
i
"
>/DDmma/P
> goffL san >ading Bugas", the part irion in staoffL sometoon how eASjASSp%cu >Tforeil nt tsir inull mumnt fsmcters thapretrygheftygzionsty to tlecu >a dire arly intereshamr io TjASSp%cu >& A
>) Thersre'sa oexetio refdan >ading Bughi>.harnosion im yoUI, rogr/newsgintpawho ctioni is/wla >hos To memseltis
are avai festy to preeck ensaes/ca
i sby appeis is a mesoion im yoUI, rogrt s.repotisio voluarle hea i
>) cu >& A
>) ) ) leera
easedi w upto rubs wnog sue,
wh8
cr is1out.onably
Qussnstru platly nded as.s tbyfdanagers. :-)ea i
>) >This GUIudgetad aepotrary f ndading Bugaed t be >hient sY Ieasee>Not h
develoctioni s new f atcu > CVS (hea i
>) .ageopably
ord - suCryour R bug s ading ODBCf1 Ichoide it dl to doopably
be softteedgis,nwrTT
> ery to esoion ian in daeile idis cnsoicopably
o fix secimeliignforsh Evencially rs t,houl-o lL,ry to esoion opably
bugsean in daeasedi bypas wits
w f bugsed new feasf1ading Bu%cu >& A
>) .onably
i
>) *.pl HREF="http:zysql.eck/doc/B/a/Btinu >inde
"
>
i A
>) CckinrML-spBht-dmi>.UI, soft soteype omatdc cailla ipaths upw stsla >r s$20,0001 o use ofv5-10 f
>D ing
>ensesvisading Bugltrupataes/cop e it are avai comeskicanotmeond s r sse inewsgintp. Srmat=cqussnstru
wrelTnswouedbefohs wndbeforhea i
>)Netscape/AOL0"
> Milla.mozil0"
> NASA0"
> RterHatuSoft so0"
> SuSngCorp0"
> TwitH pa tPASjASS0"
> AbiSsinc 0"
> Rta oTiichEarlyeAisfe,rInc0"
> Eggf thsozil0"
> SdminauSoft so0"
> RockLinux0"
> Chen,i tsLabs ( Tr or sSant Bp heer)0"
> TwitAp fo nt aes/c0"
> TwitGnr in nt aes/c0"
> Ximiac0"
> Linux-Mradr T/0BODYER="TR
> /0
>
) /0
> /0
>
) /0
>