diff options
89 files changed, 11040 insertions, 10985 deletions
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html index 3b3283361..b95ae37bd 100644 --- a/docs/html/Bugzilla-Guide.html +++ b/docs/html/Bugzilla-Guide.html @@ -1,10 +1,12 @@ <HTML ><HEAD ><TITLE ->The Bugzilla Guide - 2.17.5 Development Release</TITLE +>The Bugzilla Guide - 2.17.5 + Development Release</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><META +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><META NAME="KEYWORD" CONTENT="Bugzilla"><META NAME="KEYWORD" @@ -42,61 +44,36 @@ CLASS="title" ><A NAME="AEN2" ></A ->The Bugzilla Guide - 2.17.5 Development Release</H1 -><H3 -CLASS="author" -><A -NAME="AEN5" -></A ->Matthew P. Barnson</H3 -><H3 -CLASS="author" -><A -NAME="AEN9" -></A ->Jacob Steenhagen</H3 +>The Bugzilla Guide - 2.17.5 + Development Release</H1 ><H3 CLASS="corpauthor" >The Bugzilla Team</H3 ><P CLASS="pubdate" ->2003-11-01<BR></P +>2004-01-15<BR></P ><DIV ><DIV CLASS="abstract" ><A -NAME="AEN14" +NAME="AEN7" ></A ><P ></P ><P -> This is the documentation for Bugzilla, the mozilla.org - bug-tracking system. +> This is the documentation for Bugzilla, a + bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software - that powers issue-tracking for hundreds of - organizations around the world, tracking millions of bugs. - </P -><P -> - 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 the <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A -> component. + that tracks millions of bugs and issues for hundreds of + organizations around the world. </P ><P ->This is a development version of this guide. Information in it - is subject to change before the 2.18 release of this guide - (which will correspond with the 2.18 release of Bugzilla). - </P -><P > The most current version of this document can always be found on the <A HREF="http://www.bugzilla.org/documentation.html" TARGET="_top" ->Bugzilla Documentation Page</A +>Bugzilla + Documentation Page</A >. </P ><P @@ -154,13 +131,18 @@ HREF="#introduction" ><DL ><DT >2.1. <A -HREF="#whatis" +HREF="#what-is-bugzilla" >What is Bugzilla?</A ></DT ><DT >2.2. <A -HREF="#why" ->Why Should We Use Bugzilla?</A +HREF="#why-tracking" +>Why use a bug-tracking system?</A +></DT +><DT +>2.3. <A +HREF="#why-bugzilla" +>Why use Bugzilla?</A ></DT ></DL ></DD @@ -173,19 +155,49 @@ HREF="#using" ><DL ><DT >3.1. <A -HREF="#how" ->How do I use Bugzilla?</A +HREF="#myaccount" +>Create a Bugzilla Account</A ></DT ><DT >3.2. <A +HREF="#bug_page" +>Anatomy of a Bug</A +></DT +><DT +>3.3. <A +HREF="#query" +>Searching for Bugs</A +></DT +><DT +>3.4. <A +HREF="#list" +>Bug Lists</A +></DT +><DT +>3.5. <A +HREF="#bugreports" +>Filing Bugs</A +></DT +><DT +>3.6. <A +HREF="#patchviewer" +>Patch Viewer</A +></DT +><DT +>3.7. <A HREF="#hintsandtips" >Hints and Tips</A ></DT ><DT ->3.3. <A +>3.8. <A HREF="#userpreferences" >User Preferences</A ></DT +><DT +>3.9. <A +HREF="#reporting" +>Reports</A +></DT ></DL ></DD ><DT @@ -202,21 +214,26 @@ HREF="#stepbystep" ></DT ><DT >4.2. <A +HREF="#http" +>HTTP Server Configuration</A +></DT +><DT +>4.3. <A HREF="#extraconfig" >Optional Additional Configuration</A ></DT ><DT ->4.3. <A +>4.4. <A HREF="#os-specific" >OS Specific Installation Notes</A ></DT ><DT ->4.4. <A -HREF="#http" ->HTTP Server Configuration</A +>4.5. <A +HREF="#security" +>Bugzilla Security</A ></DT ><DT ->4.5. <A +>4.6. <A HREF="#troubleshooting" >Troubleshooting</A ></DT @@ -241,136 +258,96 @@ HREF="#useradmin" ></DT ><DT >5.3. <A -HREF="#programadmin" ->Product, Component, Milestone, and Version Administration</A +HREF="#products" +>Products</A ></DT ><DT >5.4. <A -HREF="#voting" ->Voting</A +HREF="#components" +>Components</A ></DT ><DT >5.5. <A -HREF="#groups" ->Groups and Group Security</A +HREF="#versions" +>Versions</A ></DT ><DT >5.6. <A -HREF="#security" ->Bugzilla Security</A +HREF="#milestones" +>Milestones</A ></DT ><DT >5.7. <A -HREF="#cust-templates" ->Template Customization</A +HREF="#voting" +>Voting</A ></DT ><DT >5.8. <A -HREF="#cust-change-permissions" ->Change Permission Customization</A +HREF="#groups" +>Groups and Group Security</A ></DT ><DT >5.9. <A HREF="#upgrading" >Upgrading to New Releases</A ></DT -><DT ->5.10. <A -HREF="#integration" ->Integrating Bugzilla with Third-Party Tools</A -></DT ></DL ></DD ><DT ->A. <A -HREF="#faq" ->The Bugzilla FAQ</A -></DT -><DT ->B. <A -HREF="#database" ->The Bugzilla Database</A +>6. <A +HREF="#customization" +>Customising Bugzilla</A ></DT ><DD ><DL ><DT ->B.1. <A -HREF="#dbmodify" ->Modifying Your Running System</A +>6.1. <A +HREF="#cust-templates" +>Template Customization</A ></DT ><DT ->B.2. <A -HREF="#dbdoc" ->MySQL Bugzilla Database Introduction</A +>6.2. <A +HREF="#cust-change-permissions" +>Customizing Who Can Change What</A ></DT -></DL -></DD ><DT ->C. <A -HREF="#patches" ->Useful Patches and Utilities for Bugzilla</A +>6.3. <A +HREF="#dbmodify" +>Modifying Your Running System</A ></DT -><DD -><DL ><DT ->C.1. <A -HREF="#rewrite" ->Apache - <TT -CLASS="filename" ->mod_rewrite</TT -> - - magic</A +>6.4. <A +HREF="#dbdoc" +>MySQL Bugzilla Database Introduction</A ></DT ><DT ->C.2. <A -HREF="#cmdline" ->Command-line Bugzilla Queries</A +>6.5. <A +HREF="#integration" +>Integrating Bugzilla with Third-Party Tools</A ></DT ></DL ></DD ><DT ->D. <A -HREF="#variants" ->Bugzilla Variants and Competitors</A -></DT -><DD -><DL -><DT ->D.1. <A -HREF="#variant-redhat" ->Red Hat Bugzilla</A -></DT -><DT ->D.2. <A -HREF="#variant-fenris" ->Loki Bugzilla (Fenris)</A -></DT -><DT ->D.3. <A -HREF="#variant-issuezilla" ->Issuezilla</A -></DT -><DT ->D.4. <A -HREF="#variant-scarab" ->Scarab</A +>A. <A +HREF="#faq" +>The Bugzilla FAQ</A ></DT ><DT ->D.5. <A -HREF="#variant-perforce" ->Perforce SCM</A +>B. <A +HREF="#patches" +>Contrib</A ></DT +><DD +><DL ><DT ->D.6. <A -HREF="#variant-sourceforge" ->SourceForge</A +>B.1. <A +HREF="#cmdline" +>Command-line Search Interface</A ></DT ></DL ></DD ><DT ->E. <A +>C. <A HREF="#gfdl" >GNU Free Documentation License</A ></DT @@ -484,14 +461,6 @@ HREF="#install-perlmodules-cpan" >Installing perl modules with CPAN</A ></DT ><DT ->4-2. <A -HREF="#http-apache-htaccess" -><TT -CLASS="filename" ->.htaccess</TT -> files for Apache</A -></DT -><DT >5-1. <A HREF="#upgrade-cvs" >Upgrading using CVS</A @@ -524,7 +493,7 @@ NAME="copyright" ></A >1.1. Copyright Information</H1 ><A -NAME="AEN35" +NAME="AEN25" ></A ><TABLE BORDER="0" @@ -548,7 +517,7 @@ VALIGN="TOP" Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in <A HREF="#gfdl" ->Appendix E</A +>Appendix C</A >. </P ></TD @@ -564,7 +533,7 @@ ALIGN="RIGHT" VALIGN="TOP" >--<SPAN CLASS="attribution" ->Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN +>Copyright (c) 2000-2004 The Bugzilla Team</SPAN ></TD ><TD WIDTH="10%" @@ -574,7 +543,7 @@ WIDTH="10%" ><P > If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, - please contact The Bugzilla Team. + please contact the Bugzilla Team. </P ></DIV ><DIV @@ -587,7 +556,7 @@ NAME="disclaimer" >1.2. Disclaimer</H1 ><P > No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content at your own risk. + Follow the instructions herein 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 @@ -595,35 +564,20 @@ NAME="disclaimer" war. Proceed with caution. </P ><P -> 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. - </P -><P > 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, + wholeheartedly endorse the use of GNU/Linux; it is an extremely + versatile, stable, and robust operating system that offers an ideal operating environment for Bugzilla. </P ><P -> 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! - </P -><P > 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 + ensure that all exploitable bugs or options have been + fixed, security holes surely exist. Great care should be taken both in + the installation and usage of this software. The Bugzilla development + team members assume no liability for your use of this software. You have + the source code, and are responsible for auditing it yourself to ensure your security needs are met. </P ></DIV @@ -639,31 +593,17 @@ NAME="newversions" > This is the 2.17.5 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. - This version of the guide, like its associated Bugzilla version is a - development version. Information is subject to change between now and - when 2.18 is released. + This version of the guide, like its associated Bugzilla version, is a + development version. - 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. </P ><P > The newest version of this guide can always be found at <A HREF="http://www.bugzilla.org" TARGET="_top" >http://www.bugzilla.org</A ->; including - documentation for past releases and the current development version. - </P -><P -> The documentation for the most recent stable release of Bugzilla can also - be found at - <A -HREF="http://www.tldp.org" -TARGET="_top" ->The Linux Documentation Project</A ->. +>; however, you should read the version + which came with the Bugzilla release you are using. </P ><P > The latest version of this document can always be checked out via CVS. @@ -703,116 +643,18 @@ NAME="credits" contribution to the Bugzilla community: </P ><P -></P -><DIV -CLASS="variablelist" -><DL -><DT ->Matthew P. Barnson <TT -CLASS="email" -><<A -HREF="mailto:mbarnson@sisna.com" ->mbarnson@sisna.com</A ->></TT -></DT -><DD -><P ->for the Herculaean task of pulling together the Bugzilla Guide - and shepherding it to 2.14. - </P -></DD -><DT ->Terry Weissman <TT -CLASS="email" -><<A -HREF="mailto:terry@mozilla.org" ->terry@mozilla.org</A ->></TT -></DT -><DD -><P ->for initially writing Bugzilla and creating the README upon - which the UNIX installation documentation is largely based. - </P -></DD -><DT ->Tara Hernandez <TT -CLASS="email" -><<A -HREF="mailto:tara@tequilarists.org" ->tara@tequilarists.org</A ->></TT -></DT -><DD -><P ->for keeping Bugzilla development going strong after Terry left - mozilla.org and for running landfill. - </P -></DD -><DT ->Dave Lawrence <TT -CLASS="email" -><<A -HREF="mailto:dkl@redhat.com" ->dkl@redhat.com</A ->></TT -></DT -><DD -><P ->for providing insight into the key differences between Red - Hat's customized Bugzilla, and being largely responsible for - <A -HREF="#variant-redhat" ->Section D.1</A ->. - </P -></DD -><DT ->Dawn Endico <TT -CLASS="email" -><<A -HREF="mailto:endico@mozilla.org" ->endico@mozilla.org</A ->></TT -></DT -><DD -><P ->for being a hacker extraordinaire and putting up with Matthew's - incessant questions and arguments on irc.mozilla.org in #mozwebtools - </P -></DD -><DT ->Jacob Steenhagen <TT -CLASS="email" -><<A -HREF="mailto:jake@bugzilla.org" ->jake@bugzilla.org</A ->></TT -></DT -><DD -><P ->for taking over documentation during the 2.17 development - period. - </P -></DD -></DL -></DIV +> Matthew P. Barnson, Kevin Brannen, Dawn Endico, Ben FrantzDale, Eric Hanson, Tara Hernandez, Dave Lawrence, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Jacob Steenhagen, Ron Teitelbaum, Terry Weissman, Martin Wulffeld. + </P ><P > Last but not least, all the members of the <A HREF="news://news.mozilla.org/netscape/public/mozilla/webtools" TARGET="_top" ->news://news.mozilla.org/netscape/public/mozilla/webtools</A +> netscape.public.mozilla.webtools</A > newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened. </P -><P -> Thanks also go to the following people for significant contributions - to this documentation (in alphabetical order): - Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Martin Wulffeld, Ron Teitelbaum, Spencer Smith, Zach Liption - . - </P ></DIV ><DIV CLASS="section" @@ -827,7 +669,7 @@ NAME="conventions" ><DIV CLASS="informaltable" ><A -NAME="AEN113" +NAME="AEN73" ></A ><P ></P @@ -999,7 +841,7 @@ VALIGN="TOP" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->File Names</TD +>File and directory names</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -1013,20 +855,6 @@ CLASS="filename" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Directory Names</TD -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" -> <TT -CLASS="filename" ->directory</TT -> - </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" >Commands to be typed</TD ><TD ALIGN="LEFT" @@ -1041,7 +869,7 @@ CLASS="command" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Applications Names</TD +>Applications names</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -1100,7 +928,7 @@ VALIGN="MIDDLE" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Environment Variables</TD +>Environment variables</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -1114,19 +942,6 @@ CLASS="envar" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Emphasized word</TD -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" -> <EM ->word</EM -> - </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" >Term found in the glossary</TD ><TD ALIGN="LEFT" @@ -1144,7 +959,7 @@ CLASS="glossterm" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Code Example</TD +>Code example</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -1179,6 +994,16 @@ CLASS="sgmltag" ><P ></P ></DIV +><P +> + 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 the <A +HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" +TARGET="_top" +>Bugzilla Documentation</A +> component. + </P ></DIV ></DIV ><DIV @@ -1193,24 +1018,55 @@ CLASS="section" ><H1 CLASS="section" ><A -NAME="whatis" +NAME="what-is-bugzilla" ></A >2.1. What is Bugzilla?</H1 ><P > Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track - 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. + of outstanding problems with their products. </P ><P +><EM +>Do we need more here?</EM +></P +></DIV +><DIV +CLASS="section" +><HR><H1 +CLASS="section" +><A +NAME="why-tracking" +></A +>2.2. Why use a bug-tracking system?</H1 +><P +>For many years, defect-tracking software was principally + the domain of large software development houses. Most smaller shops + simply relied on + shared lists and email to monitor the status of defects. This procedure + was error-prone and tended to cause those bugs judged least significant by + developers to be dropped or ignored.</P +><P +>Integrated + defect-tracking systems reduce downtime, increase productivity, and raise + customer satisfaction with their systems. Along with full disclosure, an + open bug-tracker allows you to keep in touch with your 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 method for accounting for unusual system or software + issues.</P +></DIV +><DIV +CLASS="section" +><HR><H1 +CLASS="section" +><A +NAME="why-bugzilla" +></A +>2.3. Why use Bugzilla?</H1 +><P >Bugzilla boasts many advanced features. These include: <P ></P @@ -1267,40 +1123,6 @@ NAME="whatis" ></UL > </P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="why" -></A ->2.2. Why Should We Use Bugzilla?</H1 -><P ->For many years, defect-tracking software has remained principally - the domain of large software development houses. Even then, most shops - 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.</P -><P ->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.</P -><P ->But why should - <EM ->you</EM -> - - use Bugzilla?</P ><P >Bugzilla is very adaptable to various situations. Known uses currently include IT support queues, Systems Administration deployment @@ -1325,22 +1147,6 @@ TARGET="_top" >, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems.</P -><P ->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 - <EM ->something</EM -> - 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.</P -><P ->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.</P ></DIV ></DIV ><DIV @@ -1350,46 +1156,37 @@ CLASS="chapter" NAME="using" ></A >Chapter 3. Using Bugzilla</H1 -><DIV -CLASS="section" -><H1 -CLASS="section" -><A -NAME="how" -></A ->3.1. How do I use Bugzilla?</H1 ><P >This section contains information for end-users of Bugzilla. - There is a Bugzilla test installation, called - <A -HREF="http://landfill.bugzilla.org/" + There is a Bugzilla test installation, called + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/" TARGET="_top" >Landfill</A >, - 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.</P + which you are welcome to play with (if it's up.) + However, it does not necessarily + have all Bugzilla features enabled, and runs an up-to-the-minute version, + so some things may not quite work as this document describes.</P ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="myaccount" ></A ->3.1.1. Create a Bugzilla Account</H2 +>3.1. Create a Bugzilla Account</H1 ><P >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: - <A + 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: + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/" TARGET="_top" >http://landfill.bugzilla.org/bugzilla-tip/</A >. - </P + </P ><P ></P ><OL @@ -1397,443 +1194,441 @@ TYPE="1" ><LI ><P >Click the - <SPAN + <SPAN CLASS="QUOTE" >"Open a new Bugzilla account"</SPAN > - link, enter your email address and, optionally, your name in the - spaces provided, then click - <SPAN + link, enter your email address and, optionally, your name in the + spaces provided, then click + <SPAN CLASS="QUOTE" >"Create Account"</SPAN > - .</P + .</P ></LI ><LI ><P >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.</P + you provided, which contains your login name (generally the + same as the email address), and a password. + This password is randomly generated, but can be + changed to something more memorable.</P ></LI ><LI ><P >Click the - <SPAN + <SPAN CLASS="QUOTE" >"Log In"</SPAN > - 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 - <SPAN + link in the footer at the bottom of the page in your browser, + enter your email address and password into the spaces provided, and + click + <SPAN CLASS="QUOTE" >"Login"</SPAN >. - </P + </P ></LI ></OL ><P ->You are now logged in. Bugzilla uses cookies for authentication - so, unless your IP address changes, you should not have to log in - again.</P +>You are now logged in. Bugzilla uses cookies to remember you are + logged in so, unless you have cookies disabled or your IP address changes, + you should not have to log in again.</P ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="bug_page" ></A ->3.1.2. Anatomy of a Bug</H2 +>3.2. Anatomy of a Bug</H1 ><P >The core of Bugzilla is the screen which displays a particular - bug. It's a good place to explain some Bugzilla concepts. - <A + bug. It's a good place to explain some Bugzilla concepts. + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1" TARGET="_top" -> Bug 1 on Landfill</A +> Bug 1 on Landfill</A > - 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.</P + 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.</P ><P ></P ><OL TYPE="1" ><LI ><P -> <EM +> <EM >Product and Component</EM >: - Bugs are divided up by Product and Component, with a Product - having one or more Components in it. For example, - bugzilla.mozilla.org's "Bugzilla" Product is composed of several - Components: - <P + Bugs are divided up by Product and Component, with a Product + having one or more Components in it. For example, + bugzilla.mozilla.org's "Bugzilla" Product is composed of several + Components: + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <EM +> <EM >Administration:</EM > - Administration of a Bugzilla installation.</TD + Administration of a Bugzilla installation.</TD ></TR ><TR ><TD -> <EM +> <EM >Bugzilla-General:</EM > - Anything that doesn't fit in the other components, or spans - multiple components.</TD + Anything that doesn't fit in the other components, or spans + multiple components.</TD ></TR ><TR ><TD -> <EM +> <EM >Creating/Changing Bugs:</EM > - Creating, changing, and viewing bugs.</TD + Creating, changing, and viewing bugs.</TD ></TR ><TR ><TD -> <EM +> <EM >Documentation:</EM > - The Bugzilla documentation, including The Bugzilla Guide.</TD + The Bugzilla documentation, including The Bugzilla Guide.</TD ></TR ><TR ><TD -> <EM +> <EM >Email:</EM > - Anything to do with email sent by Bugzilla.</TD + Anything to do with email sent by Bugzilla.</TD ></TR ><TR ><TD -> <EM +> <EM >Installation:</EM > - The installation process of Bugzilla.</TD + The installation process of Bugzilla.</TD ></TR ><TR ><TD -> <EM +> <EM >Query/Buglist:</EM > - Anything to do with searching for bugs and viewing the - buglists.</TD + Anything to do with searching for bugs and viewing the + buglists.</TD ></TR ><TR ><TD -> <EM +> <EM >Reporting/Charting:</EM > - Getting reports from Bugzilla.</TD + Getting reports from Bugzilla.</TD ></TR ><TR ><TD -> <EM +> <EM >User Accounts:</EM > - Anything about managing a user account from the user's perspective. - Saved queries, creating accounts, changing passwords, logging in, - etc.</TD + Anything about managing a user account from the user's perspective. + Saved queries, creating accounts, changing passwords, logging in, + etc.</TD ></TR ><TR ><TD -> <EM +> <EM >User Interface:</EM > - General issues having to do with the user interface cosmetics (not - functionality) including cosmetic issues, HTML templates, - etc.</TD + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, + etc.</TD ></TR ></TBODY ></TABLE ><P ></P > - </P + </P ></LI ><LI ><P -> <EM +> <EM >Status and Resolution:</EM > - 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.</P + 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.</P ></LI ><LI ><P -> <EM +> <EM >Assigned To:</EM > - The person responsible for fixing the bug.</P + The person responsible for fixing the bug.</P ></LI ><LI ><P -> <EM +> <EM >*URL:</EM > - A URL associated with the bug, if any.</P + A URL associated with the bug, if any.</P ></LI ><LI ><P -> <EM +> <EM >Summary:</EM > - A one-sentence summary of the problem.</P + A one-sentence summary of the problem.</P ></LI ><LI ><P -> <EM +> <EM >*Status Whiteboard:</EM > - (a.k.a. Whiteboard) A free-form text area for adding short notes - and tags to a bug.</P + (a.k.a. Whiteboard) A free-form text area for adding short notes + and tags to a bug.</P ></LI ><LI ><P -> <EM +> <EM >*Keywords:</EM > - The administrator can define keywords which you can use to tag and - categorise bugs - e.g. The Mozilla Project has keywords like crash - and regression.</P + The administrator can define keywords which you can use to tag and + categorise bugs - e.g. The Mozilla Project has keywords like crash + and regression.</P ></LI ><LI ><P -> <EM +> <EM >Platform and OS:</EM > - These indicate the computing environment where the bug was - found.</P + These indicate the computing environment where the bug was + found.</P ></LI ><LI ><P -> <EM +> <EM >Version:</EM > - The "Version" field is usually used for versions of a product which - have been released, and is set to indicate which versions of a - Component have the particular problem the bug report is - about.</P + The "Version" field is usually used for versions of a product which + have been released, and is set to indicate which versions of a + Component have the particular problem the bug report is + about.</P ></LI ><LI ><P -> <EM +> <EM >Priority:</EM > - The bug assignee uses this field to prioritise his or her bugs. - It's a good idea not to change this on other people's bugs.</P + The bug assignee uses this field to prioritise his or her bugs. + It's a good idea not to change this on other people's bugs.</P ></LI ><LI ><P -> <EM +> <EM >Severity:</EM > - This indicates how severe the problem is - from blocker - ("application unusable") to trivial ("minor cosmetic issue"). You - can also use this field to indicate whether a bug is an enhancement - request.</P + This indicates how severe the problem is - from blocker + ("application unusable") to trivial ("minor cosmetic issue"). You + can also use this field to indicate whether a bug is an enhancement + request.</P ></LI ><LI ><P -> <EM +> <EM >*Target:</EM > - (a.k.a. Target Milestone) A future version by which the bug is to - be fixed. e.g. The Bugzilla Project's milestones for future - Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not - restricted to numbers, thought - you can use any text strings, such - as dates.</P + (a.k.a. Target Milestone) A future version by which the bug is to + be fixed. e.g. The Bugzilla Project's milestones for future + Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not + restricted to numbers, thought - you can use any text strings, such + as dates.</P ></LI ><LI ><P -> <EM +> <EM >Reporter:</EM > - The person who filed the bug.</P + The person who filed the bug.</P ></LI ><LI ><P -> <EM +> <EM >CC list:</EM > - A list of people who get mail when the bug changes.</P + A list of people who get mail when the bug changes.</P ></LI ><LI ><P -> <EM +> <EM >Attachments:</EM > - You can attach files (e.g. testcases or patches) to bugs. If there - are any attachments, they are listed in this section.</P + You can attach files (e.g. testcases or patches) to bugs. If there + are any attachments, they are listed in this section.</P ></LI ><LI ><P -> <EM +> <EM >*Dependencies:</EM > - If this bug cannot be fixed unless other bugs are fixed (depends - on), or this bug stops other bugs being fixed (blocks), their - numbers are recorded here.</P + If this bug cannot be fixed unless other bugs are fixed (depends + on), or this bug stops other bugs being fixed (blocks), their + numbers are recorded here.</P ></LI ><LI ><P -> <EM +> <EM >*Votes:</EM > - Whether this bug has any votes.</P + Whether this bug has any votes.</P ></LI ><LI ><P -> <EM +> <EM >Additional Comments:</EM > - You can add your two cents to the bug discussion here, if you have - something worthwhile to say.</P + You can add your two cents to the bug discussion here, if you have + something worthwhile to say.</P ></LI ></OL ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="query" ></A ->3.1.3. Searching for Bugs</H2 +>3.3. Searching for Bugs</H1 ><P >The Bugzilla Search page is is the interface where you can find - any bug report, comment, or patch currently in the Bugzilla system. You - can play with it here: - <A + any bug report, comment, or patch currently in the Bugzilla system. You + can play with it here: + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi" TARGET="_top" >http://landfill.bugzilla.org/bugzilla-tip/query.cgi</A >.</P ><P >The Search page has controls for selecting different possible - values for all of the fields in a bug, as described above. For some - fields, multiple values can be selected. In those cases, Bugzilla - returns bugs where the content of the field matches one of the selected - values. If none is selected, then the field can take any value.</P + values for all of the fields in a bug, as described above. For some + fields, multiple values can be selected. In those cases, Bugzilla + returns bugs where the content of the field matches any one of the selected + values. If none is selected, then the field can take any value.</P ><P ->Once you've defined a search, you can either run it, or save it - as a Remembered Query, which can optionally appear in the footer of - your pages.</P +>Once you've run a search, you can save it as a Saved Search, which + appears in the page footer.</P ><P ->Highly advanced querying is done using Boolean Charts.</P +>Highly advanced querying is done using Boolean Charts. See the + Boolean Charts help link on the Search page for more information.</P ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="list" ></A ->3.1.4. Bug Lists</H2 +>3.4. Bug Lists</H1 ><P >If you run a search, a list of matching bugs will be returned. - The default search is to return all open bugs on the system - don't try - running this search on a Bugzilla installation with a lot of - bugs!</P + </P ><P >The format of the list is configurable. For example, it can be - sorted by clicking the column headings. Other useful features can be - accessed using the links at the bottom of the list: - <P + sorted by clicking the column headings. Other useful features can be + accessed using the links at the bottom of the list: + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <EM +> <EM >Long Format:</EM > - this gives you a large page with a non-editable summary of the fields - of each bug.</TD + this gives you a large page with a non-editable summary of the fields + of each bug.</TD ></TR ><TR ><TD -> <EM +> <EM >Change Columns:</EM > - change the bug attributes which appear in the list.</TD + change the bug attributes which appear in the list.</TD ></TR ><TR ><TD -> <EM +> <EM >Change several bugs at once:</EM > - If your account is sufficiently empowered, you can make the same - change to all the bugs in the list - for example, changing their - owner.</TD + If your account is sufficiently empowered, you can make the same + change to all the bugs in the list - for example, changing their + owner.</TD ></TR ><TR ><TD -> <EM +> <EM >Send mail to bug owners:</EM > - Sends mail to the owners of all bugs on the list.</TD + Sends mail to the owners of all bugs on the list.</TD ></TR ><TR ><TD -> <EM +> <EM >Edit this query:</EM > - 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.</TD + 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.</TD ></TR ></TBODY ></TABLE ><P ></P > - </P + </P ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="bugreports" ></A ->3.1.5. Filing Bugs</H2 +>3.5. Filing Bugs</H1 ><P >Years of bug writing experience has been distilled for your - reading pleasure into the - <A + reading pleasure into the + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html" TARGET="_top" -> Bug Writing Guidelines</A +> Bug Writing Guidelines</A >. - While some of the advice is Mozilla-specific, the basic principles of - reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the - Hardware Platform, and Operating System you were using at the time of - the failure go a long way toward ensuring accurate, responsible fixes - for the bug that bit you.</P + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you.</P ><P >The procedure for filing a test bug is as follows:</P ><P @@ -1843,18 +1638,18 @@ TYPE="1" ><LI ><P >Go to - <A + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/" TARGET="_top" -> Landfill</A +> Landfill</A > - in your browser and click - <A + in your browser and click + <A HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi" TARGET="_top" -> Enter a new bug report</A +> Enter a new bug report</A >. - </P + </P ></LI ><LI ><P @@ -1863,8 +1658,8 @@ TARGET="_top" ><LI ><P >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.</P + guesses, based upon your browser, for the "Platform" and "OS" + drop-down boxes. If they are wrong, change them.</P ></LI ><LI ><P @@ -1874,18 +1669,18 @@ TARGET="_top" ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="patchviewer" ></A ->3.1.6. Patch Viewer</H2 +>3.6. Patch Viewer</H1 ><P >Viewing and reviewing patches in Bugzilla is often difficult due to - lack of context, improper format and the inherent readability issues that - raw patches present. Patch Viewer is an enhancement to Bugzilla designed - to fix that by offering increased context, linking to sections, and - integrating with Bonsai, LXR and CVS.</P + lack of context, improper format and the inherent readability issues that + raw patches present. Patch Viewer is an enhancement to Bugzilla designed + to fix that by offering increased context, linking to sections, and + integrating with Bonsai, LXR and CVS.</P ><P >Patch viewer allows you to:</P ><P @@ -1896,7 +1691,7 @@ BORDER="0" ><TR ><TD >View patches in color, with side-by-side view rather than trying - to interpret the contents of the patch.</TD + to interpret the contents of the patch.</TD ></TR ><TR ><TD @@ -1909,22 +1704,22 @@ BORDER="0" ><TR ><TD >Collapse and expand sections of a patch for easy - reading.</TD + reading.</TD ></TR ><TR ><TD >Link to a particular section of a patch for discussion or - review</TD + review</TD ></TR ><TR ><TD >Go to Bonsai or LXR to see more context, blame, and - cross-references for the part of the patch you are looking at</TD + cross-references for the part of the patch you are looking at</TD ></TR ><TR ><TD >Create a rawtext unified format diff out of any patch, no - matter what format it came from</TD + matter what format it came from</TD ></TR ></TBODY ></TABLE @@ -1932,111 +1727,110 @@ BORDER="0" ></P ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_view" ></A ->3.1.6.1. Viewing Patches in Patch Viewer</H3 +>3.6.1. Viewing Patches in Patch Viewer</H2 ><P >The main way to view a patch in patch viewer is to click on the - "Diff" link next to a patch in the Attachments list on a bug. You may - also do this within the edit window by clicking the "View Attachment As - Diff" button in the Edit Attachment screen.</P + "Diff" link next to a patch in the Attachments list on a bug. You may + also do this within the edit window by clicking the "View Attachment As + Diff" button in the Edit Attachment screen.</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_diff" ></A ->3.1.6.2. Seeing the Difference Between Two Patches</H3 +>3.6.2. Seeing the Difference Between Two Patches</H2 ><P >To see the difference between two patches, you must first view the - newer patch in Patch Viewer. Then select the older patch from the - dropdown at the top of the page ("Differences between [dropdown] and - this patch") and click the "Diff" button. This will show you what - is new or changed in the newer patch.</P + newer patch in Patch Viewer. Then select the older patch from the + dropdown at the top of the page ("Differences between [dropdown] and + this patch") and click the "Diff" button. This will show you what + is new or changed in the newer patch.</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_context" ></A ->3.1.6.3. Getting More Context in a Patch</H3 +>3.6.3. Getting More Context in a Patch</H2 ><P >To get more context in a patch, you put a number in the textbox at - the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. - This will give you that many lines of context before and after each - change. Alternatively, you can click on the "File" link there and it - will show each change in the full context of the file. This feature only - works against files that were diffed using "cvs diff".</P + the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. + This will give you that many lines of context before and after each + change. Alternatively, you can click on the "File" link there and it + will show each change in the full context of the file. This feature only + works against files that were diffed using "cvs diff".</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_collapse" ></A ->3.1.6.4. Collapsing and Expanding Sections of a Patch</H3 +>3.6.4. Collapsing and Expanding Sections of a Patch</H2 ><P >To view only a certain set of files in a patch (for example, if a - patch is absolutely huge and you want to only review part of it at a - time), you can click the "(+)" and "(-)" links next to each file (to - expand it or collapse it). If you want to collapse all files or expand - all files, you can click the "Collapse All" and "Expand All" links at the - top of the page.</P + patch is absolutely huge and you want to only review part of it at a + time), you can click the "(+)" and "(-)" links next to each file (to + expand it or collapse it). If you want to collapse all files or expand + all files, you can click the "Collapse All" and "Expand All" links at the + top of the page.</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_link" ></A ->3.1.6.5. Linking to a Section of a Patch</H3 +>3.6.5. Linking to a Section of a Patch</H2 ><P >To link to a section of a patch (for example, if you want to be - able to give someone a URL to show them which part you are talking - about) you simply click the "Link Here" link on the section header. The - resulting URL can be copied and used in discussion. (Copy Link - Location in Mozilla works as well.)</P + able to give someone a URL to show them which part you are talking + about) you simply click the "Link Here" link on the section header. The + resulting URL can be copied and used in discussion. (Copy Link + Location in Mozilla works as well.)</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_bonsai_lxr" ></A ->3.1.6.6. Going to Bonsai and LXR</H3 +>3.6.6. Going to Bonsai and LXR</H2 ><P >To go to Bonsai to get blame for the lines you are interested in, - you can click the "Lines XX-YY" link on the section header you are - interested in. This works even if the patch is against an old - version of the file, since Bonsai stores all versions of the file.</P + you can click the "Lines XX-YY" link on the section header you are + interested in. This works even if the patch is against an old + version of the file, since Bonsai stores all versions of the file.</P ><P >To go to LXR, you click on the filename on the file header - (unfortunately, since LXR only does the most recent version, line - numbers are likely to rot).</P + (unfortunately, since LXR only does the most recent version, line + numbers are likely to rot).</P ></DIV ><DIV CLASS="section" -><HR><H3 +><HR><H2 CLASS="section" ><A NAME="patchviewer_unified_diff" ></A ->3.1.6.7. Creating a Unified Diff</H3 +>3.6.7. Creating a Unified Diff</H2 ><P >If the patch is not in a format that you like, you can turn it - into a unified diff format by clicking the "Raw Unified" link at the top - of the page.</P -></DIV + into a unified diff format by clicking the "Raw Unified" link at the top + of the page.</P ></DIV ></DIV ><DIV @@ -2046,7 +1840,7 @@ CLASS="section" ><A NAME="hintsandtips" ></A ->3.2. Hints and Tips</H1 +>3.7. Hints and Tips</H1 ><P >This section distills some Bugzilla tips and best practices that have been developed.</P @@ -2055,15 +1849,15 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN407" +NAME="AEN358" ></A ->3.2.1. Autolinkification</H2 +>3.7.1. Autolinkification</H2 ><P ->Bugzilla comments are plain text - so posting HTML will result - in literal HTML tags rather than being interpreted by a browser. +>Bugzilla comments are plain text - so typing <U> will + produce less-than, U, greater-than rather than underlined text. 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" will be turned into a link: <A HREF="http://www.bugzilla.org" TARGET="_top" @@ -2081,6 +1875,10 @@ BORDER="0" ></TR ><TR ><TD +>comment 7</TD +></TR +><TR +><TD >bug 23456, comment 53</TD ></TR ><TR @@ -2122,7 +1920,7 @@ CLASS="section" ><A NAME="quicksearch" ></A ->3.2.2. Quicksearch</H2 +>3.7.2. Quicksearch</H2 ><P >Quicksearch is a single-text-box query tool which uses metacharacters to indicate what is to be searched. For example, typing @@ -2155,7 +1953,7 @@ CLASS="section" ><A NAME="commenting" ></A ->3.2.3. Comments</H2 +>3.7.3. Comments</H2 ><P >If you are changing the fields on a bug, only comment if either you have something pertinent to say, or Bugzilla requires it. @@ -2168,7 +1966,7 @@ NAME="commenting" </P ><P > 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 + if you do it out of habit, but full mail/news-style four line ASCII art creations are not. </P ></DIV @@ -2179,7 +1977,7 @@ CLASS="section" ><A NAME="attachments" ></A ->3.2.4. Attachments</H2 +>3.7.4. Attachments</H2 ><P > Use attachments, rather than comments, for large chunks of ASCII data, such as trace, debugging output files, or log files. That way, it doesn't @@ -2203,9 +2001,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN436" +NAME="AEN388" ></A ->3.2.5. Filing Bugs</H2 +>3.7.5. Filing Bugs</H2 ><P >Try to make sure that everything said in the summary is also said in the first comment. Summaries are often updated and this will @@ -2231,11 +2029,11 @@ CLASS="section" ><A NAME="userpreferences" ></A ->3.3. User Preferences</H1 +>3.8. User Preferences</H1 ><P >Once you have logged in, you can customise various aspects of Bugzilla via the "Edit prefs" link in the page footer. - The preferences are split into four tabs:</P + The preferences are split into three tabs:</P ><DIV CLASS="section" ><HR><H2 @@ -2243,7 +2041,7 @@ CLASS="section" ><A NAME="accountsettings" ></A ->3.3.1. Account Settings</H2 +>3.8.1. Account Settings</H2 ><P >On this tab, you can change your basic account information, including your password, email address and real name. For security @@ -2268,13 +2066,19 @@ CLASS="section" ><A NAME="emailsettings" ></A ->3.3.2. Email Settings</H2 +>3.8.2. Email Settings</H2 ><P >On this tab you can reduce or increase the amount of email sent you from Bugzilla, opting in our out depending on your relationship to - 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.)</P + the bug and the change that was made to it. + </P +><P +> You can also do further filtering on the client side by + using the X-Bugzilla-Reason mail header which Bugzilla + adds to all bugmail. This tells you what relationship you have to the + bug in question, + and can be any of Owner, Reporter, QAcontact, CClist, Voter and + WatchingComponent.</P ><P >By entering user email names, delineated by commas, into the "Users to watch" text entry box you can receive a copy of all the @@ -2315,29 +2119,28 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="footersettings" +NAME="permissionsettings" ></A ->3.3.3. Page Footer</H2 +>3.8.3. Permissions</H2 ><P ->On the Search page, you can store queries in Bugzilla, so if you - regularly run a particular query it is just a drop-down menu away. - Once you have a stored query, you can come - here to request that it also be displayed in your page footer.</P +>This is a purely informative page which outlines your current + permissions on this installation of Bugzilla - what product groups you + are in, and whether you can edit bugs or perform various administration + functions.</P +></DIV ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A -NAME="permissionsettings" +NAME="reporting" ></A ->3.3.4. Permissions</H2 +>3.9. Reports</H1 ><P ->This is a purely informative page which outlines your current - permissions on this installation of Bugzilla - what product groups you - are in, and whether you can edit bugs or perform various administration - functions.</P -></DIV +><EM +>To be written</EM +></P ></DIV ></DIV ><DIV @@ -2366,7 +2169,7 @@ CLASS="productname" that make it harder. We have tried to collect that information in <A HREF="#os-specific" ->Section 4.3</A +>Section 4.4</A >, so be sure to check out that section before you start your installation. </P @@ -2396,7 +2199,7 @@ VALIGN="TOP" to install Bugzilla on Windows, be sure to see <A HREF="#os-win32" ->Section 4.3.1</A +>Section 4.4.1</A >. </P ></TD @@ -2443,6 +2246,10 @@ VALIGN="TOP" with administrative access to install it for you. </P ><P +> You are strongly recommended to make a backup of your system + before installing Bugzilla and at regular intervals thereafter. + </P +><P >The listing below is a basic step-by-step list. More information can be found in the sections below. Minimum versions will be included in parenthesis where appropriate. @@ -2454,15 +2261,6 @@ TYPE="1" ><LI ><P ><A -HREF="#install-mysql" ->Install MySQL</A -> - (3.23.41) - </P -></LI -><LI -><P -><A HREF="#install-perl" >Install Perl</A > @@ -2472,9 +2270,10 @@ HREF="#install-perl" ><LI ><P ><A -HREF="#install-perlmodules" ->Install Perl Modules</A +HREF="#install-mysql" +>Install MySQL</A > + (3.23.41) </P ></LI ><LI @@ -2496,6 +2295,14 @@ HREF="#install-bzfiles" ><LI ><P ><A +HREF="#install-perlmodules" +>Install Perl Modules</A +> + </P +></LI +><LI +><P +><A HREF="#install-setupdatabase" >Setup the MySQL Database</A > @@ -2508,9 +2315,31 @@ CLASS="section" ><HR><H2 CLASS="section" ><A +NAME="install-perl" +></A +>4.1.1. Perl</H2 +><P +>Any machine that doesn't have Perl on it is a sad machine indeed. + Perl can be got in source form from <A +HREF="http://www.perl.com" +TARGET="_top" +>http://www.perl.com</A +>. + There are also binary versions available for many platforms, most of which + are linked to from perl.com. + Although Bugzilla runs with perl 5.6, + 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.8.</P +></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A NAME="install-mysql" ></A ->4.1.1. MySQL</H2 +>4.1.2. MySQL</H2 ><P >Visit the MySQL homepage at <A @@ -2615,31 +2444,327 @@ CLASS="option" > option as mentioned in <A HREF="#security-mysql" ->Section 5.6.2</A +>Section 4.5.2</A > for the added security. </P +><DIV +CLASS="section" +><HR><H3 +CLASS="section" +><A +NAME="install-setupdatabase" +></A +>4.1.2.1. Configuring MySQL</H3 +><P +>This first thing you'll want to do is make sure you've given the + <SPAN +CLASS="QUOTE" +>"root"</SPAN +> user a password as suggested in + <A +HREF="#security-mysql" +>Section 4.5.2</A +>. For clarity, these instructions will + assume that your MySQL user for Bugzilla will be <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +>, + the database will be called <SPAN +CLASS="QUOTE" +>"bugs_db"</SPAN +> and the password for + the <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> user is <SPAN +CLASS="QUOTE" +>"bugs_password"</SPAN +>. You + should, of course, substitute the values you intend to use for your site. + </P +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Most people use <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> for both the user and + database name. + </P +></TD +></TR +></TABLE +></DIV +><P +>Next, we use an SQL <B +CLASS="command" +>GRANT</B +> command to create a + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + user, and grant sufficient permissions for checksetup.pl, which we'll + use later, to work its magic. This also restricts the + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + user to operations within a database called + <SPAN +CLASS="QUOTE" +>"bugs_db"</SPAN +>, and only allows the account to connect from + <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +>. + Modify it to reflect your setup if you will be connecting from + another machine or as a different user.</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="screen" +> <TT +CLASS="prompt" +>mysql></TT +> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, + DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost + IDENTIFIED BY 'bugs_password'; + <TT +CLASS="prompt" +>mysql></TT +> FLUSH PRIVILEGES; + </PRE +></FONT +></TD +></TR +></TABLE +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>If you are using MySQL 4, the bugs user also needs to be granted + the <TT +CLASS="computeroutput" +>LOCK TABLES</TT +> and + <TT +CLASS="computeroutput" +>CREATE TEMPORARY TABLES</TT +> permissions. + </P +></TD +></TR +></TABLE +></DIV +></DIV ></DIV ><DIV CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-perl" +NAME="install-webserver" ></A ->4.1.2. Perl</H2 +>4.1.3. HTTP Server</H2 ><P ->Any machine that doesn't have Perl on it is a sad machine indeed. - Perl can be got in source form from <A -HREF="http://www.perl.com" +>You have freedom of choice here, pretty much any web server that + is capable of running <A +HREF="#gloss-cgi" +><I +CLASS="glossterm" +>CGI</I +></A +> + scripts will work. <A +HREF="#http" +>Section 4.2</A +> has more information about + configuring web servers to work with Bugzilla. + </P +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>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 by filing a bug in <A +HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" TARGET="_top" ->http://www.perl.com</A +>Bugzilla Documentation</A >. - There are also binary versions available for many platforms, most of which - are linked to from perl.com. - Although Bugzilla runs with perl 5.6, - 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.8.</P + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="install-bzfiles" +></A +>4.1.4. Bugzilla</H2 +><P +>You should untar the Bugzilla files into a directory that you're + willing to make writable by the default web server user (probably + <SPAN +CLASS="QUOTE" +>"nobody"</SPAN +>). + You may decide to put the files in the main web space for your + web server or perhaps in + <TT +CLASS="filename" +>/usr/local</TT +> + with a symbolic link in the web space that points to the Bugzilla + directory.</P +><DIV +CLASS="tip" +><P +></P +><TABLE +CLASS="tip" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/tip.gif" +HSPACE="5" +ALT="Tip"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>If you symlink the bugzilla directory into your Apache's HTML + hierarchy, you may receive + <SPAN +CLASS="errorname" +>Forbidden</SPAN +> + errors unless you add the + <SPAN +CLASS="QUOTE" +>"FollowSymLinks"</SPAN +> + directive to the <Directory> entry for the HTML root + in httpd.conf.</P +></TD +></TR +></TABLE +></DIV +><P +>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 + <TT +CLASS="filename" +>checksetup.pl</TT +> + script, which locks down your installation.</P +><DIV +CLASS="caution" +><P +></P +><TABLE +CLASS="caution" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/caution.gif" +HSPACE="5" +ALT="Caution"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>The default Bugzilla distribution is not designed to be placed + in a <TT +CLASS="filename" +>cgi-bin</TT +> directory (this + includes any directory which is configured using the + <TT +CLASS="option" +>ScriptAlias</TT +> directive of Apache). + </P +></TD +></TR +></TABLE +></DIV ></DIV ><DIV CLASS="section" @@ -2648,7 +2773,7 @@ CLASS="section" ><A NAME="install-perlmodules" ></A ->4.1.3. Perl Modules</H2 +>4.1.5. Perl Modules</H2 ><P >Perl modules can be found using <A @@ -2676,7 +2801,7 @@ HREF="#install-perlmodules-cpan" > for CPAN and <A HREF="#win32-perlmodules" ->Section 4.3.1.2</A +>Section 4.4.1.2</A > for PPM. </P ><DIV @@ -2802,7 +2927,7 @@ BORDER="0" ALT="(2)"></A ></DT ><DD ->The process of untaring the module as defined in +>The process of untarring the module as defined in <A HREF="#cpan-moduletar" ><A @@ -3053,7 +3178,7 @@ CLASS="section" ><A NAME="install-modules-bundle-bugzilla" ></A ->4.1.3.1. Bundle::Bugzilla</H3 +>4.1.5.1. Bundle::Bugzilla</H3 ><P >If you are running at least perl 5.6.1, you can save yourself a lot of time by using Bundle::Bugzilla. This bundle contains every module @@ -3132,7 +3257,7 @@ CLASS="section" ><A NAME="install-modules-appconfig" ></A ->4.1.3.2. AppConfig (1.52)</H3 +>4.1.5.2. AppConfig (1.52)</H3 ><P >Dependency for Template Toolkit. We probably don't need to specifically check for it anymore. @@ -3145,7 +3270,7 @@ CLASS="section" ><A NAME="install-modules-cgi" ></A ->4.1.3.3. CGI (2.88)</H3 +>4.1.5.3. CGI (2.88)</H3 ><P >The CGI module parses form elements and cookies and does many other usefule things. It come as a part of recent perl distributions, but @@ -3178,7 +3303,7 @@ CLASS="section" ><A NAME="install-modules-data-dumper" ></A ->4.1.3.4. Data::Dumper (any)</H3 +>4.1.5.4. Data::Dumper (any)</H3 ><P >The Data::Dumper module provides data structure persistence for Perl (similar to Java's serialization). It comes with later @@ -3212,7 +3337,7 @@ CLASS="section" ><A NAME="install-modules-date-format" ></A ->4.1.3.5. TimeDate modules (2.21)</H3 +>4.1.5.5. TimeDate modules (2.21)</H3 ><P >Many of the more common date/time/calendar related Perl modules have been grouped into a bundle similar to the MySQL modules bundle. @@ -3247,7 +3372,7 @@ CLASS="section" ><A NAME="install-modules-dbi" ></A ->4.1.3.6. DBI (1.32)</H3 +>4.1.5.6. DBI (1.32)</H3 ><P >The DBI module is a generic Perl module used the MySQL-related modules. As long as your Perl installation was done @@ -3281,7 +3406,7 @@ CLASS="section" ><A NAME="install-modules-dbd-mysql" ></A ->4.1.3.7. MySQL-related modules</H3 +>4.1.5.7. MySQL-related modules</H3 ><P >The Perl/MySQL interface requires a few mutually-dependent Perl modules. These modules are grouped together into the the @@ -3326,7 +3451,7 @@ CLASS="section" ><A NAME="install-file-spec" ></A ->4.1.3.8. File::Spec (0.82)</H3 +>4.1.5.8. File::Spec (0.82)</H3 ><P >File::Spec is a perl module that allows file operations, such as generating full path names, to work cross platform. @@ -3358,7 +3483,7 @@ CLASS="section" ><A NAME="install-modules-file-temp" ></A ->4.1.3.9. File::Temp (any)</H3 +>4.1.5.9. File::Temp (any)</H3 ><P >File::Temp is used to generate a temporary filename that is guaranteed to be unique. It comes as a standard part of perl @@ -3390,7 +3515,7 @@ CLASS="section" ><A NAME="install-modules-template" ></A ->4.1.3.10. Template Toolkit (2.08)</H3 +>4.1.5.10. Template Toolkit (2.08)</H3 ><P >When you install Template Toolkit, you'll get asked various questions about features to enable. The defaults are fine, except @@ -3424,7 +3549,7 @@ CLASS="section" ><A NAME="install-modules-text-wrap" ></A ->4.1.3.11. Text::Wrap (2001.0131)</H3 +>4.1.5.11. Text::Wrap (2001.0131)</H3 ><P >Text::Wrap is designed to proved intelligent text wrapping. </P @@ -3450,7 +3575,7 @@ CLASS="section" ><A NAME="install-modules-gd" ></A ->4.1.3.12. GD (1.20) [optional]</H3 +>4.1.5.12. GD (1.20) [optional]</H3 ><P >The GD library was written by Thomas Boutell a long while ago to programmatically generate images in C. Since then it's become the @@ -3560,7 +3685,7 @@ CLASS="section" ><A NAME="install-modules-chart-base" ></A ->4.1.3.13. Chart::Base (0.99c) [optional]</H3 +>4.1.5.13. Chart::Base (0.99c) [optional]</H3 ><P >The Chart module provides Bugzilla with on-the-fly charting abilities. It can be installed in the usual fashion after it has been @@ -3589,7 +3714,7 @@ CLASS="section" ><A NAME="install-modules-xml-parser" ></A ->4.1.3.14. XML::Parser (any) [Optional]</H3 +>4.1.5.14. XML::Parser (any) [Optional]</H3 ><P >XML::Parser is used by the <TT CLASS="filename" @@ -3624,7 +3749,7 @@ CLASS="section" ><A NAME="install-modules-gd-graph" ></A ->4.1.3.15. GD::Graph (any) [Optional]</H3 +>4.1.5.15. GD::Graph (any) [Optional]</H3 ><P >In addition to GD listed above, the reporting interface of Bugzilla needs to have the GD::Graph module installed. @@ -3656,7 +3781,7 @@ CLASS="section" ><A NAME="install-modules-gd-text-align" ></A ->4.1.3.16. GD::Text::Align (any) [Optional]</H3 +>4.1.5.16. GD::Text::Align (any) [Optional]</H3 ><P >GD::Text::Align, as the name implies, is used to draw aligned strings of text. It is needed by the reporting interface. @@ -3688,7 +3813,7 @@ CLASS="section" ><A NAME="install-modules-mime-parser" ></A ->4.1.3.17. MIME::Parser (any) [Optional]</H3 +>4.1.5.17. MIME::Parser (any) [Optional]</H3 ><P >MIME::Parser is only needed if you want to use the e-mail interface located in the <TT @@ -3723,7 +3848,7 @@ CLASS="section" ><A NAME="install-modules-patchreader" ></A ->4.1.3.18. PatchReader (0.9.1) [Optional]</H3 +>4.1.5.18. PatchReader (0.9.1) [Optional]</H3 ><P >PatchReader is only needed if you want to use Patch Viewer, a Bugzilla feature to format patches in a pretty HTML fashion. There are a @@ -3759,135 +3884,122 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-webserver" +NAME="AEN748" ></A ->4.1.4. HTTP Server</H2 +>4.1.6. <TT +CLASS="filename" +>checksetup.pl</TT +></H2 ><P ->You have freedom of choice here, pretty much any web server that - is capable of running <A -HREF="#gloss-cgi" -><I -CLASS="glossterm" ->CGI</I -></A +>Next, run the magic checksetup.pl script. + This is designed to make sure your perl modules are the correct + version and 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 + <TT +CLASS="filename" +>data</TT > - scripts will work. <A -HREF="#http" ->Section 4.4</A -> has more information about - configuring web servers to work with Bugzilla. + directory, and create all the MySQL tables. </P -><DIV -CLASS="note" -><P -></P ><TABLE -CLASS="note" -WIDTH="100%" BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" ><TR ><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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 by filing a bug in <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. - </P +><FONT +COLOR="#000000" +><PRE +CLASS="screen" +> <TT +CLASS="prompt" +>bash#</TT +> ./checksetup.pl + </PRE +></FONT ></TD ></TR ></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="install-bzfiles" -></A ->4.1.5. Bugzilla</H2 ><P ->You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <SPAN -CLASS="QUOTE" ->"nobody"</SPAN ->). - You may decide to put the files in the main web space for your - web server or perhaps in +> The first time you run it, it will create a file called <TT CLASS="filename" ->/usr/local</TT -> - with a symbolic link in the web space that points to the Bugzilla - directory.</P -><DIV -CLASS="tip" +>localconfig</TT +>.</P ><P +>This file contains a variety of settings you may need to tweak + including how Bugzilla should connect to the MySQL database.</P +><P +>The connection settings include: + <P ></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +><OL +TYPE="1" +><LI ><P ->If you symlink the bugzilla directory into your Apache's HTML - hierarchy, you may receive - <SPAN -CLASS="errorname" ->Forbidden</SPAN +>server's host: just use + <SPAN +CLASS="QUOTE" +>"localhost"</SPAN > - errors unless you add the - <SPAN + if the MySQL server is local</P +></LI +><LI +><P +>database name: + <SPAN CLASS="QUOTE" ->"FollowSymLinks"</SPAN +>"bugs_db"</SPAN > - directive to the <Directory> entry for the HTML root - in httpd.conf.</P -></TD -></TR -></TABLE -></DIV + if you're following these directions</P +></LI +><LI ><P ->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 +>MySQL username: + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + if you're following these directions</P +></LI +><LI +><P +>Password for the + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + MySQL account; (<SPAN +CLASS="QUOTE" +>"bugs_password"</SPAN +> above)</P +></LI +></OL +> + </P +><P +>Once you are happy with the settings, + <TT +CLASS="filename" +>su</TT +> to the user + your web server runs as, and re-run <TT CLASS="filename" >checksetup.pl</TT -> - script, which locks down your installation.</P +>. (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.</P ><DIV -CLASS="caution" +CLASS="note" ><P ></P ><TABLE -CLASS="caution" +CLASS="note" WIDTH="100%" BORDER="0" ><TR @@ -3896,31 +4008,16 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/caution.gif" +SRC="../images/note.gif" HSPACE="5" -ALT="Caution"></TD +ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->The default Bugzilla distribution is not designed to be placed - in a <TT -CLASS="filename" ->cgi-bin</TT -> directory (this - includes any directory which is configured using the - <TT -CLASS="option" ->ScriptAlias</TT -> directive of Apache). This will probably - change as part of - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659" -TARGET="_top" ->bug - 44659</A ->. - </P +>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.</P ></TD ></TR ></TABLE @@ -3931,97 +4028,113 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="install-setupdatabase" +NAME="AEN778" ></A ->4.1.6. Setting Up the MySQL Database</H2 -><P ->After you've gotten all the software installed and working you're - ready to start preparing the database for its life as the back end to - a high quality bug tracker.</P +>4.1.7. Configuring Bugzilla</H2 ><P ->This first thing you'll want to do is make sure you've given the - <SPAN -CLASS="QUOTE" ->"root"</SPAN -> user a password as suggested in - <A -HREF="#security-mysql" ->Section 5.6.2</A ->. For clarity, these instructions will - assume that your MySQL user for Bugzilla will be <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN ->, - the database will be called <SPAN -CLASS="QUOTE" ->"bugs_db"</SPAN -> and the password for - the <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> user is <SPAN -CLASS="QUOTE" ->"bugs_password"</SPAN ->. You - should, of course, substitute the values you intend to use for your site. +> 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 <A +HREF="#parameters" +>Section 5.1</A +>. </P +></DIV +></DIV ><DIV -CLASS="note" +CLASS="section" +><HR><H1 +CLASS="section" +><A +NAME="http" +></A +>4.2. HTTP Server Configuration</H1 ><P -></P +>The Bugzilla Team recommends Apache when using Bugzilla, however, any web server + that can be configured to run <A +HREF="#gloss-cgi" +><I +CLASS="glossterm" +>CGI</I +></A +> scripts + should be able to handle Bugzilla. No matter what web server you choose, but + especially if you choose something other than Apache, you should be sure to read + <A +HREF="#security-access" +>Section 4.5.4</A +>. + </P +><P +>The plan for this section is to eventually document the specifics of how to lock + down permissions on individual web servers. + </P +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="http-apache" +></A +>4.2.1. Apache <SPAN +CLASS="productname" +>httpd</SPAN +></H2 +><P +>You will have to make sure that Apache is properly + configured to run the Bugzilla CGI scripts. You also need to make sure + that the <TT +CLASS="filename" +>.htaccess</TT +> files created by + <B +CLASS="command" +>./checksetup.pl</B +> are allowed to override Apache's normal access + permissions or else important password information may be exposed to the + Internet. + </P +><P +>You need to configure Apache to run .cgi files outside the + <TT +CLASS="filename" +>cgi-bin</TT +> directory. + Open your + <TT +CLASS="filename" +>httpd.conf</TT +> file and make sure the + following line exists and is uncommented:</P ><TABLE -CLASS="note" -WIDTH="100%" BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" ><TR ><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Most people use <SPAN -CLASS="QUOTE" ->"bugs"</SPAN -> for both the user and - database name. - </P +><FONT +COLOR="#000000" +><PRE +CLASS="programlisting" +> AddHandler cgi-script .cgi + </PRE +></FONT ></TD ></TR ></TABLE -></DIV ><P ->Next, we use an SQL <B -CLASS="command" ->GRANT</B -> command to create a - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> - user, and grant sufficient permissions for checksetup.pl, which we'll - use later, to work its magic. This also restricts the - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN +>To allow <TT +CLASS="filename" +>.htaccess</TT +> files to override + permissions and .cgi files to run in the Bugzilla directory, make sure + the following two lines are in a <TT +CLASS="computeroutput" +>Directory</TT > - user to operations within a database called - <SPAN -CLASS="QUOTE" ->"bugs_db"</SPAN ->, and only allows the account to connect from - <SPAN -CLASS="QUOTE" ->"localhost"</SPAN ->. - Modify it to reflect your setup if you will be connecting from - another machine or as a different user.</P + directive that applies to the Bugzilla directory on your system + (either the Bugzilla directory or one of its parents). + </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -4031,22 +4144,29 @@ WIDTH="100%" ><FONT COLOR="#000000" ><PRE -CLASS="screen" -> <TT -CLASS="prompt" ->mysql></TT -> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, - DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost - IDENTIFIED BY 'bugs_password'; -<TT -CLASS="prompt" ->mysql></TT -> FLUSH PRIVILEGES; - </PRE +CLASS="programlisting" +> Options +ExecCGI +AllowOverride Limit + </PRE ></FONT ></TD ></TR ></TABLE +><P +>You should modify the <DirectoryIndex> parameter for + the Apache virtual host running your Bugzilla installation to + allow <TT +CLASS="filename" +>index.cgi</TT +> as the index page for a + directory, as well as the usual <TT +CLASS="filename" +>index.html</TT +>, + <TT +CLASS="filename" +>index.htm</TT +>, and so forth. </P ><DIV CLASS="note" ><P @@ -4068,16 +4188,15 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->If you are using MySQL 4, the bugs user also needs to be granted - the <TT -CLASS="computeroutput" ->LOCK TABLES</TT -> and - <TT -CLASS="computeroutput" ->CREATE TEMPORARY TABLES</TT -> permissions. - </P +>For more information on Apache and its directives, see the + glossary entry on <A +HREF="#gloss-apache" +><I +CLASS="glossterm" +>Apache</I +></A +>. + </P ></TD ></TR ></TABLE @@ -4088,30 +4207,104 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN795" +NAME="http-iis" ></A ->4.1.7. <TT -CLASS="filename" ->checksetup.pl</TT +>4.2.2. Microsoft <SPAN +CLASS="productname" +>Internet Information Services</SPAN ></H2 ><P ->Next, run the magic checksetup.pl script. (Many thanks to +>If you need, or for some reason even want, to use Microsoft's + <SPAN +CLASS="productname" +>Internet Information Services</SPAN +> or + <SPAN +CLASS="productname" +>Personal Web Server</SPAN +> you should be able + to. You will need to configure them to know how to run CGI scripts, + however. This is described in Microsoft Knowledge Base article <A -HREF="mailto:holgerschurig@nikocity.de" +HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp" TARGET="_top" ->Holger Schurig</A -> - for writing this script!) - This script is designed to make sure your perl modules are the correct - version and 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 +>Q245225</A +> + for <SPAN +CLASS="productname" +>Internet Information Services</SPAN +> and + <A +HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp" +TARGET="_top" +>Q231998</A +> + for <SPAN +CLASS="productname" +>Personal Web Server</SPAN +>. + </P +><P +>Also, and this can't be stressed enough, make sure that files such as <TT CLASS="filename" +>localconfig</TT +> and your <TT +CLASS="filename" >data</TT > - directory, and create all the MySQL tables. + directory are secured as described in <A +HREF="#security-access" +>Section 4.5.4</A +>. + </P +></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="http-aol" +></A +>4.2.3. AOL Server</H2 +><P +>Ben FrantzDale reported success using AOL Server with Bugzilla. He + reported his experience and what appears below is based on that. + </P +><P +>AOL Server will have to be configured to run + <A +HREF="#gloss-cgi" +><I +CLASS="glossterm" +>CGI</I +></A +> scripts, please consult + the documentation that came with your server for more information on + how to do this. + </P +><P +>Because AOL Server doesn't support <TT +CLASS="filename" +>.htaccess</TT +> + files, you'll have to create a <A +HREF="#gloss-tcl" +><I +CLASS="glossterm" +>TCL</I +></A +> + script. You should create an <TT +CLASS="filename" +>aolserver/modules/tcl/filter.tcl</TT +> + file (the filename shouldn't matter) with the following contents (change + <TT +CLASS="computeroutput" +>/bugzilla/</TT +> to the web-based path to + your Bugzilla installation): </P ><TABLE BORDER="0" @@ -4122,88 +4315,66 @@ WIDTH="100%" ><FONT COLOR="#000000" ><PRE -CLASS="screen" -> <TT -CLASS="prompt" ->bash#</TT -> ./checksetup.pl +CLASS="programlisting" +> ns_register_filter preauth GET /bugzilla/localconfig filter_deny +ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny +ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny +ns_register_filter preauth GET /bugzilla/*.pl filter_deny +ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny +ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny +ns_register_filter preauth GET /bugzilla/data/* filter_deny +ns_register_filter preauth GET /bugzilla/template/* filter_deny + +proc filter_deny { why } { + ns_log Notice "filter_deny" + return "filter_return" +} </PRE ></FONT ></TD ></TR ></TABLE +><DIV +CLASS="warning" ><P -> The first time you run it, it will create a file called - <TT -CLASS="filename" ->localconfig</TT ->.</P -><P ->This file contains a variety of settings you may need to tweak - including how Bugzilla should connect to the MySQL database.</P -><P ->The connection settings include: - <P ></P -><OL -TYPE="1" -><LI -><P ->server's host: just use - <SPAN -CLASS="QUOTE" ->"localhost"</SPAN -> - if the MySQL server is local</P -></LI -><LI -><P ->database name: - <SPAN -CLASS="QUOTE" ->"bugs_db"</SPAN -> - if you're following these directions</P -></LI -><LI -><P ->MySQL username: - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> - if you're following these directions</P -></LI -><LI -><P ->Password for the - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> - MySQL account; (<SPAN -CLASS="QUOTE" ->"bugs_password"</SPAN -> above)</P -></LI -></OL -> - </P +><TABLE +CLASS="warning" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" ><P ->Once you are happy with the settings, - <TT -CLASS="filename" ->su</TT -> to the user - your web server runs as, and re-run - <TT +>This probably doesn't account for all possible editor backup + files so you may wish to add some additional variations of + <TT CLASS="filename" ->checksetup.pl</TT ->. (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.</P +>localconfig</TT +>. For more information, see + <A +HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383" +TARGET="_top" +> bug 186383</A +> or <A +HREF="http://online.securityfocus.com/bid/6501" +TARGET="_top" +>Bugtraq ID 6501</A +>. + </P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="note" ><P @@ -4225,31 +4396,48 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->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.</P +>If you are using webdot from research.att.com (the default + configuration for the <TT +CLASS="option" +>webdotbase</TT +> paramater), you + will need to allow access to <TT +CLASS="filename" +>data/webdot/*.dot</TT +> + for the reasearch.att.com machine. + </P +><P +>If you are using a local installation of <A +HREF="http://www.graphviz.org" +TARGET="_top" +>GraphViz</A +>, you will need to allow + everybody to access <TT +CLASS="filename" +>*.png</TT +>, + <TT +CLASS="filename" +>*.gif</TT +>, <TT +CLASS="filename" +>*.jpg</TT +>, and + <TT +CLASS="filename" +>*.map</TT +> in the + <TT +CLASS="filename" +>data/webdot</TT +> directory. + </P ></TD ></TR ></TABLE ></DIV ></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="AEN826" -></A ->4.1.8. Configuring Bugzilla</H2 -><P -> You should run through the parameters on the Edit Parameters page - (link in the footer) and set them all to appropriate values. - They key parameters are documented in <A -HREF="#parameters" ->Section 5.1</A ->. - </P -></DIV ></DIV ><DIV CLASS="section" @@ -4258,15 +4446,15 @@ CLASS="section" ><A NAME="extraconfig" ></A ->4.2. Optional Additional Configuration</H1 +>4.3. Optional Additional Configuration</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN832" +NAME="AEN852" ></A ->4.2.1. Dependency Charts</H2 +>4.3.1. Dependency Charts</H2 ><P >As well as the text-based dependency graphs, Bugzilla also supports dependency graphing, using a package called 'dot'. @@ -4328,9 +4516,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN847" +NAME="AEN867" ></A ->4.2.2. Bug Graphs</H2 +>4.3.2. Bug Graphs</H2 ><P >As long as you installed the GD and Graph::Base Perl modules you might as well turn on the nifty Bugzilla bug reporting graphs.</P @@ -4387,9 +4575,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN860" +NAME="AEN880" ></A ->4.2.3. The Whining Cron</H2 +>4.3.3. The Whining Cron</H2 ><P >By now you have a fully functional Bugzilla, but what good are bugs if they're not annoying? To help make those bugs more annoying you @@ -4478,47 +4666,11 @@ CLASS="section" ><A NAME="bzldap" ></A ->4.2.4. LDAP Authentication</H2 -><DIV -CLASS="note" +>4.3.4. LDAP Authentication</H2 ><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->LDAP authentication has been rewritten for the 2.18 release of - Bugzilla. It no longer requires the Mozilla::LDAP module and now uses - Net::LDAP instead. This rewrite was part of a larger landing that - allowed for additional authentication schemes to be easily added - (<A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=180642" -TARGET="_top" ->bug - 180642</A ->). - </P -><P ->This patch originally landed in 21-Mar-2003 and was included - in the 2.17.4 development release. - </P -></TD -></TR -></TABLE -></DIV +>LDAP authentication is a module for Bugzilla's plugin + authentication architecture. + </P ><P > The existing authentication scheme for Bugzilla uses email addresses as the primary user ID, and a @@ -4728,26 +4880,26 @@ CLASS="section" ><A NAME="content-type" ></A ->4.2.5. Preventing untrusted Bugzilla content from executing malicious +>4.3.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</H2 ><P ->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 +>It is possible for a Bugzilla attachment to contain malicious + Javascript + code, which would be executed in the domain of your Bugzilla, thereby + making it possible for the attacker to e.g. steal your login cookies. + Due to internationalization concerns, we are unable to + incorporate by default the code changes necessary to fulfill the CERT + advisory requirements mentioned in <A HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3" TARGET="_top" >http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3</A >. - Making the change below will fix the problem if your installation is for - an English speaking audience. + If your installation is for an English speaking audience only, making the + change below will prevent this problem. </P ><P ->Telling Bugzilla to output a charset as part of the HTTP header is - much easier in version 2.18 and higher (including any cvs - pull after 4-May-2003 and development release after 2.17.5) than it was - in previous versions. Simply locate the following line in +>Simply locate the following line in <TT CLASS="filename" >Bugzilla/CGI.pm</TT @@ -4762,8 +4914,7 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # Make sure that we don't send any charset headers - $self->charset(''); +> $self->charset(''); </PRE ></FONT ></TD @@ -4781,8 +4932,7 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # Send all data using the ISO-8859-1 charset - $self->charset('ISO-8859-1'); +> $self->charset('ISO-8859-1'); </PRE ></FONT ></TD @@ -4790,69 +4940,6 @@ CLASS="programlisting" ></TABLE > </P -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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. See - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266" -TARGET="_top" ->bug 126266</A -> - for more information including progress toward making - bugzilla charset aware by default. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="directoryindex" -></A ->4.2.6. <TT -CLASS="filename" ->directoryindex</TT -> for the Bugzilla default page.</H2 -><P ->You should modify the <DirectoryIndex> parameter for - the Apache virtual host running your Bugzilla installation to - allow <TT -CLASS="filename" ->index.cgi</TT -> as the index page for a - directory, as well as the usual <TT -CLASS="filename" ->index.html</TT ->, - <TT -CLASS="filename" ->index.htm</TT ->, and so forth. </P ></DIV ><DIV CLASS="section" @@ -4861,7 +4948,7 @@ CLASS="section" ><A NAME="mod_perl" ></A ->4.2.7. Bugzilla and <TT +>4.3.6. Bugzilla and <TT CLASS="filename" >mod_perl</TT ></H2 @@ -4878,7 +4965,7 @@ CLASS="section" ><A NAME="mod-throttle" ></A ->4.2.8. <TT +>4.3.7. <TT CLASS="filename" >mod_throttle</TT > @@ -4929,7 +5016,7 @@ CLASS="section" ><A NAME="os-specific" ></A ->4.3. OS Specific Installation Notes</H1 +>4.4. OS Specific Installation Notes</H1 ><P >Many aspects of the Bugzilla installation can be affected by the the operating system you choose to install it on. Sometimes it can be made @@ -4952,9 +5039,9 @@ CLASS="section" ><A NAME="os-win32" ></A ->4.3.1. Microsoft Windows</H2 +>4.4.1. Microsoft Windows</H2 ><P ->Making Bugzilla work on windows is still a very painful processes. +>Making Bugzilla work on windows is still a painful processes. The Bugzilla Team is working to make it easier, but that goal is not considered a top priority. If you wish to run Bugzilla, we still recommend doing so on a Unix based system such as GNU/Linux. As of this @@ -4978,7 +5065,7 @@ CLASS="section" ><A NAME="win32-perl" ></A ->4.3.1.1. Win32 Perl</H3 +>4.4.1.1. Win32 Perl</H3 ><P >Perl for Windows can be obtained from <A HREF="http://www.activestate.com/" @@ -4999,12 +5086,12 @@ CLASS="section" ><A NAME="win32-perlmodules" ></A ->4.3.1.2. Perl Modules on Win32</H3 +>4.4.1.2. Perl Modules on Win32</H3 ><P >Bugzilla on Windows requires the same perl modules found in <A HREF="#install-perlmodules" ->Section 4.1.3</A +>Section 4.1.5</A >. The main difference is that windows uses <A HREF="#gloss-ppm" @@ -5111,18 +5198,11 @@ CLASS="section" ><A NAME="win32-code-changes" ></A ->4.3.1.3. Code changes required to run on win32</H3 +>4.4.1.3. Code changes required to run on win32</H3 ><P ->Unfortunately, Bugzilla still doesn't run "out of the box" on - Windows. There is work in progress to make this easier, but until that - happens code will have to be modified. This section is an attempt to - list the required changes. It is an attempt to be all inclusive, but - there may be other changes required. If you find something is missing, - please file a bug in <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. +>As Bugzilla still doesn't run "out of the box" on + Windows, code has to be modified. This section is an attempt to + list the required changes. </P ><DIV CLASS="section" @@ -5131,7 +5211,7 @@ CLASS="section" ><A NAME="win32-code-checksetup" ></A ->4.3.1.3.1. Changes to <TT +>4.4.1.3.1. Changes to <TT CLASS="filename" >checksetup.pl</TT ></H4 @@ -5218,7 +5298,7 @@ CLASS="section" ><A NAME="win32-code-bugmail" ></A ->4.3.1.3.2. Changes to <TT +>4.4.1.3.2. Changes to <TT CLASS="filename" >BugMail.pm</TT ></H4 @@ -5230,11 +5310,8 @@ TARGET="_top" >bug 84876</A > lands), the - simplest way is to have Net::SMTP installed and change this (in - <TT -CLASS="filename" ->Bugzilla/BugMail.pm</TT ->):</P + simplest way is to have the Net::SMTP Perl module installed and + change this:</P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -5299,19 +5376,19 @@ CLASS="section" ><A NAME="win32-http" ></A ->4.3.1.4. Serving the web pages</H3 +>4.4.1.4. Serving the web pages</H3 ><P >As is the case on Unix based systems, any web server should be able to handle Bugzilla; however, the Bugzilla Team still recommends Apache whenever asked. No matter what web server you choose, be sure to pay attention to the security notes in <A HREF="#security-access" ->Section 5.6.4</A +>Section 4.5.4</A >. More information on configuring specific web servers can be found in <A HREF="#http" ->Section 4.4</A +>Section 4.2</A >. </P ><DIV @@ -5360,7 +5437,7 @@ CLASS="section" ><A NAME="os-macosx" ></A ->4.3.2. <SPAN +>4.4.2. <SPAN CLASS="productname" >Mac OS X</SPAN ></H2 @@ -5554,7 +5631,7 @@ CLASS="section" ><A NAME="os-mandrake" ></A ->4.3.3. Linux-Mandrake 8.0</H2 +>4.4.3. Linux-Mandrake 8.0</H2 ><P >Linux-Mandrake 8.0 includes every required and optional library for Bugzilla. The easiest way to install them is by using the @@ -5652,87 +5729,105 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="http" +NAME="security" ></A ->4.4. HTTP Server Configuration</H1 +>4.5. Bugzilla Security</H1 +><DIV +CLASS="warning" ><P ->The Bugzilla Team recommends Apache when using Bugzilla, however, any web server - that can be configured to run <A -HREF="#gloss-cgi" -><I -CLASS="glossterm" ->CGI</I +></P +><TABLE +CLASS="warning" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>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.</P +><P +>This is not meant to be a comprehensive list of every possible + security issue pertaining to the software mentioned in this section. + There is + no subsitute for reading the information written by the authors of any + software running on your system. + </P +></TD +></TR +></TABLE +></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="security-networking" ></A -> scripts - should be able to handle Bugzilla. No matter what web server you choose, but - especially if you choose something other than Apache, you should be sure to read - <A -HREF="#security-access" ->Section 5.6.4</A ->. - </P +>4.5.1. TCP/IP Ports</H2 ><P ->The plan for this section is to eventually document the specifics of how to lock - down permissions on individual web servers. - </P +>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla + only needs 1, or 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. + </P +></DIV ><DIV CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="http-apache" +NAME="security-mysql" ></A ->4.4.1. Apache <SPAN -CLASS="productname" ->httpd</SPAN -></H2 +>4.5.2. MySQL</H2 ><P ->As mentioned above, the Bugzilla Team recommends Apache for use - with Bugzilla. You will have to make sure that Apache is properly - configured to run the Bugzilla CGI scripts. You also need to make sure - that the <TT -CLASS="filename" ->.htaccess</TT -> files created by - <B -CLASS="command" ->./checksetup.pl</B -> (shown in <A -HREF="#http-apache-htaccess" ->Example 4-2</A -> - for the curious) are allowed to override Apache's normal access - permissions or else important password information may be exposed to the - Internet. +>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 <EM +>not</EM +> the same as + the system root). Also, many installations default to running + <SPAN +CLASS="application" +>mysqld</SPAN +> as the system root. </P ><P ->Many Apache installations are not configured to run scripts - anywhere but in the <TT -CLASS="filename" ->cgi-bin</TT -> - directory; however, we recommend that Bugzilla not be installed in the - <TT -CLASS="filename" ->cgi-bin</TT ->, otherwise the static - files such as images and <A -HREF="#gloss-javascript" -><I -CLASS="glossterm" ->JavaScript</I -></A -> - will not work correctly. To allow scripts to run in the normal - web space, the following changes should be made to your - <TT -CLASS="filename" ->httpd.conf</TT -> file. - </P +></P +><OL +TYPE="1" +><LI ><P ->To allow files with a .cgi extension to be run, make sure the - following line exists and is uncommented:</P +>Consult the documentation that came with your system for + information on making <SPAN +CLASS="application" +>mysqld</SPAN +> run as an + unprivleged user. + </P +></LI +><LI +><P +>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: + </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -5743,25 +5838,56 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> AddHandler cgi-script .cgi - </PRE +> <TT +CLASS="prompt" +>bash$</TT +> mysql mysql +<TT +CLASS="prompt" +>mysql></TT +> DELETE FROM user WHERE user = ''; +<TT +CLASS="prompt" +>mysql></TT +> UPDATE user SET password = password('<TT +CLASS="replaceable" +><I +>new_password</I +></TT +>') WHERE user = 'root'; +<TT +CLASS="prompt" +>mysql></TT +> FLUSH PRIVILEGES; + </PRE ></FONT ></TD ></TR ></TABLE ><P ->To allow <TT +>From this point forward you will need to use + <B +CLASS="command" +>mysql -u root -p</B +> and enter + <TT +CLASS="replaceable" +><I +>new_password</I +></TT +> when prompted when using the + mysql client. + </P +></LI +><LI +><P +>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 <TT CLASS="filename" ->.htaccess</TT -> files to override - permissions and .cgi files to run in the Bugzilla directory, make sure - the following two lines are in a <TT -CLASS="computeroutput" ->Directory</TT -> - directive that applies to the Bugzilla directory on your system - (either the Bugzilla directory or one of its parents). - </P +>/etc/my.conf</TT +>: + </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -5772,13 +5898,57 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> Options +ExecCGI -AllowOverride Limit - </PRE +> [myslqd] +# Prevent network access to MySQL. +skip-networking + </PRE ></FONT ></TD ></TR ></TABLE +></LI +><LI +><P +>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. + </P +></LI +></OL +></DIV +><DIV +CLASS="section" +><HR><H2 +CLASS="section" +><A +NAME="security-daemon" +></A +>4.5.3. Daemon Accounts</H2 +><P +>Many daemons, such as Apache's httpd and MySQL's mysqld default to + running as either <SPAN +CLASS="QUOTE" +>"root"</SPAN +> or <SPAN +CLASS="QUOTE" +>"nobody"</SPAN +>. Running + as <SPAN +CLASS="QUOTE" +>"root"</SPAN +> introduces obvious security problems, but the + problems introduced by running everything as <SPAN +CLASS="QUOTE" +>"nobody"</SPAN +> may + not be so obvious. Basically, if you're running every daemon as + <SPAN +CLASS="QUOTE" +>"nobody"</SPAN +> and one of them gets compromised, they all get + compromised. For this reason it is recommended that you create a user + account for each daemon. + </P ><DIV CLASS="note" ><P @@ -5800,317 +5970,251 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->For more information on Apache and its directives, see the - glossary entry on <A -HREF="#gloss-apache" -><I -CLASS="glossterm" ->Apache</I -></A ->. - </P +>You will need to set the <TT +CLASS="varname" +>webservergroup</TT +> to + the group you created for your webserver to run as in + <TT +CLASS="filename" +>localconfig</TT +>. This will allow + <B +CLASS="command" +>./checksetup.pl</B +> to better adjust the file + permissions on your Bugzilla install so as to not require making + anything world-writable. + </P ></TD ></TR ></TABLE ></DIV +></DIV ><DIV -CLASS="example" +CLASS="section" +><HR><H2 +CLASS="section" ><A -NAME="http-apache-htaccess" +NAME="security-access" ></A +>4.5.4. Web Server Access Controls</H2 +><P +>There are many files that are placed in the Bugzilla directory + area that should not be accessable from the web. Because of the way + Bugzilla is currently laid out, the list of what should and should + not be accessible is rather complicated. + </P +><P +>Users of Apache don't need to worry about this, however, because + Bugzilla ships with .htaccess files which restrict access to all the + sensitive files in this section. Users of other webservers, read on. + </P ><P -><B ->Example 4-2. <TT -CLASS="filename" ->.htaccess</TT -> files for Apache</B ></P +><UL +COMPACT="COMPACT" +><LI ><P -><TT +>In the main Bugzilla directory, you should:</P +><P +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block: + <TT CLASS="filename" ->$BUGZILLA_HOME/.htaccess</TT +>*.pl</TT +>, <TT +CLASS="filename" +>*localconfig*</TT +>, <TT +CLASS="filename" +>runtests.sh</TT > - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # don't allow people to retrieve non-cgi executable files or our private data -<FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$> - deny from all -</FilesMatch> -<FilesMatch ^(localconfig.js|localconfig.rdf)$> - allow from all -</FilesMatch> - </PRE -></FONT -></TD -></TR -></TABLE -> - </P + </P +></LI +><LI ><P -><TT +>But allow: + <TT CLASS="filename" ->$BUGZILLA_HOME/data/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory; the only exception is duplicates.rdf, which is used by -# duplicates.xul and must be loadable over the web -deny from all -<Files duplicates.rdf> - allow from all -</Files> - </PRE -></FONT -></TD -></TR -></TABLE +>localconfig.js</TT +>, <TT +CLASS="filename" +>localconfig.rdf</TT > - </P + </P +></LI +></UL +></LI +><LI ><P -><TT +>In <TT CLASS="filename" ->$BUGZILLA_HOME/data/webdot</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # Restrict access to .dot files to the public webdot server at research.att.com -# if research.att.com ever changed their IP, or if you use a different -# webdot server, you'll need to edit this -<FilesMatch ^[0-9]+\.dot$> - Allow from 192.20.225.10 - Deny from all -</FilesMatch> - -# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and -# .map files -<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> - Allow from all -</FilesMatch> - -# And no directory listings, either. -Deny from all - </PRE -></FONT -></TD -></TR -></TABLE -> - </P +>data</TT +>:</P ><P -><TT +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block everything</P +></LI +><LI +><P +>But allow: + <TT CLASS="filename" ->$BUGZILLA_HOME/Bugzilla/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all - </PRE -></FONT -></TD -></TR -></TABLE +>duplicates.rdf</TT > - </P + </P +></LI +></UL +></LI +><LI ><P -><TT +>In <TT CLASS="filename" ->$BUGZILLA_HOME/template/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -></DIV -></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="http-iis" -></A ->4.4.2. Microsoft <SPAN -CLASS="productname" ->Internet Information Services</SPAN -></H2 +>data/webdot</TT +>:</P ><P ->If you need, or for some reason even want, to use Microsoft's - <SPAN -CLASS="productname" ->Internet Information Services</SPAN -> or - <SPAN -CLASS="productname" ->Personal Web Server</SPAN -> you should be able - to. You will need to configure them to know how to run CGI scripts, - however. This is described in Microsoft Knowledge Base article - <A -HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp" -TARGET="_top" ->Q245225</A +></P +><UL +COMPACT="COMPACT" +><LI +><P +>If you use a remote webdot server:</P +><P +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block everything</P +></LI +><LI +><P +>But allow + <TT +CLASS="filename" +>*.dot</TT > - for <SPAN -CLASS="productname" ->Internet Information Services</SPAN -> and - <A -HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp" -TARGET="_top" ->Q231998</A -> - for <SPAN -CLASS="productname" ->Personal Web Server</SPAN ->. - </P + only for the remote webdot server</P +></LI +></UL +></LI +><LI ><P ->Also, and this can't be stressed enough, make sure that files such as - <TT +>Otherwise, if you use a local GraphViz:</P +><P +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block everything</P +></LI +><LI +><P +>But allow: + <TT CLASS="filename" ->localconfig</TT -> and your <TT +>*.png</TT +>, <TT CLASS="filename" ->data</TT +>*.gif</TT +>, <TT +CLASS="filename" +>*.jpg</TT +>, <TT +CLASS="filename" +>*.map</TT > - directory are secured as described in <A -HREF="#security-access" ->Section 5.6.4</A ->. - </P -></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="http-aol" -></A ->4.4.3. AOL Server</H2 + </P +></LI +></UL +></LI +><LI ><P ->Ben FrantzDale reported success using AOL Server with Bugzilla. He - reported his experience and what appears below is based on that. - </P +>And if you don't use any dot:</P ><P ->AOL Server will have to be configured to run - <A -HREF="#gloss-cgi" -><I -CLASS="glossterm" ->CGI</I -></A -> scripts, please consult - the documentation that came with your server for more information on - how to do this. - </P +></P +><UL +COMPACT="COMPACT" +><LI ><P ->Because AOL Server doesn't support <TT +>Block everything</P +></LI +></UL +></LI +></UL +></LI +><LI +><P +>In <TT CLASS="filename" ->.htaccess</TT -> - files, you'll have to create a <A -HREF="#gloss-tcl" -><I -CLASS="glossterm" ->TCL</I -></A -> - script. You should create an <TT +>Bugzilla</TT +>:</P +><P +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block everything</P +></LI +></UL +></LI +><LI +><P +>In <TT CLASS="filename" ->aolserver/modules/tcl/filter.tcl</TT -> - file (the filename shouldn't matter) with the following contents (change +>template</TT +>:</P +><P +></P +><UL +COMPACT="COMPACT" +><LI +><P +>Block everything</P +></LI +></UL +></LI +></UL +><P +>You should test to make sure that the files mentioned above are + not accessible from the Internet, especially your <TT -CLASS="computeroutput" ->/bugzilla/</TT -> to the web-based path to - your Bugzilla installation): +CLASS="filename" +>localconfig</TT +> 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 + <A +HREF="http://bugzilla.mozilla.org/localconfig" +TARGET="_top" +>http://bugzilla.mozilla.org/localconfig</A +>. You should + get a <SPAN +CLASS="errorcode" +>403</SPAN +> <SPAN +CLASS="errorname" +>Forbidden</SPAN +> + error. </P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> ns_register_filter preauth GET /bugzilla/localconfig filter_deny -ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny -ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny -ns_register_filter preauth GET /bugzilla/*.pl filter_deny -ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny -ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny -ns_register_filter preauth GET /bugzilla/data/* filter_deny -ns_register_filter preauth GET /bugzilla/template/* filter_deny - -proc filter_deny { why } { - ns_log Notice "filter_deny" - return "filter_return" -} - </PRE -></FONT -></TD -></TR -></TABLE ><DIV -CLASS="warning" +CLASS="caution" ><P ></P ><TABLE -CLASS="warning" +CLASS="caution" WIDTH="100%" BORDER="0" ><TR @@ -6119,39 +6223,27 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="../images/caution.gif" HSPACE="5" -ALT="Warning"></TD +ALT="Caution"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->This probably doesn't account for all possible editor backup - files so you may wish to add some additional variations of - <TT -CLASS="filename" ->localconfig</TT ->. For more information, see - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383" -TARGET="_top" -> bug 186383</A -> or <A -HREF="http://online.securityfocus.com/bid/6501" -TARGET="_top" ->Bugtraq ID 6501</A ->. +>Not following the instructions in this section, including + testing, may result in sensitive information being globally + accessible. </P ></TD ></TR ></TABLE ></DIV ><DIV -CLASS="note" +CLASS="tip" ><P ></P ><TABLE -CLASS="note" +CLASS="tip" WIDTH="100%" BORDER="0" ><TR @@ -6160,49 +6252,20 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/note.gif" +SRC="../images/tip.gif" HSPACE="5" -ALT="Note"></TD +ALT="Tip"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->If you are using webdot from research.att.com (the default - configuration for the <TT -CLASS="option" ->webdotbase</TT -> paramater), you - will need to allow access to <TT -CLASS="filename" ->data/webdot/*.dot</TT -> - for the reasearch.att.com machine. - </P -><P ->If you are using a local installation of <A -HREF="http://www.graphviz.org" -TARGET="_top" ->GraphViz</A ->, you will need to allow - everybody to access <TT -CLASS="filename" ->*.png</TT ->, - <TT -CLASS="filename" ->*.gif</TT ->, <TT -CLASS="filename" ->*.jpg</TT ->, and - <TT -CLASS="filename" ->*.map</TT -> in the - <TT -CLASS="filename" ->data/webdot</TT -> directory. +>You should check <A +HREF="#http" +>Section 4.2</A +> to see if instructions + have been included for your web server. You should also compare those + instructions with this list to make sure everything is properly + accounted for. </P ></TD ></TR @@ -6217,7 +6280,7 @@ CLASS="section" ><A NAME="troubleshooting" ></A ->4.5. Troubleshooting</H1 +>4.6. Troubleshooting</H1 ><P >This section gives solutions to common Bugzilla installation problems. @@ -6227,9 +6290,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1157" +NAME="AEN1215" ></A ->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 +>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 ><P > Try executing <B CLASS="command" @@ -6252,9 +6315,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1162" +NAME="AEN1220" ></A ->4.5.2. DBD::Sponge::db prepare failed</H2 +>4.6.2. DBD::Sponge::db prepare failed</H2 ><P > The following error message may appear due to a bug in DBD::mysql (over which the Bugzilla team have no control): @@ -6340,7 +6403,7 @@ CLASS="section" ><A NAME="paranoid-security" ></A ->4.5.3. cannot chdir(/var/spool/mqueue)</H2 +>4.6.3. cannot chdir(/var/spool/mqueue)</H2 ><P >If you are installing Bugzilla on SuSE Linux, or some other distributions with @@ -6398,7 +6461,7 @@ CLASS="section" ><A NAME="trouble-filetemp" ></A ->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 +>4.6.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 ><P >This is caused by a bug in the version of <SPAN @@ -6607,7 +6670,7 @@ CLASS="command" standard type, and Bugzilla does not yet take advantage of features such as transactions which would justify this speed decrease. The Bugzilla team are, however, happy to hear about any experiences with - row level locking and Bugzilla</P + row level locking and Bugzilla.</P ><P >The <SPAN CLASS="QUOTE" @@ -6620,7 +6683,7 @@ CLASS="QUOTE" an enormous performance improvement when implemented on extremely high-traffic Bugzilla databases.</P ><P -> As a guide, mozilla.org began needing +> As a guide, on reasonably old hardware, mozilla.org began needing <SPAN CLASS="QUOTE" >"shadowdb"</SPAN @@ -7017,7 +7080,7 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->Don't disable the administrator account!</P +>Don't disable all the administrator accounts!</P ></TD ></TR ></TABLE @@ -7159,37 +7222,29 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="programadmin" -></A ->5.3. Product, Component, Milestone, and Version Administration</H1 -><DIV -CLASS="section" -><H2 -CLASS="section" -><A NAME="products" ></A ->5.3.1. Products</H2 +>5.3. Products</H1 ><P -> <A +> <A HREF="#gloss-product" ><I CLASS="glossterm" -> Products</I +> Products</I ></A > - 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...)</P + 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...)</P ><P >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.</P + 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.</P ><P >To create a new product:</P ><P @@ -7207,46 +7262,46 @@ TYPE="1" ><LI ><P >Enter the name of the product and a description. The - Description field may contain HTML.</P + Description field may contain HTML.</P ></LI ></OL ><P >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. - </P + 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. + </P ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="components" ></A ->5.3.2. Components</H2 +>5.4. Components</H1 ><P >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.</P -><P -> 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 - <EM + 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.</P +><P +> 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 + <EM >default assignments</EM >; - these can be changed on bug submission, or at any later point in - a bug's life.</P + these can be changed on bug submission, or at any later point in + a bug's life.</P ><P >To create a new Component:</P ><P @@ -7256,7 +7311,7 @@ TYPE="1" ><LI ><P >Select the "Edit components" link from the "Edit product" - page</P + page</P ></LI ><LI ><P @@ -7265,28 +7320,28 @@ TYPE="1" ><LI ><P >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. - </P + 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. + </P ></LI ></OL ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="versions" ></A ->5.3.3. Versions</H2 +>5.5. Versions</H1 ><P >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. - </P + 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select + field; the usual practice is to select the earliest version known to have + the bug. + </P ><P >To create and edit Versions:</P ><P @@ -7300,27 +7355,27 @@ TYPE="1" ><LI ><P >You will notice that the product already has the default - version "undefined". Click the "Add" link in the bottom right.</P + version "undefined". Click the "Add" link in the bottom right.</P ></LI ><LI ><P >Enter the name of the Version. This field takes text only. - Then click the "Add" button.</P + Then click the "Add" button.</P ></LI ></OL ></DIV ><DIV CLASS="section" -><HR><H2 +><HR><H1 CLASS="section" ><A NAME="milestones" ></A ->5.3.4. Milestones</H2 +>5.6. Milestones</H1 ><P >Milestones are "targets" that you plan to get a bug fixed by. For - example, you have a bug that you plan to fix for your 3.0 release, it - would be assigned the milestone of 3.0.</P + example, you have a bug that you plan to fix for your 3.0 release, it + would be assigned the milestone of 3.0.</P ><DIV CLASS="note" ><P @@ -7343,15 +7398,15 @@ ALIGN="LEFT" VALIGN="TOP" ><P >Milestone options will only appear for a Product if you turned - on the "usetargetmilestone" Param in the "Edit Parameters" screen. - </P + on the "usetargetmilestone" Param in the "Edit Parameters" screen. + </P ></TD ></TR ></TABLE ></DIV ><P >To create new Milestones, set Default Milestones, and set - Milestone URL:</P + Milestone URL:</P ><P ></P ><OL @@ -7363,55 +7418,25 @@ TYPE="1" ><LI ><P >Select "Add" in the bottom right corner. - text</P + text</P ></LI ><LI ><P >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".</P + 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".</P ></LI ><LI ><P >From the Edit product screen, you can enter the URL of a - page which gives information about your milestones and what - they mean. </P -><DIV -CLASS="tip" -><P -></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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.</P -></TD -></TR -></TABLE -></DIV + page which gives information about your milestones and what + they mean. </P ></LI ></OL ></DIV -></DIV ><DIV CLASS="section" ><HR><H1 @@ -7419,7 +7444,7 @@ CLASS="section" ><A NAME="voting" ></A ->5.4. Voting</H1 +>5.7. Voting</H1 ><P >Voting allows users to be given a pot of votes which they can allocate to bugs, to indicate that they'd like them fixed. @@ -7481,7 +7506,7 @@ CLASS="section" ><A NAME="groups" ></A ->5.5. Groups and Group Security</H1 +>5.8. Groups and Group Security</H1 ><P >Groups allow the administrator to isolate bugs or products that should only be seen by certain people. @@ -7620,9 +7645,10 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->The User Regexp is a perl regexp and, if not anchored, will match - any part of an address. So, if you do not want to grant access - into 'mycompany.com' to 'badperson@mycompany.com.hacker.net', use +>If specifying a domain in the regexp, make sure you end + the regexp with a $. Otherwise, when granting access to + "@mycompany\.com", you will allow access to + 'badperson@mycompany.com.cracker.net'. You need to use '@mycompany\.com$' as the regexp.</P ></TD ></TR @@ -7661,9 +7687,9 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="security" +NAME="upgrading" ></A ->5.6. Bugzilla Security</H1 +>5.9. Upgrading to New Releases</H1 ><DIV CLASS="warning" ><P @@ -7685,54 +7711,117 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->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.</P +>Upgrading is a one-way process. You should backup your database + and current Bugzilla directory before attempting the upgrade. If you wish + to revert to the old Bugzilla version for any reason, you will have to + restore from these backups. + </P ></TD ></TR ></TABLE ></DIV -><DIV -CLASS="note" +><P +>Upgrading Bugzilla is something we all want to do from time to time, + be it to get new features or pick up the latest security fix. How easy + it is to update depends on a few factors. + </P ><P ></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +><UL +><LI ><P ->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 <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. - </P -></TD -></TR -></TABLE -></DIV +>If the new version is a revision or a new point release</P +></LI +><LI +><P +>How many, if any, local changes have been made</P +></LI +></UL +><P +>There are also three different methods to upgrade your installation. + </P +><P +></P +><OL +TYPE="1" +><LI +><P +>Using CVS (<A +HREF="#upgrade-cvs" +>Example 5-1</A +>)</P +></LI +><LI +><P +>Downloading a new tarball (<A +HREF="#upgrade-tarball" +>Example 5-2</A +>)</P +></LI +><LI +><P +>Applying the relevant patches (<A +HREF="#upgrade-patches" +>Example 5-3</A +>)</P +></LI +></OL +><P +>Which options are available to you may depend on how large a jump + you are making and/or your network configuration. + </P +><P +>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. + </P +><P +>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. + </P +><P +>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. + </P +><P +>These examples also assume that your Bugzilla installation is at + <TT +CLASS="filename" +>/var/www/html/bugzilla</TT +>. If that is not the case, + simply substitute the proper paths where appropriate. + </P ><DIV -CLASS="warning" +CLASS="example" +><A +NAME="upgrade-cvs" +></A +><P +><B +>Example 5-1. Upgrading using CVS</B +></P +><P +>Every release of Bugzilla, whether it is a revision or a point + release, is tagged in CVS. Also, every tarball we have distributed + since version 2.12 has been primed for using CVS. This does, however, + require that you are able to access cvs-mirror.mozilla.org on port + 2401. + + <DIV +CLASS="tip" ><P ></P ><TABLE -CLASS="warning" +CLASS="tip" WIDTH="100%" BORDER="0" ><TR @@ -7741,81 +7830,22 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/warning.gif" +SRC="../images/tip.gif" HSPACE="5" -ALT="Warning"></TD +ALT="Tip"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->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. - </P +>If you can do this, updating using CVS is probably the most + painless method, especially if you have a lot of local changes. + </P ></TD ></TR ></TABLE ></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="security-networking" -></A ->5.6.1. TCP/IP Ports</H2 -><P ->TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla - only needs 1... 2 if you need to use features that require e-mail such - 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. - </P -></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="security-mysql" -></A ->5.6.2. MySQL</H2 -><P ->MySQL ships by default with many settings that should be changed. - By defaults it allows anybody to connect from localhost without a - password and have full administrative capabilities. It also defaults to - not have a root password (this is <EM ->not</EM -> the same as - the system root). Also, many installations default to running - <SPAN -CLASS="application" ->mysqld</SPAN -> as the system root. +> </P -><P -></P -><OL -TYPE="1" -><LI -><P ->Consult the documentation that came with your system for - information on making <SPAN -CLASS="application" ->mysqld</SPAN -> run as an - unprivleged user. - </P -></LI -><LI -><P ->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: - </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -7826,118 +7856,74 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> <TT -CLASS="prompt" ->bash$</TT -> mysql mysql -<TT -CLASS="prompt" ->mysql></TT -> DELETE FROM user WHERE user = ''; -<TT -CLASS="prompt" ->mysql></TT -> UPDATE user SET password = password('<TT -CLASS="replaceable" -><I ->new_password</I -></TT ->') WHERE user = 'root'; -<TT -CLASS="prompt" ->mysql></TT -> FLUSH PRIVILEGES; - </PRE +> bash$ <B +CLASS="command" +>cd /var/www/html/bugzilla</B +> +bash$ <B +CLASS="command" +>cvs login</B +> +Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot +CVS password: <B +CLASS="command" +>anonymous</B +> +bash$ <B +CLASS="command" +>cvs -q update -r BUGZILLA-2_16_2 -dP</B +> +P checksetup.pl +P collectstats.pl +P globals.pl +P docs/rel_notes.txt +P template/en/default/list/quips.html.tmpl + </PRE ></FONT ></TD ></TR ></TABLE ><P ->From this point forward you will need to use - <B -CLASS="command" ->mysql -u root -p</B -> and enter - <TT -CLASS="replaceable" -><I ->new_password</I -></TT -> when prompted when using the - mysql client. - </P -></LI -><LI +> <DIV +CLASS="caution" ><P ->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 <TT -CLASS="filename" ->/etc/my.conf</TT ->: - </P +></P ><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" +CLASS="caution" WIDTH="100%" +BORDER="0" ><TR ><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> [myslqd] -# Prevent network access to MySQL. -skip-networking - </PRE -></FONT +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/caution.gif" +HSPACE="5" +ALT="Caution"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>If a line in the output from <B +CLASS="command" +>cvs update</B +> + begins with a <TT +CLASS="computeroutput" +>C</TT +> that represents a + file with local changes that CVS was unable to properly merge. You + need to resolve these conflicts manually before Bugzilla (or at + least the portion using that file) will be usable. + </P ></TD ></TR ></TABLE -></LI -><LI -><P ->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. - </P -></LI -></OL ></DIV -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="security-daemon" -></A ->5.6.3. Daemon Accounts</H2 -><P ->Many daemons, such as Apache's httpd and MySQL's mysqld default to - running as either <SPAN -CLASS="QUOTE" ->"root"</SPAN -> or <SPAN -CLASS="QUOTE" ->"nobody"</SPAN ->. Running - as <SPAN -CLASS="QUOTE" ->"root"</SPAN -> introduces obvious security problems, but the - problems introduced by running everything as <SPAN -CLASS="QUOTE" ->"nobody"</SPAN -> may - not be so obvious. Basically, if you're running every daemon as - <SPAN -CLASS="QUOTE" ->"nobody"</SPAN -> 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. - </P -><DIV +> + + <DIV CLASS="note" ><P ></P @@ -7958,231 +7944,111 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->You will need to set the <TT -CLASS="varname" ->webservergroup</TT -> to - the group you created for your webserver to run as in - <TT -CLASS="filename" ->localconfig</TT ->. This will allow - <B +>You also need to run <B CLASS="command" >./checksetup.pl</B -> to better adjust the file - permissions on your Bugzilla install so as to not require making - anything world-writable. - </P +> + before your Bugzilla upgrade will be complete. + </P ></TD ></TR ></TABLE ></DIV +> + </P ></DIV ><DIV -CLASS="section" -><HR><H2 -CLASS="section" +CLASS="example" ><A -NAME="security-access" +NAME="upgrade-tarball" ></A ->5.6.4. Web Server Access Controls</H2 -><P ->There are many files that are placed in the Bugzilla directory - area that should not be accessable from the web. Because of the way - 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 - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659" -TARGET="_top" -> bug 44659</A -> for more information. - </P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->In the main Bugzilla directory, you should:</P ><P +><B +>Example 5-2. Upgrading using the tarball</B ></P -><UL -COMPACT="COMPACT" -><LI ><P ->Block: - <TT -CLASS="filename" ->*.pl</TT ->, <TT -CLASS="filename" ->*localconfig*</TT ->, <TT -CLASS="filename" ->runtests.sh</TT +>If you are unable or unwilling to use CVS, another option that's + always available is to download the latest tarball. This is the most + difficult option to use, especially if you have local changes. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="programlisting" +> bash$ <B +CLASS="command" +>cd /var/www/html</B > - </P -></LI -><LI -><P ->But allow: - <TT -CLASS="filename" ->localconfig.js</TT ->, <TT -CLASS="filename" ->localconfig.rdf</TT +bash$ <B +CLASS="command" +>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B > - </P -></LI -></UL -></LI -><LI -><P ->In <TT -CLASS="filename" ->data</TT ->:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->Block everything</P -></LI -><LI -><P ->But allow: - <TT -CLASS="filename" ->duplicates.rdf</TT +<EM +>Output omitted</EM > - </P -></LI -></UL -></LI -><LI -><P ->In <TT -CLASS="filename" ->data/webdot</TT ->:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->If you use a remote webdot server:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->Block everything</P -></LI -><LI -><P ->But allow - <TT -CLASS="filename" ->*.dot</TT +bash$ <B +CLASS="command" +>tar xzvf bugzilla-2.16.2.tar.gz</B > - only for the remote webdot server</P -></LI -></UL -></LI -><LI -><P ->Otherwise, if you use a local GraphViz:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->Block everything</P -></LI -><LI -><P ->But allow: - <TT -CLASS="filename" ->*.png</TT ->, <TT -CLASS="filename" ->*.gif</TT ->, <TT -CLASS="filename" ->*.jpg</TT ->, <TT -CLASS="filename" ->*.map</TT +bugzilla-2.16.2/ +bugzilla-2.16.2/.cvsignore +bugzilla-2.16.2/1x1.gif +<EM +>Output truncated</EM > - </P -></LI -></UL -></LI -><LI -><P ->And if you don't use any dot:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->Block everything</P -></LI -></UL -></LI -></UL -></LI -><LI -><P ->In <TT -CLASS="filename" ->Bugzilla</TT ->:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI -><P ->Block everything</P -></LI -></UL -></LI -><LI -><P ->In <TT -CLASS="filename" ->template</TT ->:</P -><P -></P -><UL -COMPACT="COMPACT" -><LI +bash$ <B +CLASS="command" +>cd bugzilla-2.16.2</B +> +bash$ <B +CLASS="command" +>cp ../bugzilla/localconfig* .</B +> +bash$ <B +CLASS="command" +>cp -r ../bugzilla/data .</B +> +bash$ <B +CLASS="command" +>cd ..</B +> +bash$ <B +CLASS="command" +>mv bugzilla bugzilla.old</B +> +bash$ <B +CLASS="command" +>mv bugzilla-2.16.2 bugzilla</B +> +bash$ <B +CLASS="command" +>cd bugzilla</B +> +bash$ <B +CLASS="command" +>./checksetup.pl</B +> +<EM +>Output omitted</EM +> + </PRE +></FONT +></TD +></TR +></TABLE ><P ->Block everything</P -></LI -></UL -></LI -></UL -><DIV -CLASS="tip" +> <DIV +CLASS="warning" ><P ></P ><TABLE -CLASS="tip" +CLASS="warning" WIDTH="100%" BORDER="0" ><TR @@ -8191,64 +8057,37 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/tip.gif" +SRC="../images/warning.gif" HSPACE="5" -ALT="Tip"></TD +ALT="Warning"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->Bugzilla ships with the ability to generate - <TT -CLASS="filename" ->.htaccess</TT -> files instructing - <A -HREF="#gloss-apache" -><I -CLASS="glossterm" ->Apache</I -></A -> which files - should and should not be accessible. For more information, see - <A -HREF="#http-apache" ->Section 4.4.1</A ->. - </P +>The <B +CLASS="command" +>cp</B +> commands both end with periods which + is a very important detail, it tells the shell that the destination + directory is the current working directory. Also, the period at the + beginning of the <B +CLASS="command" +>./checksetup.pl</B +> is important and + can not be omitted. + </P ></TD ></TR ></TABLE ></DIV -><P ->You should test to make sure that the files mentioned above are - not accessible from the Internet, especially your - <TT -CLASS="filename" ->localconfig</TT -> 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 - <A -HREF="http://bugzilla.mozilla.org/localconfig" -TARGET="_top" ->http://bugzilla.mozilla.org/localconfig</A ->. You should - get a <SPAN -CLASS="errorcode" ->403</SPAN -> <SPAN -CLASS="errorname" ->Forbidden</SPAN > - error. - </P -><DIV -CLASS="caution" + + <DIV +CLASS="note" ><P ></P ><TABLE -CLASS="caution" +CLASS="note" WIDTH="100%" BORDER="0" ><TR @@ -8257,27 +8096,88 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/caution.gif" +SRC="../images/note.gif" HSPACE="5" -ALT="Caution"></TD +ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->Not following the instructions in this section, including - testing, may result in sensitive information being globally - accessible. - </P +>You will now have to reapply any changes you have made to your + local installation manually. + </P ></TD ></TR ></TABLE ></DIV +> + </P +></DIV ><DIV -CLASS="tip" +CLASS="example" +><A +NAME="upgrade-patches" +></A ><P +><B +>Example 5-3. Upgrading using patches</B ></P +><P +>The Bugzilla team will normally make a patch file available for + revisions to go from the most recent revision to the new one. You could + also read the release notes and grab the patches attached to the + mentioned bug, but it is safer to use the released patch file as + sometimes patches get changed before they get checked in. + It is also theoretically possible to + scour the fixed bug list and pick and choose which patches to apply + from a point release, but this is not recommended either as what you'll + end up with is a hodge podge Bugzilla that isn't really any version. + This would also make it more difficult to upgrade in the future. + </P ><TABLE -CLASS="tip" +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="programlisting" +> bash$ <B +CLASS="command" +>cd /var/www/html/bugzilla</B +> +bash$ <B +CLASS="command" +>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B +> +<EM +>Output omitted</EM +> +bash$ <B +CLASS="command" +>gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B +> +bash$ <B +CLASS="command" +>patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B +> +patching file checksetup.pl +patching file collectstats.pl +patching file globals.pl + </PRE +></FONT +></TD +></TR +></TABLE +><P +> <DIV +CLASS="caution" +><P +></P +><TABLE +CLASS="caution" WIDTH="100%" BORDER="0" ><TR @@ -8286,55 +8186,60 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG -SRC="../images/tip.gif" +SRC="../images/caution.gif" HSPACE="5" -ALT="Tip"></TD +ALT="Caution"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P ->You should check <A -HREF="#http" ->Section 4.4</A -> to see if instructions - have been included for your web server. You should also compare those - instructions with this list to make sure everything is properly - accounted for. - </P +>If you do this, beware that this doesn't change the entires in + your <TT +CLASS="filename" +>CVS</TT +> directory so it may make + updates using CVS (<A +HREF="#upgrade-cvs" +>Example 5-1</A +>) more difficult in the + future. + </P ></TD ></TR ></TABLE ></DIV +> + </P +></DIV ></DIV ></DIV ><DIV -CLASS="section" +CLASS="chapter" ><HR><H1 +><A +NAME="customization" +></A +>Chapter 6. Customising Bugzilla</H1 +><DIV +CLASS="section" +><H1 CLASS="section" ><A NAME="cust-templates" ></A ->5.7. Template Customization</H1 +>6.1. Template Customization</H1 ><P -> One of the large changes for 2.16 was the templatization of the - entire user-facing UI, using the - <A -HREF="http://www.template-toolkit.org" -TARGET="_top" ->Template Toolkit</A ->. - Administrators can now configure the look and feel of Bugzilla without +> Administrators can 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. </P ><P > Templatization also makes localized versions of Bugzilla possible, - for the first time. As of version 2.17.4 which will soon - become 2.18, it's possible to have Bugzilla's language determined by - the user's browser. More information is available in + for the first time. It's possible to have Bugzilla's UI language + determined by the user's browser. More information is available in <A HREF="#template-http-accept" ->Section 5.7.5</A +>Section 6.1.5</A >. </P ><DIV @@ -8342,13 +8247,11 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1606" +NAME="AEN1597" ></A ->5.7.1. What to Edit</H2 +>6.1.1. What to Edit</H2 ><P -> There are two different ways of editing of Bugzilla's templates, - and which you use depends mainly on how you upgrade Bugzilla. The - template directory structure is that there's a top level directory, +> The template directory structure is that there's a top level directory, <TT CLASS="filename" >template</TT @@ -8377,7 +8280,10 @@ CLASS="filename" must be created if you want to use it. </P ><P -> The first method of making customizations is to directly edit the +> There are two different ways of editing Bugzilla's templates, + and which you use depends mainly on the method you plan to use to + upgrade Bugzilla. + The first method of making customizations is to directly edit the templates in <TT CLASS="filename" >template/en/default</TT @@ -8395,7 +8301,8 @@ CLASS="command" occur. </P ><P -> The other method is to copy the templates into a mirrored directory +> The other method is to copy the templates to be modified into a + mirrored directory structure under <TT CLASS="filename" >template/en/custom</TT @@ -8492,47 +8399,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1629" +NAME="AEN1620" ></A ->5.7.2. How To Edit Templates</H2 -><P -> The syntax of the Template Toolkit language is beyond the scope of - this guide. It's reasonably easy to pick up by looking at the current - templates; or, you can read the manual, available on the - <A -HREF="http://www.template-toolkit.org" -TARGET="_top" ->Template Toolkit home - page</A ->. 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. - </P -><P -> 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 &lt;. 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. - </P -><P -> 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. - </P -><P -> 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. - </P +>6.1.2. How To Edit Templates</H2 ><DIV CLASS="note" ><P @@ -8568,15 +8437,51 @@ TARGET="_top" ></TR ></TABLE ></DIV +><P +> The syntax of the Template Toolkit language is beyond the scope of + this guide. It's reasonably easy to pick up by looking at the current + templates; or, you can read the manual, available on the + <A +HREF="http://www.template-toolkit.org" +TARGET="_top" +>Template Toolkit home + page</A +>. + </P +><P +> 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 &lt;. You use the 'html' filter in the + Template Toolkit to do this. If you forget, you may open up + your installation to cross-site scripting attacks. + </P +><P +> 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. + </P +><P +> 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. + </P ></DIV ><DIV CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1639" +NAME="AEN1630" ></A ->5.7.3. Template Formats</H2 +>6.1.3. Template Formats</H2 ><P > Some CGIs have the ability to use more than one template. For example, buglist.cgi can output bug lists as RDF or two @@ -8590,9 +8495,9 @@ CLASS="filename" </P ><P > To see if a CGI supports multiple output formats, grep the - CGI for "ValidateOutputFormat". If it's not present, adding + CGI for "GetFormat". If it's not present, adding multiple format support isn't too hard - see how it's done in - other CGIs. + other CGIs, e.g. config.cgi. </P ><P > To make a new format template for a CGI which supports this, @@ -8636,9 +8541,9 @@ CLASS="section" ><HR><H2 CLASS="section" ><A -NAME="AEN1652" +NAME="AEN1643" ></A ->5.7.4. Particular Templates</H2 +>6.1.4. Particular Templates</H2 ><P > There are a few templates you may be particularly interested in customizing for your installation. @@ -8694,21 +8599,6 @@ CLASS="command" ><P > <B CLASS="command" ->bug/process/midair.html.tmpl</B ->: - This is the page used if two people submit simultaneous changes to the - same bug. The second person to submit their changes will get this page - to tell them what the first person did, and ask if they wish to - overwrite those changes or go back and revisit the bug. The default - title and header on this page read "Mid-air collision detected!" If - you work in the aviation industry, or other environment where this - might be found offensive (yes, we have true stories of this happening) - you'll want to change this to something more appropriate for your - environment. - </P -><P -> <B -CLASS="command" >bug/create/create.html.tmpl</B > and <B @@ -8827,13 +8717,11 @@ CLASS="section" ><A NAME="template-http-accept" ></A ->5.7.5. Configuring Bugzilla to Detect the User's Language</H2 +>6.1.5. Configuring Bugzilla to Detect the User's Language</H2 ><P ->Begining in version 2.18 (first introduced in version - 2.17.4), it's now possible to have the users web browser tell Bugzilla - which language templates to use for each visitor (using the HTTP_ACCEPT - header). For this to work, Bugzilla needs to have the correct language - templates installed for the version of Bugzilla you are using. Many +>Bugzilla honours the user's Accept: HTTP header. You can install + templates in other languages, and Bugzilla will pick the most appropriate + according to a priority order defined by you. Many language templates can be obtained from <A HREF="http://www.bugzilla.org/download.html#localizations" TARGET="_top" @@ -8845,7 +8733,7 @@ TARGET="_top" >After untarring the localizations (or creating your own) in the <TT CLASS="filename" ->[Bugzilla_Root]/template</TT +>$BUGZILLA_HOME/template</TT > directory, you must update the <TT CLASS="option" @@ -8870,7 +8758,7 @@ CLASS="section" ><A NAME="cust-change-permissions" ></A ->5.8. Change Permission Customization</H1 +>6.2. Customizing Who Can Change What</H1 ><DIV CLASS="warning" ><P @@ -8894,9 +8782,10 @@ VALIGN="TOP" ><P > This feature should be considered experimental; the Bugzilla code you will be changing is not stable, and could change or move between - versions. Be aware that if you make modifications to it, you may have + versions. Be aware that if you make modifications as outlined here, + you may have to re-make them or port them if Bugzilla changes internally between - versions. + versions, and you upgrade. </P ></TD ></TR @@ -9039,454 +8928,258 @@ CLASS="section" ><HR><H1 CLASS="section" ><A -NAME="upgrading" +NAME="dbmodify" ></A ->5.9. Upgrading to New Releases</H1 -><DIV -CLASS="warning" +>6.3. Modifying Your Running System</H1 ><P -></P -><TABLE -CLASS="warning" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/warning.gif" -HSPACE="5" -ALT="Warning"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Upgrading is a one-way process. You should backup your database - and current Bugzilla directory before attempting the upgrade. If you wish - to revert to the old Bugzilla version for any reason, you will have to - restore from these backups. - </P -></TD -></TR -></TABLE -></DIV -><P ->Upgrading Bugzilla is something we all want to do from time to time, - be it to get new features or pick up the latest security fix. How easy - it is to update depends on a few factors. - </P -><P -></P -><UL -><LI -><P ->If the new version is a revision or a new point release</P -></LI -><LI -><P ->How many, if any, local changes have been made</P -></LI -></UL +>Bugzilla optimizes database lookups by storing all relatively + static information in the + <TT +CLASS="filename" +>versioncache</TT +> file, located in the + <TT +CLASS="filename" +>data/</TT +> + subdirectory under your installation directory.</P ><P ->There are also three different methods to upgrade your installation. - </P +>If you make a change to the structural data in your database (the + versions table for example), or to the + <SPAN +CLASS="QUOTE" +>"constants"</SPAN +> + + encoded in <TT +CLASS="filename" +>defparams.pl</TT +>, you will need to remove + the cached content from the data directory (by doing a + <SPAN +CLASS="QUOTE" +>"rm data/versioncache"</SPAN +> + + ), or your changes won't show up.</P ><P -></P -><OL -TYPE="1" -><LI +> <TT +CLASS="filename" +>versioncache</TT +> + gets automatically regenerated whenever it's more than + an hour old, so Bugzilla will eventually notice your changes by itself, + but generally you want it to notice right away, so that you can test + things.</P +></DIV +><DIV +CLASS="section" +><HR><H1 +CLASS="section" +><A +NAME="dbdoc" +></A +>6.4. MySQL Bugzilla Database Introduction</H1 ><P ->Using CVS (<A -HREF="#upgrade-cvs" ->Example 5-1</A ->)</P -></LI -><LI +>This information comes straight from my life. I was forced to learn + how Bugzilla organizes database because of nitpicky requests from users + for tiny changes in wording, rather than having people re-educate + themselves or figure out how to work our procedures around the tool. It + sucks, but it can and will happen to you, so learn how the schema works + and deal with it when it comes.</P ><P ->Downloading a new tarball (<A -HREF="#upgrade-tarball" ->Example 5-2</A ->)</P -></LI -><LI +>So, here you are with your brand-new installation of Bugzilla. + You've got MySQL set up, Apache working right, Perl DBI and DBD talking + to the database flawlessly. Maybe you've even entered a few test bugs to + make sure email's working; people seem to be notified of new bugs and + changes, and you can enter and edit bugs to your heart's content. Perhaps + you've gone through the trouble of setting up a gateway for people to + submit bugs to your database via email, have had a few people test it, + and received rave reviews from your beta testers.</P ><P ->Applying the relevant patches (<A -HREF="#upgrade-patches" ->Example 5-3</A ->)</P -></LI -></OL +>What's the next thing you do? Outline a training strategy for your + development team, of course, and bring them up to speed on the new tool + you've labored over for hours.</P ><P ->Which options are available to you may depend on how large a jump - you are making and/or your network configuration. - </P +>Your first training session starts off very well! You have a + captive audience which seems enraptured by the efficiency embodied in + this thing called "Bugzilla". You are caught up describing the nifty + features, how people can save favorite queries in the database, set them + up as headers and footers on their pages, customize their layouts, + generate reports, track status with greater efficiency than ever before, + leap tall buildings with a single bound and rescue Jane from the clutches + of Certain Death!</P ><P ->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. - </P +>But Certain Death speaks up -- a tiny voice, from the dark corners + of the conference room. "I have a concern," the voice hisses from the + darkness, "about the use of the word 'verified'."</P ><P ->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. - </P +>The room, previously filled with happy chatter, lapses into + reverential silence as Certain Death (better known as the Vice President + of Software Engineering) continues. "You see, for two years we've used + the word 'verified' to indicate that a developer or quality assurance + engineer has confirmed that, in fact, a bug is valid. I don't want to + lose two years of training to a new software product. You need to change + the bug status of 'verified' to 'approved' as soon as possible. To avoid + confusion, of course."</P ><P ->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. - </P +>Oh no! Terror strikes your heart, as you find yourself mumbling + "yes, yes, I don't think that would be a problem," You review the changes + with Certain Death, and continue to jabber on, "no, it's not too big a + change. I mean, we have the source code, right? You know, 'Use the + Source, Luke' and all that... no problem," All the while you quiver + inside like a beached jellyfish bubbling, burbling, and boiling on a hot + Jamaican sand dune...</P ><P ->These examples also assume that your Bugzilla installation is at - <TT -CLASS="filename" ->/var/www/html/bugzilla</TT ->. If that is not the case, - simply substitute the proper paths where appropriate. - </P +>Thus begins your adventure into the heart of Bugzilla. You've been + forced to learn about non-portable enum() fields, varchar columns, and + tinyint definitions. The Adventure Awaits You!</P ><DIV -CLASS="example" +CLASS="section" +><HR><H2 +CLASS="section" ><A -NAME="upgrade-cvs" +NAME="AEN1719" ></A +>6.4.1. Bugzilla Database Basics</H2 ><P -><B ->Example 5-1. Upgrading using CVS</B -></P -><P ->Every release of Bugzilla, whether it is a revision or a point - release, is tagged in CVS. Also, every tarball we have distributed - since version 2.12 has been primed for using CVS. This does, however, - require that you are able to access cvs-mirror.mozilla.org on port - 2401. +>If you were like me, at this point you're totally clueless about + the internals of MySQL, and if it weren't for this executive order from + the Vice President you couldn't care less about the difference between + a + <SPAN +CLASS="QUOTE" +>"bigint"</SPAN +> - <DIV -CLASS="tip" + and a + <SPAN +CLASS="QUOTE" +>"tinyint"</SPAN +> + + entry in MySQL. I recommend you refer to the + <A +HREF="http://www.mysql.com/documentation/" +TARGET="_top" +>MySQL documentation</A +> + . Below are the basics you need to know about the Bugzilla database. + Check the chart above for more details.</P ><P +> <P ></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +><OL +TYPE="1" +><LI ><P ->If you can do this, updating using CVS is probably the most - painless method, especially if you have a lot of local changes. - </P -></TD -></TR -></TABLE -></DIV -> - </P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> bash$ <B -CLASS="command" ->cd /var/www/html/bugzilla</B +>To connect to your database:</P +><P +> <TT +CLASS="prompt" +>bash#</TT > -bash$ <B + + <B CLASS="command" ->cvs login</B +>mysql</B > -Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot -CVS password: <B -CLASS="command" ->anonymous</B + + <TT +CLASS="parameter" +><I +>-u root</I +></TT > -bash$ <B -CLASS="command" ->cvs -q update -r BUGZILLA-2_16_2 -dP</B + </P +><P +>If this works without asking you for a password, + <EM +>shame on you</EM > -P checksetup.pl -P collectstats.pl -P globals.pl -P docs/rel_notes.txt -P template/en/default/list/quips.html.tmpl - </PRE -></FONT -></TD -></TR -></TABLE + + ! You should have locked your security down like the installation + instructions told you to. You can find details on locking down + your database in the Bugzilla FAQ in this directory (under + "Security"), or more robust security generalities in the + <A +HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system" +TARGET="_top" +>MySQL + searchable documentation</A +>. + </P +></LI +><LI ><P -> <DIV -CLASS="caution" +>You should now be at a prompt that looks like this:</P ><P -></P -><TABLE -CLASS="caution" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/caution.gif" -HSPACE="5" -ALT="Caution"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +> <TT +CLASS="prompt" +>mysql></TT +> + </P ><P ->If a line in the output from <B -CLASS="command" ->cvs update</B +>At the prompt, if + <SPAN +CLASS="QUOTE" +>"bugs"</SPAN > - begins with a <TT -CLASS="computeroutput" ->C</TT -> that represents a - file with local changes that CVS was unable to properly merge. You - need to resolve these conflicts manually before Bugzilla (or at - least the portion using that file) will be usable. - </P -></TD -></TR -></TABLE -></DIV + + is the name you chose in the + <TT +CLASS="filename" +>localconfig</TT > - <DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" + file for your Bugzilla database, type:</P ><P ->You also need to run <B +> <TT +CLASS="prompt" +>mysql</TT +> + + <B CLASS="command" ->./checksetup.pl</B +>use bugs;</B > - before your Bugzilla upgrade will be complete. - </P -></TD -></TR -></TABLE -></DIV + </P +></LI +></OL > </P -></DIV ><DIV -CLASS="example" +CLASS="section" +><HR><H3 +CLASS="section" ><A -NAME="upgrade-tarball" +NAME="AEN1746" ></A +>6.4.1.1. Bugzilla Database Tables</H3 ><P -><B ->Example 5-2. Upgrading using the tarball</B -></P +>Imagine your MySQL database as a series of spreadsheets, and + you won't be too far off. If you use this command:</P ><P ->If you are unable or unwilling to use CVS, another option that's - always available is to download the latest tarball. This is the most - difficult option to use, especially if you have local changes. - </P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> bash$ <B -CLASS="command" ->cd /var/www/html</B -> -bash$ <B -CLASS="command" ->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B -> -<EM ->Output omitted</EM -> -bash$ <B -CLASS="command" ->tar xzvf bugzilla-2.16.2.tar.gz</B -> -bugzilla-2.16.2/ -bugzilla-2.16.2/.cvsignore -bugzilla-2.16.2/1x1.gif -<EM ->Output truncated</EM -> -bash$ <B -CLASS="command" ->cd bugzilla-2.16.2</B -> -bash$ <B -CLASS="command" ->cp ../bugzilla/localconfig* .</B -> -bash$ <B -CLASS="command" ->cp -r ../bugzilla/data .</B -> -bash$ <B -CLASS="command" ->cd ..</B -> -bash$ <B -CLASS="command" ->mv bugzilla bugzilla.old</B -> -bash$ <B -CLASS="command" ->mv bugzilla-2.16.2 bugzilla</B -> -bash$ <B -CLASS="command" ->cd bugzilla</B -> -bash$ <B -CLASS="command" ->./checksetup.pl</B -> -<EM ->Output omitted</EM +> <TT +CLASS="prompt" +>mysql></TT > - </PRE -></FONT -></TD -></TR -></TABLE -><P -> <DIV -CLASS="warning" -><P -></P -><TABLE -CLASS="warning" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/warning.gif" -HSPACE="5" -ALT="Warning"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->The <B -CLASS="command" ->cp</B -> commands both end with periods which - is a very important detail, it tells the shell that the destination - directory is the current working directory. Also, the period at the - beginning of the <B + <B CLASS="command" ->./checksetup.pl</B -> is important and - can not be omitted. - </P -></TD -></TR -></TABLE -></DIV +>show tables from bugs;</B > - - <DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" + </P ><P ->You will now have to reapply any changes you have made to your - local installation manually. - </P -></TD -></TR -></TABLE -></DIV +>you'll be able to see the names of all the + <SPAN +CLASS="QUOTE" +>"spreadsheets"</SPAN > - </P -></DIV -><DIV -CLASS="example" -><A -NAME="upgrade-patches" -></A -><P -><B ->Example 5-3. Upgrading using patches</B -></P + (tables) in your database.</P ><P ->The Bugzilla team will normally make a patch file available for - revisions to go from the most recent revision to the new one. You could - also read the release notes and grab the patches attached to the - mentioned bug, but it is safer to use the released patch file as - sometimes patches get changed before they get checked in (for minor - spelling fixes and the like). It is also theorectically possible to - scour the fixed bug list and pick and choose which patches to apply - from a point release, but this is not recommended either as what you'll - end up with is a hodge podge Bugzilla that isn't really any version. - This would also make it more difficult to upgrade in the future. - </P -><TABLE +>From the command issued above, ou should have some + output that looks like this: +<TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -9496,72 +9189,200 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> bash$ <B -CLASS="command" ->cd /var/www/html/bugzilla</B -> -bash$ <B -CLASS="command" ->wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B -> -<EM ->Output omitted</EM -> -bash$ <B -CLASS="command" ->gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B -> -bash$ <B -CLASS="command" ->patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B -> -patching file checksetup.pl -patching file collectstats.pl -patching file globals.pl - </PRE +> +-------------------+ +| Tables in bugs | ++-------------------+ +| attachments | +| bugs | +| bugs_activity | +| cc | +| components | +| dependencies | +| fielddefs | +| groups | +| keyworddefs | +| keywords | +| logincookies | +| longdescs | +| milestones | +| namedqueries | +| products | +| profiles | +| profiles_activity | +| tokens | +| versions | +| votes | +| watch | ++-------------------+ +</PRE ></FONT ></TD ></TR ></TABLE +> +</P ><P -> <DIV -CLASS="caution" -><P -></P -><TABLE -CLASS="caution" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/caution.gif" -HSPACE="5" -ALT="Caution"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->If you do this, beware that this doesn't change the entires in - your <TT -CLASS="filename" ->CVS</TT -> directory so it may make - updates using CVS (<A -HREF="#upgrade-cvs" ->Example 5-1</A ->) more difficult in the - future. - </P -></TD -></TR -></TABLE +CLASS="literallayout" +><br> + Here's an overview of what each table does. Most columns in each table have<br> +descriptive names that make it fairly trivial to figure out their jobs.<br> +<br> +attachments: This table stores all attachments to bugs. It tends to be your<br> +largest table, yet also generally has the fewest entries because file<br> +attachments are so (relatively) large.<br> +<br> +bugs: This is the core of your system. The bugs table stores most of the<br> +current information about a bug, with the exception of the info stored in the<br> +other tables.<br> +<br> +bugs_activity: This stores information regarding what changes are made to bugs<br> +when -- a history file.<br> +<br> +cc: This tiny table simply stores all the CC information for any bug which has<br> +any entries in the CC field of the bug. Note that, like most other tables in<br> +Bugzilla, it does not refer to users by their user names, but by their unique<br> +userid, stored as a primary key in the profiles table.<br> +<br> +components: This stores the programs and components (or products and<br> +components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br> +(product) field is the full name of the product, rather than some other unique<br> +identifier, like bug_id and user_id are elsewhere in the database.<br> +<br> +dependencies: Stores data about those cool dependency trees.<br> +<br> +fielddefs: A nifty table that defines other tables. For instance, when you<br> +submit a form that changes the value of "AssignedTo" this table allows<br> +translation to the actual field name "assigned_to" for entry into MySQL.<br> +<br> +groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br> +identify group memberships. For instance, say the group that is allowed to<br> +tweak parameters is assigned a value of "1", the group that is allowed to edit<br> +users is assigned a "2", and the group that is allowed to create new groups is<br> +assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br> +like the chmod command in UNIX,) you can identify a user is allowed to tweak<br> +parameters and create groups, but not edit users, by giving him a bitmask of<br> +"5", or a user allowed to edit users and create groups, but not tweak<br> +parameters, by giving him a bitmask of "6" Simple, huh?<br> + If this makes no sense to you, try this at the mysql prompt:<br> +mysql> select * from groups;<br> + You'll see the list, it makes much more sense that way.<br> +<br> +keyworddefs: Definitions of keywords to be used<br> +<br> +keywords: Unlike what you'd think, this table holds which keywords are<br> +associated with which bug id's.<br> +<br> +logincookies: This stores every login cookie ever assigned to you for every<br> +machine you've ever logged into Bugzilla from. Curiously, it never does any<br> +housecleaning -- I see cookies in this file I've not used for months. However,<br> +since Bugzilla never expires your cookie (for convenience' sake), it makes<br> +sense.<br> +<br> +longdescs: The meat of bugzilla -- here is where all user comments are stored!<br> +You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br> +sparingly -- that's only the amount of space the Old Testament from the Bible<br> +would take (uncompressed, 16 megabytes). Each comment is keyed to the<br> +bug_id to which it's attached, so the order is necessarily chronological, for<br> +comments are played back in the order in which they are received.<br> +<br> +milestones: Interesting that milestones are associated with a specific product<br> +in this table, but Bugzilla does not yet support differing milestones by<br> +product through the standard configuration interfaces.<br> +<br> +namedqueries: This is where everybody stores their "custom queries". Very<br> +cool feature; it beats the tar out of having to bookmark each cool query you<br> +construct.<br> +<br> +products: What products you have, whether new bug entries are allowed for the<br> +product, what milestone you're working toward on that product, votes, etc. It<br> +will be nice when the components table supports these same features, so you<br> +could close a particular component for bug entry without having to close an<br> +entire product...<br> +<br> +profiles: Ahh, so you were wondering where your precious user information was<br> +stored? Here it is! With the passwords in plain text for all to see! (but<br> +sshh... don't tell your users!)<br> +<br> +profiles_activity: Need to know who did what when to who's profile? This'll<br> +tell you, it's a pretty complete history.<br> +<br> +versions: Version information for every product<br> +<br> +votes: Who voted for what when<br> +<br> +watch: Who (according to userid) is watching who's bugs (according to their<br> +userid).<br> +<br> +<br> +===<br> +THE DETAILS<br> +===<br> +<br> + Ahh, so you're wondering just what to do with the information above? At the<br> +mysql prompt, you can view any information about the columns in a table with<br> +this command (where "table" is the name of the table you wish to view):<br> +<br> +mysql> show columns from table;<br> +<br> + You can also view all the data in a table with this command:<br> +<br> +mysql> select * from table;<br> +<br> + -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br> +you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br> +50,000 bugs play across your screen.<br> +<br> + You can limit the display from above a little with the command, where<br> +"column" is the name of the column for which you wish to restrict information:<br> +<br> +mysql> select * from table where (column = "some info");<br> +<br> + -- or the reverse of this<br> +<br> +mysql> select * from table where (column != "some info");<br> +<br> + Let's take our example from the introduction, and assume you need to change<br> +the word "verified" to "approved" in the resolution field. We know from the<br> +above information that the resolution is likely to be stored in the "bugs"<br> +table. Note we'll need to change a little perl code as well as this database<br> +change, but I won't plunge into that in this document. Let's verify the<br> +information is stored in the "bugs" table:<br> +<br> +mysql> show columns from bugs<br> +<br> + (exceedingly long output truncated here)<br> +| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br> +<br> + Sorry about that long line. We see from this that the "bug status" column is<br> +an "enum field", which is a MySQL peculiarity where a string type field can<br> +only have certain types of entries. While I think this is very cool, it's not<br> +standard SQL. Anyway, we need to add the possible enum field entry<br> +'APPROVED' by altering the "bugs" table.<br> +<br> +mysql> ALTER table bugs CHANGE bug_status bug_status<br> + -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br> + -> "VERIFIED", "APPROVED", "CLOSED") not null;<br> +<br> + (note we can take three lines or more -- whatever you put in before the<br> +semicolon is evaluated as a single expression)<br> +<br> +Now if you do this:<br> +<br> +mysql> show columns from bugs;<br> +<br> + you'll see that the bug_status field has an extra "APPROVED" enum that's<br> +available! Cool thing, too, is that this is reflected on your query page as<br> +well -- you can query by the new status. But how's it fit into the existing<br> +scheme of things?<br> + Looks like you need to go back and look for instances of the word "verified"<br> +in the perl code for Bugzilla -- wherever you find "verified", change it to<br> +"approved" and you're in business (make sure that's a case-insensitive search).<br> +Although you can query by the enum field, you can't give something a status<br> +of "APPROVED" until you make the perl changes. Note that this change I<br> +mentioned can also be done by editing checksetup.pl, which automates a lot of<br> +this. But you need to know this stuff anyway, right?<br> + </P ></DIV -> - </P ></DIV ></DIV ><DIV @@ -9571,7 +9392,7 @@ CLASS="section" ><A NAME="integration" ></A ->5.10. Integrating Bugzilla with Third-Party Tools</H1 +>6.5. Integrating Bugzilla with Third-Party Tools</H1 ><DIV CLASS="section" ><H2 @@ -9579,7 +9400,7 @@ CLASS="section" ><A NAME="bonsai" ></A ->5.10.1. Bonsai</H2 +>6.5.1. Bonsai</H2 ><P >Bonsai is a web-based tool for managing <A @@ -9605,7 +9426,7 @@ CLASS="section" ><A NAME="cvs" ></A ->5.10.2. CVS</H2 +>6.5.2. CVS</H2 ><P >CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P @@ -9641,7 +9462,7 @@ CLASS="section" ><A NAME="scm" ></A ->5.10.3. Perforce SCM</H2 +>6.5.3. Perforce SCM</H2 ><P >You can find the project page for Bugzilla and Teamtrack Perforce integration (p4dti) at: @@ -9681,9 +9502,22 @@ CLASS="section" ><A NAME="tinderbox" ></A ->5.10.4. Tinderbox/Tinderbox2</H2 +>6.5.4. Tinderbox/Tinderbox2</H2 ><P ->We need Tinderbox integration information.</P +>Tinderbox is a continuous-build system which can integrate with + Bugzilla - see + <A +HREF="http://www.mozilla.org/projects/tinderbox" +TARGET="_top" +>http://www.mozilla.org/projects/tinderbox</A +> for details + of Tinderbox, and + <A +HREF="http://tinderbox.mozilla.org/showbuilds.cgi" +TARGET="_top" +>http://tinderbox.mozilla.org/showbuilds.cgi</A +> to see it + in action.</P ></DIV ></DIV ></DIV @@ -9709,56 +9543,51 @@ HREF="#faq-general" ><DL ><DT >A.1.1. <A -HREF="#faq-general-information" -> Where can I find information about Bugzilla?</A -></DT -><DT ->A.1.2. <A HREF="#faq-general-license" > What license is Bugzilla distributed under? </A ></DT ><DT ->A.1.3. <A +>A.1.2. <A HREF="#faq-general-support" > How do I get commercial support for Bugzilla? </A ></DT ><DT ->A.1.4. <A +>A.1.3. <A HREF="#faq-general-companies" > What major companies or projects are currently using Bugzilla for bug-tracking? </A ></DT ><DT ->A.1.5. <A +>A.1.4. <A HREF="#faq-general-maintainers" > Who maintains Bugzilla? </A ></DT ><DT ->A.1.6. <A +>A.1.5. <A HREF="#faq-general-compare" > How does Bugzilla stack up against other bug-tracking databases? </A ></DT ><DT ->A.1.7. <A +>A.1.6. <A HREF="#faq-general-bzmissing" > Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software? </A ></DT ><DT ->A.1.8. <A +>A.1.7. <A HREF="#faq-general-mysql" > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL. </A ></DT ><DT ->A.1.9. <A +>A.1.8. <A HREF="#faq-general-bonsaitools" > What is <TT CLASS="filename" @@ -9767,7 +9596,7 @@ CLASS="filename" </A ></DT ><DT ->A.1.10. <A +>A.1.9. <A HREF="#faq-general-perlpath" > My perl is not located at <TT CLASS="filename" @@ -9777,7 +9606,7 @@ CLASS="filename" </A ></DT ><DT ->A.1.11. <A +>A.1.10. <A HREF="#faq-general-cookie" > Is there an easy way to change the Bugzilla cookie name? </A @@ -9800,33 +9629,6 @@ HREF="#faq-phb-client" ></DT ><DT >A.2.2. <A -HREF="#faq-phb-integration" -> Can Bugzilla integrate with - Perforce (SCM software)? - </A -></DT -><DT ->A.2.3. <A -HREF="#faq-phb-projects" -> Does Bugzilla allow the user to track multiple projects? - </A -></DT -><DT ->A.2.4. <A -HREF="#faq-phb-sorting" -> If I am on many projects, and search for all bugs assigned to me, will - Bugzilla list them for me and allow me to sort by project, severity etc? - </A -></DT -><DT ->A.2.5. <A -HREF="#faq-phb-attachments" -> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, - are there any that are NOT allowed? - </A -></DT -><DT ->A.2.6. <A HREF="#faq-phb-priorities" > Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and @@ -9834,35 +9636,28 @@ HREF="#faq-phb-priorities" </A ></DT ><DT ->A.2.7. <A +>A.2.3. <A HREF="#faq-phb-reporting" > Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) </A ></DT ><DT ->A.2.8. <A +>A.2.4. <A HREF="#faq-phb-email" > Is there email notification and if so, what do you see when you get an email? </A ></DT ><DT ->A.2.9. <A -HREF="#faq-phb-cclist" -> Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? - </A -></DT -><DT ->A.2.10. <A +>A.2.5. <A HREF="#faq-phb-emailapp" > Do users have to have any particular type of email application? </A ></DT ><DT ->A.2.11. <A +>A.2.6. <A HREF="#faq-phb-data" > Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be @@ -9871,28 +9666,21 @@ HREF="#faq-phb-data" </A ></DT ><DT ->A.2.12. <A +>A.2.7. <A HREF="#faq-phb-l10n" > Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? </A ></DT ><DT ->A.2.13. <A +>A.2.8. <A HREF="#faq-phb-reports" > Can a user create and save reports? Can they do this in Word format? Excel format? </A ></DT ><DT ->A.2.14. <A -HREF="#faq-phb-searching" -> Does Bugzilla have the ability to search by word, phrase, compound - search? - </A -></DT -><DT ->A.2.15. <A +>A.2.9. <A HREF="#faq-phb-midair" > Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use @@ -9900,29 +9688,29 @@ HREF="#faq-phb-midair" </A ></DT ><DT ->A.2.16. <A +>A.2.10. <A HREF="#faq-phb-backup" > Are there any backup features provided? </A ></DT ><DT ->A.2.17. <A +>A.2.11. <A HREF="#faq-phb-livebackup" > Can users be on the system while a backup is in progress? </A ></DT ><DT ->A.2.18. <A +>A.2.12. <A HREF="#faq-phb-maintenance" > What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an - "Out-of-the-Box" solution. + "out-of-the-box" solution? </A ></DT ><DT ->A.2.19. <A +>A.2.13. <A HREF="#faq-phb-installtime" > What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to @@ -9932,7 +9720,7 @@ HREF="#faq-phb-installtime" </A ></DT ><DT ->A.2.20. <A +>A.2.14. <A HREF="#faq-phb-cost" > Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -9960,14 +9748,6 @@ HREF="#faq-security-knownproblems" > Are there any security problems with Bugzilla? </A ></DT -><DT ->A.3.3. <A -HREF="#faq-security-mysqluser" -> I've implemented the security fixes mentioned in Chris Yeh's security - advisory of 5/10/2000 advising not to run MySQL as root, and am running into - problems with MySQL no longer working correctly. - </A -></DT ></DL ></DD ><DT @@ -9994,32 +9774,25 @@ HREF="#faq-email-testing" ><DT >A.4.3. <A HREF="#faq-email-whine" -> I want whineatnews.pl to whine at something more, or other than, only new +> I want whineatnews.pl to whine at something different to only new bugs. How do I do it? </A ></DT ><DT >A.4.4. <A -HREF="#faq-email-procmail" -> I don't like/want to use Procmail to hand mail off to bug_email.pl. - What alternatives do I have? - </A -></DT -><DT ->A.4.5. <A HREF="#faq-email-mailif" > How do I set up the email interface to submit/change bugs via email? </A ></DT ><DT ->A.4.6. <A +>A.4.5. <A HREF="#faq-email-sendmailnow" > Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives? </A ></DT ><DT ->A.4.7. <A +>A.4.6. <A HREF="#faq-email-nonreceived" > How come email from Bugzilla changes never reaches me? </A @@ -10198,38 +9971,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-information" -></A -><B ->A.1.1. </B -> - Where can I find information about Bugzilla?</P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You can stay up-to-date with the latest Bugzilla - information at <A -HREF="http://www.bugzilla.org/" -TARGET="_top" ->http://www.bugzilla.org/</A ->. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-general-license" ></A ><B ->A.1.2. </B +>A.1.1. </B > What license is Bugzilla distributed under? </P @@ -10258,7 +10003,7 @@ CLASS="question" NAME="faq-general-support" ></A ><B ->A.1.3. </B +>A.1.2. </B > How do I get commercial support for Bugzilla? </P @@ -10278,16 +10023,6 @@ TARGET="_top" as consultants for Bugzilla. </P ><P -> <A -HREF="http://www.collab.net/" -TARGET="_top" ->http://www.collab.net/</A -> offers - Bugzilla as part of their standard offering to large projects. - They do have some minimum fees that are pretty hefty, and generally - aren't interested in small projects. - </P -><P > There are several experienced Bugzilla hackers on the mailing list/newsgroup who are willing to make themselves available for generous compensation. @@ -10304,7 +10039,7 @@ CLASS="question" NAME="faq-general-companies" ></A ><B ->A.1.4. </B +>A.1.3. </B > What major companies or projects are currently using Bugzilla for bug-tracking? @@ -10322,9 +10057,9 @@ CLASS="answer" Bugzilla sites to track bugs in their products. We have a fairly complete list available on our website at <A -HREF="http://bugzilla.org/installation_list.html" +HREF="http://bugzilla.org/installation-list/" TARGET="_top" ->http://bugzilla.org/installation_list.html</A +>http://bugzilla.org/installation-list/</A >. If you have an installation of Bugzilla and would like to be added to the list, whether it's a public install or not, simply e-mail @@ -10334,11 +10069,7 @@ CLASS="email" HREF="mailto:gerv@mozilla.org" >gerv@mozilla.org</A >></TT ->. Keep in mind that it's kinda - difficult to get onto the <SPAN -CLASS="QUOTE" ->"high-profile"</SPAN -> list ;). +>. </P ></DIV ></DIV @@ -10351,7 +10082,7 @@ CLASS="question" NAME="faq-general-maintainers" ></A ><B ->A.1.5. </B +>A.1.4. </B > Who maintains Bugzilla? </P @@ -10381,7 +10112,7 @@ CLASS="question" NAME="faq-general-compare" ></A ><B ->A.1.6. </B +>A.1.5. </B > How does Bugzilla stack up against other bug-tracking databases? </P @@ -10419,7 +10150,7 @@ CLASS="question" NAME="faq-general-bzmissing" ></A ><B ->A.1.7. </B +>A.1.6. </B > Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software? @@ -10459,7 +10190,7 @@ CLASS="question" NAME="faq-general-mysql" ></A ><B ->A.1.8. </B +>A.1.7. </B > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL. @@ -10504,7 +10235,7 @@ CLASS="question" NAME="faq-general-bonsaitools" ></A ><B ->A.1.9. </B +>A.1.8. </B > What is <TT CLASS="filename" @@ -10546,7 +10277,7 @@ CLASS="question" NAME="faq-general-perlpath" ></A ><B ->A.1.10. </B +>A.1.9. </B > My perl is not located at <TT CLASS="filename" @@ -10595,7 +10326,7 @@ CLASS="question" NAME="faq-general-cookie" ></A ><B ->A.1.11. </B +>A.1.10. </B > Is there an easy way to change the Bugzilla cookie name? </P @@ -10618,36 +10349,6 @@ CLASS="qandadiv" NAME="faq-phb" ></A >2. Managerial Questions</H3 -><P -> <DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> Questions likely to be asked by managers. :-) - </P -></TD -></TR -></TABLE -></DIV -> - </P ><DIV CLASS="qandaentry" ><DIV @@ -10669,113 +10370,7 @@ CLASS="answer" ><B > </B > - It is web and e-mail based. You can edit bugs by sending specially - formatted email to a properly configured Bugzilla, or control via the web. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-integration" -></A -><B ->A.2.2. </B -> - Can Bugzilla integrate with - Perforce (SCM software)? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes! You can find more information elsewhere in "The Bugzilla - Guide" in the "Integration with Third-Party Products" section. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-projects" -></A -><B ->A.2.3. </B -> - Does Bugzilla allow the user to track multiple projects? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Absolutely! You can track any number of Products that can each be - composed of any number of Components. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-sorting" -></A -><B ->A.2.4. </B -> - If I am on many projects, and search for all bugs assigned to me, will - Bugzilla list them for me and allow me to sort by project, severity etc? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-attachments" -></A -><B ->A.2.5. </B -> - Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, - are there any that are NOT allowed? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes - any sort of attachment is allowed, although administrators can - configure a maximum size. - Bugzilla gives the user the option of either using the MIME-type - supplied by the browser, choosing from a pre-defined list or - manually typing any arbitrary MIME-type. + It is web and e-mail based. </P ></DIV ></DIV @@ -10788,7 +10383,7 @@ CLASS="question" NAME="faq-phb-priorities" ></A ><B ->A.2.6. </B +>A.2.2. </B > Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and @@ -10825,7 +10420,7 @@ CLASS="question" NAME="faq-phb-reporting" ></A ><B ->A.2.7. </B +>A.2.3. </B > Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) @@ -10863,7 +10458,7 @@ CLASS="question" NAME="faq-phb-email" ></A ><B ->A.2.8. </B +>A.2.4. </B > Is there email notification and if so, what do you see when you get an email? @@ -10876,7 +10471,7 @@ CLASS="answer" > </B > Email notification is user-configurable. By default, the bug id and - Summary of the bug report accompany each email notification, along with + summary of the bug report accompany each email notification, along with a list of the changes made. </P ></DIV @@ -10887,35 +10482,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-cclist" -></A -><B ->A.2.9. </B -> - Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-phb-emailapp" ></A ><B ->A.2.10. </B +>A.2.5. </B > Do users have to have any particular type of email application? @@ -10974,7 +10544,7 @@ CLASS="question" NAME="faq-phb-data" ></A ><B ->A.2.11. </B +>A.2.6. </B > Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be @@ -10991,7 +10561,7 @@ CLASS="answer" Bugzilla can output buglists as HTML (the default), CSV or RDF. The link for CSV can be found at the bottom of the buglist in HTML format. This CSV format can easily be imported into MS Excel or - other spread-sheet applications. + other spreadsheet applications. </P ><P > To use the RDF format of the buglist it is necessary to append a @@ -11000,7 +10570,7 @@ CLASS="computeroutput" >&ctype=rdf</TT > to the URL. RDF is meant to be machine readable and thus it is assumed that the - URL would be generated progmatically so there is no user visible + URL would be generated programatically so there is no user visible link to this format. </P ><P @@ -11036,7 +10606,7 @@ CLASS="question" NAME="faq-phb-l10n" ></A ><B ->A.2.12. </B +>A.2.7. </B > Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? @@ -11074,7 +10644,7 @@ CLASS="question" NAME="faq-phb-reports" ></A ><B ->A.2.13. </B +>A.2.8. </B > Can a user create and save reports? Can they do this in Word format? Excel format? @@ -11096,36 +10666,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-searching" -></A -><B ->A.2.14. </B -> - Does Bugzilla have the ability to search by word, phrase, compound - search? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You have no idea. Bugzilla's query interface, particularly with the - advanced Boolean operators, is incredibly versatile. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-phb-midair" ></A ><B ->A.2.15. </B +>A.2.9. </B > Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use @@ -11152,7 +10696,7 @@ CLASS="question" NAME="faq-phb-backup" ></A ><B ->A.2.16. </B +>A.2.10. </B > Are there any backup features provided? </P @@ -11182,7 +10726,7 @@ CLASS="question" NAME="faq-phb-livebackup" ></A ><B ->A.2.17. </B +>A.2.11. </B > Can users be on the system while a backup is in progress? </P @@ -11208,13 +10752,13 @@ CLASS="question" NAME="faq-phb-maintenance" ></A ><B ->A.2.18. </B +>A.2.12. </B > What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an - "Out-of-the-Box" solution. + "out-of-the-box" solution? </P ></DIV ><DIV @@ -11243,7 +10787,7 @@ CLASS="question" NAME="faq-phb-installtime" ></A ><B ->A.2.19. </B +>A.2.13. </B > What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to @@ -11276,7 +10820,7 @@ CLASS="question" NAME="faq-phb-cost" ></A ><B ->A.2.20. </B +>A.2.14. </B > Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -11358,34 +10902,6 @@ CLASS="answer" </P ></DIV ></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-security-mysqluser" -></A -><B ->A.3.3. </B -> - I've implemented the security fixes mentioned in Chris Yeh's security - advisory of 5/10/2000 advising not to run MySQL as root, and am running into - problems with MySQL no longer working correctly. - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - This is a common problem, related to running out of file descriptors. - Simply add "ulimit -n unlimited" to the script which starts - mysqld. - </P -></DIV -></DIV ></DIV ><DIV CLASS="qandadiv" @@ -11461,7 +10977,7 @@ NAME="faq-email-whine" ><B >A.4.3. </B > - I want whineatnews.pl to whine at something more, or other than, only new + I want whineatnews.pl to whine at something different to only new bugs. How do I do it? </P ></DIV @@ -11489,49 +11005,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-procmail" -></A -><B ->A.4.4. </B -> - I don't like/want to use Procmail to hand mail off to bug_email.pl. - What alternatives do I have? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You can call bug_email.pl directly from your aliases file, with - an entry like this: - <A -NAME="AEN2067" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" -><P -> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" - </P -></BLOCKQUOTE -> - However, this is fairly nasty and subject to problems; you also - need to set up your smrsh (sendmail restricted shell) to allow - it. In a pinch, though, it can work. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-email-mailif" ></A ><B ->A.4.5. </B +>A.4.4. </B > How do I set up the email interface to submit/change bugs via email? </P @@ -11556,7 +11033,7 @@ CLASS="question" NAME="faq-email-sendmailnow" ></A ><B ->A.4.6. </B +>A.4.5. </B > Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives? @@ -11568,7 +11045,21 @@ CLASS="answer" ><B > </B > - If you are using an alternate <A + If you are using <SPAN +CLASS="application" +>sendmail</SPAN +>, try enabling + <TT +CLASS="option" +>sendmailnow</TT +> in <TT +CLASS="filename" +>editparams.cgi</TT +>. + + </P +><P +> If you are using an alternate <A HREF="#gloss-mta" ><I CLASS="glossterm" @@ -11592,20 +11083,6 @@ CLASS="literal" >on</TT >. </P -><P -> If you are using <SPAN -CLASS="application" ->sendmail</SPAN ->, try enabling - <TT -CLASS="option" ->sendmailnow</TT -> in <TT -CLASS="filename" ->editparams.cgi</TT ->. - - </P ></DIV ></DIV ><DIV @@ -11617,7 +11094,7 @@ CLASS="question" NAME="faq-email-nonreceived" ></A ><B ->A.4.7. </B +>A.4.6. </B > How come email from Bugzilla changes never reaches me? </P @@ -11634,7 +11111,7 @@ CLASS="answer" button after entering your email address. </P ><P -> If you never receive mail from Bugzilla, chances you do not have +> If you never receive mail from Bugzilla, chances are you do not have sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked to, "/usr/lib/sendmail". </P @@ -11668,11 +11145,12 @@ CLASS="answer" ><B > </B > - Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. + Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle, + but it is now so old as to be obsolete, and is totally unsupported. Red Hat's newer version (based on 2.17.1 and soon to be merged into the main distribution) runs on PostgreSQL. At this time we know of - no recent ports of Bugzilla to Oracle but do intend to support it - in the future (possibly the 2.20 time-frame). + no recent ports of Bugzilla to Oracle; to be honest, Bugzilla + doesn't need what Oracle offers. </P ></DIV ></DIV @@ -11703,10 +11181,9 @@ CLASS="QUOTE" > utility (<TT CLASS="filename" ->./sanitycheck.cgi</TT -> in the - Bugzilla_home directory) from your web browser to see! If - it finishes without errors, you're +>sanitycheck.cgi</TT +>) from your web browser to see! + If it finishes without errors, you're <EM >probably</EM > OK. If it doesn't come back @@ -11951,7 +11428,7 @@ CLASS="answer" ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN2150" +NAME="AEN2062" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -12469,581 +11946,16 @@ TARGET="_top" CLASS="appendix" ><HR><H1 ><A -NAME="database" -></A ->Appendix B. The Bugzilla Database</H1 -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->This document really needs to be updated with more fleshed out - information about primary keys, interrelationships, and maybe some nifty - tables to document dependencies. Any takers?</P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="dbmodify" -></A ->B.1. Modifying Your Running System</H1 -><P ->Bugzilla optimizes database lookups by storing all relatively - static information in the - <TT -CLASS="filename" ->versioncache</TT -> file, located in the - <TT -CLASS="filename" ->data/</TT -> - subdirectory under your installation directory.</P -><P ->If you make a change to the structural data in your database (the - versions table for example), or to the - <SPAN -CLASS="QUOTE" ->"constants"</SPAN -> - - encoded in <TT -CLASS="filename" ->defparams.pl</TT ->, you will need to remove - the cached content from the data directory (by doing a - <SPAN -CLASS="QUOTE" ->"rm data/versioncache"</SPAN -> - - ), or your changes won't show up.</P -><P -> <TT -CLASS="filename" ->versioncache</TT -> - gets automatically regenerated whenever it's more than - an hour old, so Bugzilla will eventually notice your changes by itself, - but generally you want it to notice right away, so that you can test - things.</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="dbdoc" -></A ->B.2. MySQL Bugzilla Database Introduction</H1 -><P ->This information comes straight from my life. I was forced to learn - how Bugzilla organizes database because of nitpicky requests from users - for tiny changes in wording, rather than having people re-educate - themselves or figure out how to work our procedures around the tool. It - sucks, but it can and will happen to you, so learn how the schema works - and deal with it when it comes.</P -><P ->So, here you are with your brand-new installation of Bugzilla. - You've got MySQL set up, Apache working right, Perl DBI and DBD talking - to the database flawlessly. Maybe you've even entered a few test bugs to - make sure email's working; people seem to be notified of new bugs and - changes, and you can enter and edit bugs to your heart's content. Perhaps - you've gone through the trouble of setting up a gateway for people to - submit bugs to your database via email, have had a few people test it, - and received rave reviews from your beta testers.</P -><P ->What's the next thing you do? Outline a training strategy for your - development team, of course, and bring them up to speed on the new tool - you've labored over for hours.</P -><P ->Your first training session starts off very well! You have a - captive audience which seems enraptured by the efficiency embodied in - this thing called "Bugzilla". You are caught up describing the nifty - features, how people can save favorite queries in the database, set them - up as headers and footers on their pages, customize their layouts, - generate reports, track status with greater efficiency than ever before, - leap tall buildings with a single bound and rescue Jane from the clutches - of Certain Death!</P -><P ->But Certain Death speaks up -- a tiny voice, from the dark corners - of the conference room. "I have a concern," the voice hisses from the - darkness, "about the use of the word 'verified'."</P -><P ->The room, previously filled with happy chatter, lapses into - reverential silence as Certain Death (better known as the Vice President - of Software Engineering) continues. "You see, for two years we've used - the word 'verified' to indicate that a developer or quality assurance - engineer has confirmed that, in fact, a bug is valid. I don't want to - lose two years of training to a new software product. You need to change - the bug status of 'verified' to 'approved' as soon as possible. To avoid - confusion, of course."</P -><P ->Oh no! Terror strikes your heart, as you find yourself mumbling - "yes, yes, I don't think that would be a problem," You review the changes - with Certain Death, and continue to jabber on, "no, it's not too big a - change. I mean, we have the source code, right? You know, 'Use the - Source, Luke' and all that... no problem," All the while you quiver - inside like a beached jellyfish bubbling, burbling, and boiling on a hot - Jamaican sand dune...</P -><P ->Thus begins your adventure into the heart of Bugzilla. You've been - forced to learn about non-portable enum() fields, varchar columns, and - tinyint definitions. The Adventure Awaits You!</P -><DIV -CLASS="section" -><HR><H2 -CLASS="section" -><A -NAME="AEN2279" -></A ->B.2.1. Bugzilla Database Basics</H2 -><P ->If you were like me, at this point you're totally clueless about - the internals of MySQL, and if it weren't for this executive order from - the Vice President you couldn't care less about the difference between - a - <SPAN -CLASS="QUOTE" ->"bigint"</SPAN -> - - and a - <SPAN -CLASS="QUOTE" ->"tinyint"</SPAN -> - - entry in MySQL. I recommend you refer to the - <A -HREF="http://www.mysql.com/documentation/" -TARGET="_top" ->MySQL documentation</A -> - . Below are the basics you need to know about the Bugzilla database. - Check the chart above for more details.</P -><P -> <P -></P -><OL -TYPE="1" -><LI -><P ->To connect to your database:</P -><P -> <TT -CLASS="prompt" ->bash#</TT -> - - <B -CLASS="command" ->mysql</B -> - - <TT -CLASS="parameter" -><I ->-u root</I -></TT -> - </P -><P ->If this works without asking you for a password, - <EM ->shame on you</EM -> - - ! You should have locked your security down like the installation - instructions told you to. You can find details on locking down - your database in the Bugzilla FAQ in this directory (under - "Security"), or more robust security generalities in the - <A -HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system" -TARGET="_top" ->MySQL - searchable documentation</A ->. - </P -></LI -><LI -><P ->You should now be at a prompt that looks like this:</P -><P -> <TT -CLASS="prompt" ->mysql></TT -> - </P -><P ->At the prompt, if - <SPAN -CLASS="QUOTE" ->"bugs"</SPAN -> - - is the name you chose in the - <TT -CLASS="filename" ->localconfig</TT -> - - file for your Bugzilla database, type:</P -><P -> <TT -CLASS="prompt" ->mysql</TT -> - - <B -CLASS="command" ->use bugs;</B -> - </P -></LI -></OL -> - </P -><DIV -CLASS="section" -><HR><H3 -CLASS="section" -><A -NAME="AEN2306" -></A ->B.2.1.1. Bugzilla Database Tables</H3 -><P ->Imagine your MySQL database as a series of spreadsheets, and - you won't be too far off. If you use this command:</P -><P -> <TT -CLASS="prompt" ->mysql></TT -> - <B -CLASS="command" ->show tables from bugs;</B -> - </P -><P ->you'll be able to see the names of all the - <SPAN -CLASS="QUOTE" ->"spreadsheets"</SPAN -> - (tables) in your database.</P -><P ->From the command issued above, ou should have some - output that looks like this: -<TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> +-------------------+ -| Tables in bugs | -+-------------------+ -| attachments | -| bugs | -| bugs_activity | -| cc | -| components | -| dependencies | -| fielddefs | -| groups | -| keyworddefs | -| keywords | -| logincookies | -| longdescs | -| milestones | -| namedqueries | -| products | -| profiles | -| profiles_activity | -| tokens | -| versions | -| votes | -| watch | -+-------------------+ -</PRE -></FONT -></TD -></TR -></TABLE -> -</P -><P -CLASS="literallayout" -><br> - Here's an overview of what each table does. Most columns in each table have<br> -descriptive names that make it fairly trivial to figure out their jobs.<br> -<br> -attachments: This table stores all attachments to bugs. It tends to be your<br> -largest table, yet also generally has the fewest entries because file<br> -attachments are so (relatively) large.<br> -<br> -bugs: This is the core of your system. The bugs table stores most of the<br> -current information about a bug, with the exception of the info stored in the<br> -other tables.<br> -<br> -bugs_activity: This stores information regarding what changes are made to bugs<br> -when -- a history file.<br> -<br> -cc: This tiny table simply stores all the CC information for any bug which has<br> -any entries in the CC field of the bug. Note that, like most other tables in<br> -Bugzilla, it does not refer to users by their user names, but by their unique<br> -userid, stored as a primary key in the profiles table.<br> -<br> -components: This stores the programs and components (or products and<br> -components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"<br> -(product) field is the full name of the product, rather than some other unique<br> -identifier, like bug_id and user_id are elsewhere in the database.<br> -<br> -dependencies: Stores data about those cool dependency trees.<br> -<br> -fielddefs: A nifty table that defines other tables. For instance, when you<br> -submit a form that changes the value of "AssignedTo" this table allows<br> -translation to the actual field name "assigned_to" for entry into MySQL.<br> -<br> -groups: defines bitmasks for groups. A bitmask is a number that can uniquely<br> -identify group memberships. For instance, say the group that is allowed to<br> -tweak parameters is assigned a value of "1", the group that is allowed to edit<br> -users is assigned a "2", and the group that is allowed to create new groups is<br> -assigned the bitmask of "4". By uniquely combining the group bitmasks (much<br> -like the chmod command in UNIX,) you can identify a user is allowed to tweak<br> -parameters and create groups, but not edit users, by giving him a bitmask of<br> -"5", or a user allowed to edit users and create groups, but not tweak<br> -parameters, by giving him a bitmask of "6" Simple, huh?<br> - If this makes no sense to you, try this at the mysql prompt:<br> -mysql> select * from groups;<br> - You'll see the list, it makes much more sense that way.<br> -<br> -keyworddefs: Definitions of keywords to be used<br> -<br> -keywords: Unlike what you'd think, this table holds which keywords are<br> -associated with which bug id's.<br> -<br> -logincookies: This stores every login cookie ever assigned to you for every<br> -machine you've ever logged into Bugzilla from. Curiously, it never does any<br> -housecleaning -- I see cookies in this file I've not used for months. However,<br> -since Bugzilla never expires your cookie (for convenience' sake), it makes<br> -sense.<br> -<br> -longdescs: The meat of bugzilla -- here is where all user comments are stored!<br> -You've only got 2^24 bytes per comment (it's a mediumtext field), so speak<br> -sparingly -- that's only the amount of space the Old Testament from the Bible<br> -would take (uncompressed, 16 megabytes). Each comment is keyed to the<br> -bug_id to which it's attached, so the order is necessarily chronological, for<br> -comments are played back in the order in which they are received.<br> -<br> -milestones: Interesting that milestones are associated with a specific product<br> -in this table, but Bugzilla does not yet support differing milestones by<br> -product through the standard configuration interfaces.<br> -<br> -namedqueries: This is where everybody stores their "custom queries". Very<br> -cool feature; it beats the tar out of having to bookmark each cool query you<br> -construct.<br> -<br> -products: What products you have, whether new bug entries are allowed for the<br> -product, what milestone you're working toward on that product, votes, etc. It<br> -will be nice when the components table supports these same features, so you<br> -could close a particular component for bug entry without having to close an<br> -entire product...<br> -<br> -profiles: Ahh, so you were wondering where your precious user information was<br> -stored? Here it is! With the passwords in plain text for all to see! (but<br> -sshh... don't tell your users!)<br> -<br> -profiles_activity: Need to know who did what when to who's profile? This'll<br> -tell you, it's a pretty complete history.<br> -<br> -versions: Version information for every product<br> -<br> -votes: Who voted for what when<br> -<br> -watch: Who (according to userid) is watching who's bugs (according to their<br> -userid).<br> -<br> -<br> -===<br> -THE DETAILS<br> -===<br> -<br> - Ahh, so you're wondering just what to do with the information above? At the<br> -mysql prompt, you can view any information about the columns in a table with<br> -this command (where "table" is the name of the table you wish to view):<br> -<br> -mysql> show columns from table;<br> -<br> - You can also view all the data in a table with this command:<br> -<br> -mysql> select * from table;<br> -<br> - -- note: this is a very bad idea to do on, for instance, the "bugs" table if<br> -you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or<br> -50,000 bugs play across your screen.<br> -<br> - You can limit the display from above a little with the command, where<br> -"column" is the name of the column for which you wish to restrict information:<br> -<br> -mysql> select * from table where (column = "some info");<br> -<br> - -- or the reverse of this<br> -<br> -mysql> select * from table where (column != "some info");<br> -<br> - Let's take our example from the introduction, and assume you need to change<br> -the word "verified" to "approved" in the resolution field. We know from the<br> -above information that the resolution is likely to be stored in the "bugs"<br> -table. Note we'll need to change a little perl code as well as this database<br> -change, but I won't plunge into that in this document. Let's verify the<br> -information is stored in the "bugs" table:<br> -<br> -mysql> show columns from bugs<br> -<br> - (exceedingly long output truncated here)<br> -| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||<br> -<br> - Sorry about that long line. We see from this that the "bug status" column is<br> -an "enum field", which is a MySQL peculiarity where a string type field can<br> -only have certain types of entries. While I think this is very cool, it's not<br> -standard SQL. Anyway, we need to add the possible enum field entry<br> -'APPROVED' by altering the "bugs" table.<br> -<br> -mysql> ALTER table bugs CHANGE bug_status bug_status<br> - -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",<br> - -> "VERIFIED", "APPROVED", "CLOSED") not null;<br> -<br> - (note we can take three lines or more -- whatever you put in before the<br> -semicolon is evaluated as a single expression)<br> -<br> -Now if you do this:<br> -<br> -mysql> show columns from bugs;<br> -<br> - you'll see that the bug_status field has an extra "APPROVED" enum that's<br> -available! Cool thing, too, is that this is reflected on your query page as<br> -well -- you can query by the new status. But how's it fit into the existing<br> -scheme of things?<br> - Looks like you need to go back and look for instances of the word "verified"<br> -in the perl code for Bugzilla -- wherever you find "verified", change it to<br> -"approved" and you're in business (make sure that's a case-insensitive search).<br> -Although you can query by the enum field, you can't give something a status<br> -of "APPROVED" until you make the perl changes. Note that this change I<br> -mentioned can also be done by editing checksetup.pl, which automates a lot of<br> -this. But you need to know this stuff anyway, right?<br> - </P -></DIV -></DIV -></DIV -></DIV -><DIV -CLASS="appendix" -><HR><H1 -><A NAME="patches" ></A ->Appendix C. Useful Patches and Utilities for Bugzilla</H1 +>Appendix B. Contrib</H1 ><P ->Are you looking for a way to put your Bugzilla into overdrive? Catch - some of the niftiest tricks here in this section.</P -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="rewrite" -></A ->C.1. Apache - <TT -CLASS="filename" ->mod_rewrite</TT -> - - magic</H1 -><P ->Apache's - <TT +>There are a number of unofficial Bugzilla add-ons in the + <TT CLASS="filename" ->mod_rewrite</TT +>$BUGZILLA_ROOT/contrib/</TT > - - module lets you do some truly amazing things with URL rewriting. Here are - a couple of examples of what you can do.</P -><P -></P -><OL -TYPE="1" -><LI -><P ->Make it so if someone types - <TT -CLASS="computeroutput" ->http://www.foo.com/12345</TT -> - - , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try - setting up your VirtualHost section for Bugzilla with a rule like - this:</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> <VirtualHost 12.34.56.78> -RewriteEngine On -RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] -</VirtualHost> -</PRE -></FONT -></TD -></TR -></TABLE -></LI -><LI -><P ->There are many, many more things you can do with mod_rewrite. - Please refer to the mod_rewrite documentation at - <A -HREF="http://www.apache.org" -TARGET="_top" ->http://www.apache.org</A ->. - </P -></LI -></OL -></DIV + directory. This section documents them.</P ><DIV CLASS="section" ><HR><H1 @@ -13051,9 +11963,9 @@ CLASS="section" ><A NAME="cmdline" ></A ->C.2. Command-line Bugzilla Queries</H1 +>B.1. Command-line Search Interface</H1 ><P ->There are a suite of Unix utilities for querying Bugzilla from the +>There are a suite of Unix utilities for searching Bugzilla from the command line. They live in the <TT CLASS="filename" @@ -13131,169 +12043,13 @@ CLASS="command" CLASS="appendix" ><HR><H1 ><A -NAME="variants" -></A ->Appendix D. Bugzilla Variants and Competitors</H1 -><P ->I created this section to answer questions about Bugzilla competitors - and variants, then found a wonderful site which covers an awful lot of what - I wanted to discuss. Rather than quote it in its entirety, I'll simply - refer you here: - <A -HREF="http://linas.org/linux/pm.html" -TARGET="_top" ->http://linas.org/linux/pm.html</A ->. - </P -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-redhat" -></A ->D.1. Red Hat Bugzilla</H1 -><P ->Red Hat's old fork of Bugzilla which was based on version 2.8 is now - obsolete. The newest version in use is based on version 2.17.1 and is in - the process of being integrated into the main Bugzilla source tree. The - back-end is modified to work with PostgreSQL instead of MySQL and they have - custom templates to get their desired look and feel, but other than that it - is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of - effort to make sure that the changes he made could be integrated back into - the main tree. - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304" -TARGET="_top" ->Bug 98304</A -> - exists to track this integration. - </P -><P ->URL: <A -HREF="http://bugzilla.redhat.com/bugzilla/" -TARGET="_top" ->http://bugzilla.redhat.com/bugzilla/</A -> - </P -><P ->This section last updated 24 Dec 2002</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-fenris" -></A ->D.2. Loki Bugzilla (Fenris)</H1 -><P ->Fenris was a fork from Bugzilla made by Loki Games; when - Loki went into receivership, it died. While Loki's other code lives on, - its custodians recommend Bugzilla for future bug-tracker deployments. - </P -><P ->This section last updated 27 Jul 2002</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-issuezilla" -></A ->D.3. Issuezilla</H1 -><P ->Issuezilla was another fork from Bugzilla, made by collab.net and - hosted at tigris.org. It is also dead; the primary focus of bug-tracking - at tigris.org is their Java-based bug-tracker, - <A -HREF="#variant-scarab" ->Section D.4</A ->.</P -><P ->This section last updated 27 Jul 2002</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-scarab" -></A ->D.4. Scarab</H1 -><P ->Scarab is a new open source bug-tracking system built using Java - Servlet technology. It is currently at version 1.0 beta 13.</P -><P ->URL: <A -HREF="http://scarab.tigris.org/" -TARGET="_top" ->http://scarab.tigris.org/</A -> - </P -><P ->This section last updated 18 Jan 2003</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-perforce" -></A ->D.5. Perforce SCM</H1 -><P ->Although Perforce isn't really a bug tracker, it can be used as - such through the <SPAN -CLASS="QUOTE" ->"jobs"</SPAN -> - functionality.</P -><P ->URL: <A -HREF="http://www.perforce.com/perforce/technotes/note052.html" -TARGET="_top" ->http://www.perforce.com/perforce/technotes/note052.html</A -> - </P -><P ->This section last updated 27 Jul 2002</P -></DIV -><DIV -CLASS="section" -><HR><H1 -CLASS="section" -><A -NAME="variant-sourceforge" -></A ->D.6. SourceForge</H1 -><P ->SourceForge is a way of coordinating geographically - distributed free software and open source projects over the Internet. - It has a built-in bug tracker, but it's not highly thought of.</P -><P ->URL: <A -HREF="http://www.sourceforge.net" -TARGET="_top" ->http://www.sourceforge.net</A -> - </P -><P ->This section last updated 27 Jul 2002</P -></DIV -></DIV -><DIV -CLASS="appendix" -><HR><H1 -><A NAME="gfdl" ></A ->Appendix E. GNU Free Documentation License</H1 +>Appendix C. GNU Free Documentation License</H1 ><P >Version 1.1, March 2000</P ><A -NAME="AEN2394" +NAME="AEN2192" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -13756,7 +12512,7 @@ NAME="gfdl-howto" of the License in the document and put the following copyright and license notices just after the title page:</P ><A -NAME="AEN2484" +NAME="AEN2282" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -13793,7 +12549,7 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="AEN2489" +NAME="AEN2287" ></A >0-9, high ascii</H1 ><DL @@ -13963,7 +12719,7 @@ TARGET="_top" >For more information about how to configure Apache for Bugzilla, see <A HREF="#http-apache" ->Section 4.4.1</A +>Section 4.2.1</A >. </P ></DD @@ -14356,7 +13112,7 @@ TARGET="_top" >Much more detailed information about the suggestions in <A HREF="#security-mysql" ->Section 5.6.2</A +>Section 4.5.2</A >. </P ></DD @@ -14657,7 +13413,7 @@ NAME="gloss-zarro" Terry had the following to say: </P ><A -NAME="AEN2724" +NAME="AEN2522" ></A ><TABLE BORDER="0" diff --git a/docs/html/about.html b/docs/html/about.html index 3d5d1b9ae..ea3fa5bc3 100644 --- a/docs/html/about.html +++ b/docs/html/about.html @@ -4,12 +4,15 @@ >About This Guide</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="NEXT" TITLE="Copyright Information" @@ -33,7 +36,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -150,7 +154,8 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->The Bugzilla Guide - 2.17.5 Development Release</TD +>The Bugzilla Guide - 2.17.5 + Development Release</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/administration.html b/docs/html/administration.html index 44c45eb87..eec432e39 100644 --- a/docs/html/administration.html +++ b/docs/html/administration.html @@ -4,9 +4,11 @@ >Administering Bugzilla</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Troubleshooting" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -104,145 +107,39 @@ HREF="useradmin.html#manageusers" ></DD ><DT >5.3. <A -HREF="programadmin.html" ->Product, Component, Milestone, and Version Administration</A -></DT -><DD -><DL -><DT ->5.3.1. <A -HREF="programadmin.html#products" +HREF="products.html" >Products</A ></DT ><DT ->5.3.2. <A -HREF="programadmin.html#components" +>5.4. <A +HREF="components.html" >Components</A ></DT ><DT ->5.3.3. <A -HREF="programadmin.html#versions" +>5.5. <A +HREF="versions.html" >Versions</A ></DT ><DT ->5.3.4. <A -HREF="programadmin.html#milestones" +>5.6. <A +HREF="milestones.html" >Milestones</A ></DT -></DL -></DD ><DT ->5.4. <A +>5.7. <A HREF="voting.html" >Voting</A ></DT ><DT ->5.5. <A +>5.8. <A HREF="groups.html" >Groups and Group Security</A ></DT ><DT ->5.6. <A -HREF="security.html" ->Bugzilla Security</A -></DT -><DD -><DL -><DT ->5.6.1. <A -HREF="security.html#security-networking" ->TCP/IP Ports</A -></DT -><DT ->5.6.2. <A -HREF="security.html#security-mysql" ->MySQL</A -></DT -><DT ->5.6.3. <A -HREF="security.html#security-daemon" ->Daemon Accounts</A -></DT -><DT ->5.6.4. <A -HREF="security.html#security-access" ->Web Server Access Controls</A -></DT -></DL -></DD -><DT ->5.7. <A -HREF="cust-templates.html" ->Template Customization</A -></DT -><DD -><DL -><DT ->5.7.1. <A -HREF="cust-templates.html#AEN1606" ->What to Edit</A -></DT -><DT ->5.7.2. <A -HREF="cust-templates.html#AEN1629" ->How To Edit Templates</A -></DT -><DT ->5.7.3. <A -HREF="cust-templates.html#AEN1639" ->Template Formats</A -></DT -><DT ->5.7.4. <A -HREF="cust-templates.html#AEN1652" ->Particular Templates</A -></DT -><DT ->5.7.5. <A -HREF="cust-templates.html#template-http-accept" ->Configuring Bugzilla to Detect the User's Language</A -></DT -></DL -></DD -><DT ->5.8. <A -HREF="cust-change-permissions.html" ->Change Permission Customization</A -></DT -><DT >5.9. <A HREF="upgrading.html" >Upgrading to New Releases</A ></DT -><DT ->5.10. <A -HREF="integration.html" ->Integrating Bugzilla with Third-Party Tools</A -></DT -><DD -><DL -><DT ->5.10.1. <A -HREF="integration.html#bonsai" ->Bonsai</A -></DT -><DT ->5.10.2. <A -HREF="integration.html#cvs" ->CVS</A -></DT -><DT ->5.10.3. <A -HREF="integration.html#scm" ->Perforce SCM</A -></DT -><DT ->5.10.4. <A -HREF="integration.html#tinderbox" ->Tinderbox/Tinderbox2</A -></DT -></DL -></DD ></DL ></DIV ></DIV diff --git a/docs/html/bug_page.html b/docs/html/bug_page.html new file mode 100644 index 000000000..ece7524cd --- /dev/null +++ b/docs/html/bug_page.html @@ -0,0 +1,404 @@ +<HTML +><HEAD +><TITLE +>Anatomy of a Bug</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Create a Bugzilla Account" +HREF="myaccount.html"><LINK +REL="NEXT" +TITLE="Searching for Bugs" +HREF="query.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="myaccount.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="query.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="bug_page" +></A +>3.2. Anatomy of a Bug</H1 +><P +>The core of Bugzilla is the screen which displays a particular + bug. It's a good place to explain some Bugzilla concepts. + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1" +TARGET="_top" +> Bug 1 on Landfill</A +> + + 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.</P +><P +></P +><OL +TYPE="1" +><LI +><P +> <EM +>Product and Component</EM +>: + Bugs are divided up by Product and Component, with a Product + having one or more Components in it. For example, + bugzilla.mozilla.org's "Bugzilla" Product is composed of several + Components: + <P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +> <EM +>Administration:</EM +> + Administration of a Bugzilla installation.</TD +></TR +><TR +><TD +> <EM +>Bugzilla-General:</EM +> + Anything that doesn't fit in the other components, or spans + multiple components.</TD +></TR +><TR +><TD +> <EM +>Creating/Changing Bugs:</EM +> + Creating, changing, and viewing bugs.</TD +></TR +><TR +><TD +> <EM +>Documentation:</EM +> + The Bugzilla documentation, including The Bugzilla Guide.</TD +></TR +><TR +><TD +> <EM +>Email:</EM +> + Anything to do with email sent by Bugzilla.</TD +></TR +><TR +><TD +> <EM +>Installation:</EM +> + The installation process of Bugzilla.</TD +></TR +><TR +><TD +> <EM +>Query/Buglist:</EM +> + Anything to do with searching for bugs and viewing the + buglists.</TD +></TR +><TR +><TD +> <EM +>Reporting/Charting:</EM +> + Getting reports from Bugzilla.</TD +></TR +><TR +><TD +> <EM +>User Accounts:</EM +> + Anything about managing a user account from the user's perspective. + Saved queries, creating accounts, changing passwords, logging in, + etc.</TD +></TR +><TR +><TD +> <EM +>User Interface:</EM +> + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, + etc.</TD +></TR +></TBODY +></TABLE +><P +></P +> + </P +></LI +><LI +><P +> <EM +>Status and Resolution:</EM +> + + 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.</P +></LI +><LI +><P +> <EM +>Assigned To:</EM +> + The person responsible for fixing the bug.</P +></LI +><LI +><P +> <EM +>*URL:</EM +> + A URL associated with the bug, if any.</P +></LI +><LI +><P +> <EM +>Summary:</EM +> + A one-sentence summary of the problem.</P +></LI +><LI +><P +> <EM +>*Status Whiteboard:</EM +> + (a.k.a. Whiteboard) A free-form text area for adding short notes + and tags to a bug.</P +></LI +><LI +><P +> <EM +>*Keywords:</EM +> + The administrator can define keywords which you can use to tag and + categorise bugs - e.g. The Mozilla Project has keywords like crash + and regression.</P +></LI +><LI +><P +> <EM +>Platform and OS:</EM +> + These indicate the computing environment where the bug was + found.</P +></LI +><LI +><P +> <EM +>Version:</EM +> + The "Version" field is usually used for versions of a product which + have been released, and is set to indicate which versions of a + Component have the particular problem the bug report is + about.</P +></LI +><LI +><P +> <EM +>Priority:</EM +> + The bug assignee uses this field to prioritise his or her bugs. + It's a good idea not to change this on other people's bugs.</P +></LI +><LI +><P +> <EM +>Severity:</EM +> + This indicates how severe the problem is - from blocker + ("application unusable") to trivial ("minor cosmetic issue"). You + can also use this field to indicate whether a bug is an enhancement + request.</P +></LI +><LI +><P +> <EM +>*Target:</EM +> + (a.k.a. Target Milestone) A future version by which the bug is to + be fixed. e.g. The Bugzilla Project's milestones for future + Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not + restricted to numbers, thought - you can use any text strings, such + as dates.</P +></LI +><LI +><P +> <EM +>Reporter:</EM +> + The person who filed the bug.</P +></LI +><LI +><P +> <EM +>CC list:</EM +> + A list of people who get mail when the bug changes.</P +></LI +><LI +><P +> <EM +>Attachments:</EM +> + You can attach files (e.g. testcases or patches) to bugs. If there + are any attachments, they are listed in this section.</P +></LI +><LI +><P +> <EM +>*Dependencies:</EM +> + If this bug cannot be fixed unless other bugs are fixed (depends + on), or this bug stops other bugs being fixed (blocks), their + numbers are recorded here.</P +></LI +><LI +><P +> <EM +>*Votes:</EM +> + Whether this bug has any votes.</P +></LI +><LI +><P +> <EM +>Additional Comments:</EM +> + You can add your two cents to the bug discussion here, if you have + something worthwhile to say.</P +></LI +></OL +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="myaccount.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="query.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Create a Bugzilla Account</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Searching for Bugs</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/bugreports.html b/docs/html/bugreports.html new file mode 100644 index 000000000..91df7f3ba --- /dev/null +++ b/docs/html/bugreports.html @@ -0,0 +1,197 @@ +<HTML +><HEAD +><TITLE +>Filing Bugs</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Bug Lists" +HREF="list.html"><LINK +REL="NEXT" +TITLE="Patch Viewer" +HREF="patchviewer.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="list.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="patchviewer.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="bugreports" +></A +>3.5. Filing Bugs</H1 +><P +>Years of bug writing experience has been distilled for your + reading pleasure into the + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html" +TARGET="_top" +> Bug Writing Guidelines</A +>. + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you.</P +><P +>The procedure for filing a test bug is as follows:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>Go to + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/" +TARGET="_top" +> Landfill</A +> + in your browser and click + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi" +TARGET="_top" +> Enter a new bug report</A +>. + </P +></LI +><LI +><P +>Select a product - any one will do.</P +></LI +><LI +><P +>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.</P +></LI +><LI +><P +>Select "Commit" and send in your bug report.</P +></LI +></OL +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="list.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="patchviewer.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Bug Lists</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Patch Viewer</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/cmdline.html b/docs/html/cmdline.html index 70af1510a..be3ee0a5e 100644 --- a/docs/html/cmdline.html +++ b/docs/html/cmdline.html @@ -1,25 +1,24 @@ <HTML ><HEAD ><TITLE ->Command-line Bugzilla Queries</TITLE +>Command-line Search Interface</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="Useful Patches and Utilities for Bugzilla" +TITLE="Contrib" HREF="patches.html"><LINK REL="PREVIOUS" -TITLE="Apache - mod_rewrite - - magic" -HREF="rewrite.html"><LINK +TITLE="Contrib" +HREF="patches.html"><LINK REL="NEXT" -TITLE="Bugzilla Variants and Competitors" -HREF="variants.html"></HEAD +TITLE="GNU Free Documentation License" +HREF="gfdl.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -39,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -47,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="rewrite.html" +HREF="patches.html" ACCESSKEY="P" >Prev</A ></TD @@ -55,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix C. Useful Patches and Utilities for Bugzilla</TD +>Appendix B. Contrib</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="variants.html" +HREF="gfdl.html" ACCESSKEY="N" >Next</A ></TD @@ -77,9 +77,9 @@ CLASS="section" ><A NAME="cmdline" ></A ->C.2. Command-line Bugzilla Queries</H1 +>B.1. Command-line Search Interface</H1 ><P ->There are a suite of Unix utilities for querying Bugzilla from the +>There are a suite of Unix utilities for searching Bugzilla from the command line. They live in the <TT CLASS="filename" @@ -168,7 +168,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="rewrite.html" +HREF="patches.html" ACCESSKEY="P" >Prev</A ></TD @@ -186,7 +186,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="variants.html" +HREF="gfdl.html" ACCESSKEY="N" >Next</A ></TD @@ -196,13 +196,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Apache - <TT -CLASS="filename" ->mod_rewrite</TT -> - - magic</TD +>Contrib</TD ><TD WIDTH="34%" ALIGN="center" @@ -216,7 +210,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Bugzilla Variants and Competitors</TD +>GNU Free Documentation License</TD ></TR ></TABLE ></DIV diff --git a/docs/html/components.html b/docs/html/components.html new file mode 100644 index 000000000..78328e004 --- /dev/null +++ b/docs/html/components.html @@ -0,0 +1,192 @@ +<HTML +><HEAD +><TITLE +>Components</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Administering Bugzilla" +HREF="administration.html"><LINK +REL="PREVIOUS" +TITLE="Products" +HREF="products.html"><LINK +REL="NEXT" +TITLE="Versions" +HREF="versions.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="products.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 5. Administering Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="versions.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="components" +></A +>5.4. Components</H1 +><P +>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.</P +><P +> 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 + <EM +>default assignments</EM +>; + these can be changed on bug submission, or at any later point in + a bug's life.</P +><P +>To create a new Component:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>Select the "Edit components" link from the "Edit product" + page</P +></LI +><LI +><P +>Select the "Add" link in the bottom right.</P +></LI +><LI +><P +>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. + </P +></LI +></OL +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="products.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="versions.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Products</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="administration.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Versions</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/conventions.html b/docs/html/conventions.html index 5ba3317d3..d646b30ef 100644 --- a/docs/html/conventions.html +++ b/docs/html/conventions.html @@ -4,9 +4,11 @@ >Document Conventions</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="About This Guide" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -80,7 +83,7 @@ NAME="conventions" ><DIV CLASS="informaltable" ><A -NAME="AEN113" +NAME="AEN73" ></A ><P ></P @@ -252,7 +255,7 @@ VALIGN="TOP" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->File Names</TD +>File and directory names</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -266,20 +269,6 @@ CLASS="filename" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Directory Names</TD -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" -> <TT -CLASS="filename" ->directory</TT -> - </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" >Commands to be typed</TD ><TD ALIGN="LEFT" @@ -294,7 +283,7 @@ CLASS="command" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Applications Names</TD +>Applications names</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -353,7 +342,7 @@ VALIGN="MIDDLE" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Environment Variables</TD +>Environment variables</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -367,19 +356,6 @@ CLASS="envar" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Emphasized word</TD -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" -> <EM ->word</EM -> - </TD -></TR -><TR -><TD -ALIGN="LEFT" -VALIGN="MIDDLE" >Term found in the glossary</TD ><TD ALIGN="LEFT" @@ -397,7 +373,7 @@ CLASS="glossterm" ><TD ALIGN="LEFT" VALIGN="MIDDLE" ->Code Example</TD +>Code example</TD ><TD ALIGN="LEFT" VALIGN="MIDDLE" @@ -432,6 +408,16 @@ CLASS="sgmltag" ><P ></P ></DIV +><P +> + 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 the <A +HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" +TARGET="_top" +>Bugzilla Documentation</A +> component. + </P ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/copyright.html b/docs/html/copyright.html index 268851857..fbad50967 100644 --- a/docs/html/copyright.html +++ b/docs/html/copyright.html @@ -4,9 +4,11 @@ >Copyright Information</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="About This Guide" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -76,7 +79,7 @@ NAME="copyright" ></A >1.1. Copyright Information</H1 ><A -NAME="AEN35" +NAME="AEN25" ></A ><TABLE BORDER="0" @@ -100,7 +103,7 @@ VALIGN="TOP" Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in <A HREF="gfdl.html" ->Appendix E</A +>Appendix C</A >. </P ></TD @@ -116,7 +119,7 @@ ALIGN="RIGHT" VALIGN="TOP" >--<SPAN CLASS="attribution" ->Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team</SPAN +>Copyright (c) 2000-2004 The Bugzilla Team</SPAN ></TD ><TD WIDTH="10%" @@ -126,7 +129,7 @@ WIDTH="10%" ><P > If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, - please contact The Bugzilla Team. + please contact the Bugzilla Team. </P ></DIV ><DIV diff --git a/docs/html/credits.html b/docs/html/credits.html index 5993eebeb..82a63e518 100644 --- a/docs/html/credits.html +++ b/docs/html/credits.html @@ -4,9 +4,11 @@ >Credits</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="About This Guide" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -82,116 +85,18 @@ NAME="credits" contribution to the Bugzilla community: </P ><P -></P -><DIV -CLASS="variablelist" -><DL -><DT ->Matthew P. Barnson <TT -CLASS="email" -><<A -HREF="mailto:mbarnson@sisna.com" ->mbarnson@sisna.com</A ->></TT -></DT -><DD -><P ->for the Herculaean task of pulling together the Bugzilla Guide - and shepherding it to 2.14. - </P -></DD -><DT ->Terry Weissman <TT -CLASS="email" -><<A -HREF="mailto:terry@mozilla.org" ->terry@mozilla.org</A ->></TT -></DT -><DD -><P ->for initially writing Bugzilla and creating the README upon - which the UNIX installation documentation is largely based. - </P -></DD -><DT ->Tara Hernandez <TT -CLASS="email" -><<A -HREF="mailto:tara@tequilarists.org" ->tara@tequilarists.org</A ->></TT -></DT -><DD -><P ->for keeping Bugzilla development going strong after Terry left - mozilla.org and for running landfill. - </P -></DD -><DT ->Dave Lawrence <TT -CLASS="email" -><<A -HREF="mailto:dkl@redhat.com" ->dkl@redhat.com</A ->></TT -></DT -><DD -><P ->for providing insight into the key differences between Red - Hat's customized Bugzilla, and being largely responsible for - <A -HREF="variant-redhat.html" ->Section D.1</A ->. - </P -></DD -><DT ->Dawn Endico <TT -CLASS="email" -><<A -HREF="mailto:endico@mozilla.org" ->endico@mozilla.org</A ->></TT -></DT -><DD -><P ->for being a hacker extraordinaire and putting up with Matthew's - incessant questions and arguments on irc.mozilla.org in #mozwebtools - </P -></DD -><DT ->Jacob Steenhagen <TT -CLASS="email" -><<A -HREF="mailto:jake@bugzilla.org" ->jake@bugzilla.org</A ->></TT -></DT -><DD -><P ->for taking over documentation during the 2.17 development - period. - </P -></DD -></DL -></DIV +> Matthew P. Barnson, Kevin Brannen, Dawn Endico, Ben FrantzDale, Eric Hanson, Tara Hernandez, Dave Lawrence, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Jacob Steenhagen, Ron Teitelbaum, Terry Weissman, Martin Wulffeld. + </P ><P > Last but not least, all the members of the <A HREF="news://news.mozilla.org/netscape/public/mozilla/webtools" TARGET="_top" ->news://news.mozilla.org/netscape/public/mozilla/webtools</A +> netscape.public.mozilla.webtools</A > newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened. </P -><P -> Thanks also go to the following people for significant contributions - to this documentation (in alphabetical order): - Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Martin Wulffeld, Ron Teitelbaum, Spencer Smith, Zach Liption - . - </P ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/cust-change-permissions.html b/docs/html/cust-change-permissions.html index cb123985d..65f627919 100644 --- a/docs/html/cust-change-permissions.html +++ b/docs/html/cust-change-permissions.html @@ -1,22 +1,24 @@ <HTML ><HEAD ><TITLE ->Change Permission Customization</TITLE +>Customizing Who Can Change What</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="Administering Bugzilla" -HREF="administration.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="PREVIOUS" TITLE="Template Customization" HREF="cust-templates.html"><LINK REL="NEXT" -TITLE="Upgrading to New Releases" -HREF="upgrading.html"></HEAD +TITLE="Modifying Your Running System" +HREF="dbmodify.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 5. Administering Bugzilla</TD +>Chapter 6. Customising Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="upgrading.html" +HREF="dbmodify.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="cust-change-permissions" ></A ->5.8. Change Permission Customization</H1 +>6.2. Customizing Who Can Change What</H1 ><DIV CLASS="warning" ><P @@ -98,9 +101,10 @@ VALIGN="TOP" ><P > This feature should be considered experimental; the Bugzilla code you will be changing is not stable, and could change or move between - versions. Be aware that if you make modifications to it, you may have + versions. Be aware that if you make modifications as outlined here, + you may have to re-make them or port them if Bugzilla changes internally between - versions. + versions, and you upgrade. </P ></TD ></TR @@ -272,7 +276,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="upgrading.html" +HREF="dbmodify.html" ACCESSKEY="N" >Next</A ></TD @@ -288,7 +292,7 @@ WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="administration.html" +HREF="customization.html" ACCESSKEY="U" >Up</A ></TD @@ -296,7 +300,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Upgrading to New Releases</TD +>Modifying Your Running System</TD ></TR ></TABLE ></DIV diff --git a/docs/html/cust-templates.html b/docs/html/cust-templates.html index a981513c8..c905e3031 100644 --- a/docs/html/cust-templates.html +++ b/docs/html/cust-templates.html @@ -4,18 +4,20 @@ >Template Customization</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="Administering Bugzilla" -HREF="administration.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="PREVIOUS" -TITLE="Bugzilla Security" -HREF="security.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="NEXT" -TITLE="Change Permission Customization" +TITLE="Customizing Who Can Change What" HREF="cust-change-permissions.html"></HEAD ><BODY CLASS="section" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="security.html" +HREF="customization.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 5. Administering Bugzilla</TD +>Chapter 6. Customising Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" @@ -74,27 +77,19 @@ CLASS="section" ><A NAME="cust-templates" ></A ->5.7. Template Customization</H1 +>6.1. Template Customization</H1 ><P -> One of the large changes for 2.16 was the templatization of the - entire user-facing UI, using the - <A -HREF="http://www.template-toolkit.org" -TARGET="_top" ->Template Toolkit</A ->. - Administrators can now configure the look and feel of Bugzilla without +> Administrators can 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. </P ><P > Templatization also makes localized versions of Bugzilla possible, - for the first time. As of version 2.17.4 which will soon - become 2.18, it's possible to have Bugzilla's language determined by - the user's browser. More information is available in + for the first time. It's possible to have Bugzilla's UI language + determined by the user's browser. More information is available in <A HREF="cust-templates.html#template-http-accept" ->Section 5.7.5</A +>Section 6.1.5</A >. </P ><DIV @@ -102,13 +97,11 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1606" +NAME="AEN1597" ></A ->5.7.1. What to Edit</H2 +>6.1.1. What to Edit</H2 ><P -> There are two different ways of editing of Bugzilla's templates, - and which you use depends mainly on how you upgrade Bugzilla. The - template directory structure is that there's a top level directory, +> The template directory structure is that there's a top level directory, <TT CLASS="filename" >template</TT @@ -137,7 +130,10 @@ CLASS="filename" must be created if you want to use it. </P ><P -> The first method of making customizations is to directly edit the +> There are two different ways of editing Bugzilla's templates, + and which you use depends mainly on the method you plan to use to + upgrade Bugzilla. + The first method of making customizations is to directly edit the templates in <TT CLASS="filename" >template/en/default</TT @@ -155,7 +151,8 @@ CLASS="command" occur. </P ><P -> The other method is to copy the templates into a mirrored directory +> The other method is to copy the templates to be modified into a + mirrored directory structure under <TT CLASS="filename" >template/en/custom</TT @@ -252,47 +249,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1629" +NAME="AEN1620" ></A ->5.7.2. How To Edit Templates</H2 -><P -> The syntax of the Template Toolkit language is beyond the scope of - this guide. It's reasonably easy to pick up by looking at the current - templates; or, you can read the manual, available on the - <A -HREF="http://www.template-toolkit.org" -TARGET="_top" ->Template Toolkit home - page</A ->. 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. - </P -><P -> 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 &lt;. 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. - </P -><P -> 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. - </P -><P -> 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. - </P +>6.1.2. How To Edit Templates</H2 ><DIV CLASS="note" ><P @@ -328,15 +287,51 @@ TARGET="_top" ></TR ></TABLE ></DIV +><P +> The syntax of the Template Toolkit language is beyond the scope of + this guide. It's reasonably easy to pick up by looking at the current + templates; or, you can read the manual, available on the + <A +HREF="http://www.template-toolkit.org" +TARGET="_top" +>Template Toolkit home + page</A +>. + </P +><P +> 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 &lt;. You use the 'html' filter in the + Template Toolkit to do this. If you forget, you may open up + your installation to cross-site scripting attacks. + </P +><P +> 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. + </P +><P +> 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. + </P ></DIV ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1639" +NAME="AEN1630" ></A ->5.7.3. Template Formats</H2 +>6.1.3. Template Formats</H2 ><P > Some CGIs have the ability to use more than one template. For example, buglist.cgi can output bug lists as RDF or two @@ -350,9 +345,9 @@ CLASS="filename" </P ><P > To see if a CGI supports multiple output formats, grep the - CGI for "ValidateOutputFormat". If it's not present, adding + CGI for "GetFormat". If it's not present, adding multiple format support isn't too hard - see how it's done in - other CGIs. + other CGIs, e.g. config.cgi. </P ><P > To make a new format template for a CGI which supports this, @@ -396,9 +391,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1652" +NAME="AEN1643" ></A ->5.7.4. Particular Templates</H2 +>6.1.4. Particular Templates</H2 ><P > There are a few templates you may be particularly interested in customizing for your installation. @@ -454,21 +449,6 @@ CLASS="command" ><P > <B CLASS="command" ->bug/process/midair.html.tmpl</B ->: - This is the page used if two people submit simultaneous changes to the - same bug. The second person to submit their changes will get this page - to tell them what the first person did, and ask if they wish to - overwrite those changes or go back and revisit the bug. The default - title and header on this page read "Mid-air collision detected!" If - you work in the aviation industry, or other environment where this - might be found offensive (yes, we have true stories of this happening) - you'll want to change this to something more appropriate for your - environment. - </P -><P -> <B -CLASS="command" >bug/create/create.html.tmpl</B > and <B @@ -587,13 +567,11 @@ CLASS="section" ><A NAME="template-http-accept" ></A ->5.7.5. Configuring Bugzilla to Detect the User's Language</H2 +>6.1.5. Configuring Bugzilla to Detect the User's Language</H2 ><P ->Begining in version 2.18 (first introduced in version - 2.17.4), it's now possible to have the users web browser tell Bugzilla - which language templates to use for each visitor (using the HTTP_ACCEPT - header). For this to work, Bugzilla needs to have the correct language - templates installed for the version of Bugzilla you are using. Many +>Bugzilla honours the user's Accept: HTTP header. You can install + templates in other languages, and Bugzilla will pick the most appropriate + according to a priority order defined by you. Many language templates can be obtained from <A HREF="http://www.bugzilla.org/download.html#localizations" TARGET="_top" @@ -605,7 +583,7 @@ TARGET="_top" >After untarring the localizations (or creating your own) in the <TT CLASS="filename" ->[Bugzilla_Root]/template</TT +>$BUGZILLA_HOME/template</TT > directory, you must update the <TT CLASS="option" @@ -639,7 +617,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="security.html" +HREF="customization.html" ACCESSKEY="P" >Prev</A ></TD @@ -667,13 +645,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Bugzilla Security</TD +>Customising Bugzilla</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="administration.html" +HREF="customization.html" ACCESSKEY="U" >Up</A ></TD @@ -681,7 +659,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Change Permission Customization</TD +>Customizing Who Can Change What</TD ></TR ></TABLE ></DIV diff --git a/docs/html/customization.html b/docs/html/customization.html new file mode 100644 index 000000000..006806b6a --- /dev/null +++ b/docs/html/customization.html @@ -0,0 +1,225 @@ +<HTML +><HEAD +><TITLE +>Customising Bugzilla</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="PREVIOUS" +TITLE="Upgrading to New Releases" +HREF="upgrading.html"><LINK +REL="NEXT" +TITLE="Template Customization" +HREF="cust-templates.html"></HEAD +><BODY +CLASS="chapter" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="upgrading.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +></TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="cust-templates.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="chapter" +><H1 +><A +NAME="customization" +></A +>Chapter 6. Customising Bugzilla</H1 +><DIV +CLASS="TOC" +><DL +><DT +><B +>Table of Contents</B +></DT +><DT +>6.1. <A +HREF="cust-templates.html" +>Template Customization</A +></DT +><DD +><DL +><DT +>6.1.1. <A +HREF="cust-templates.html#AEN1597" +>What to Edit</A +></DT +><DT +>6.1.2. <A +HREF="cust-templates.html#AEN1620" +>How To Edit Templates</A +></DT +><DT +>6.1.3. <A +HREF="cust-templates.html#AEN1630" +>Template Formats</A +></DT +><DT +>6.1.4. <A +HREF="cust-templates.html#AEN1643" +>Particular Templates</A +></DT +><DT +>6.1.5. <A +HREF="cust-templates.html#template-http-accept" +>Configuring Bugzilla to Detect the User's Language</A +></DT +></DL +></DD +><DT +>6.2. <A +HREF="cust-change-permissions.html" +>Customizing Who Can Change What</A +></DT +><DT +>6.3. <A +HREF="dbmodify.html" +>Modifying Your Running System</A +></DT +><DT +>6.4. <A +HREF="dbdoc.html" +>MySQL Bugzilla Database Introduction</A +></DT +><DT +>6.5. <A +HREF="integration.html" +>Integrating Bugzilla with Third-Party Tools</A +></DT +><DD +><DL +><DT +>6.5.1. <A +HREF="integration.html#bonsai" +>Bonsai</A +></DT +><DT +>6.5.2. <A +HREF="integration.html#cvs" +>CVS</A +></DT +><DT +>6.5.3. <A +HREF="integration.html#scm" +>Perforce SCM</A +></DT +><DT +>6.5.4. <A +HREF="integration.html#tinderbox" +>Tinderbox/Tinderbox2</A +></DT +></DL +></DD +></DL +></DIV +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="upgrading.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="cust-templates.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Upgrading to New Releases</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +> </TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Template Customization</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/database.html b/docs/html/database.html index d9bc26c2c..06e792a1c 100644 --- a/docs/html/database.html +++ b/docs/html/database.html @@ -4,16 +4,18 @@ >The Bugzilla Database</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="The Bugzilla FAQ" -HREF="faq.html"><LINK +TITLE="Integrating Bugzilla with Third-Party Tools" +HREF="integration.html"><LINK REL="NEXT" -TITLE="Modifying Your Running System" -HREF="dbmodify.html"></HEAD +TITLE="Template Customization" +HREF="cust-templates.html"></HEAD ><BODY CLASS="appendix" BGCOLOR="#FFFFFF" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -41,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="faq.html" +HREF="integration.html" ACCESSKEY="P" >Prev</A ></TD @@ -55,7 +58,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="dbmodify.html" +HREF="cust-templates.html" ACCESSKEY="N" >Next</A ></TD @@ -70,7 +73,7 @@ CLASS="appendix" ><A NAME="database" ></A ->Appendix B. The Bugzilla Database</H1 +>Appendix A. The Bugzilla Database</H1 ><DIV CLASS="TOC" ><DL @@ -79,12 +82,51 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->B.1. <A +>A.1. <A +HREF="cust-templates.html" +>Template Customization</A +></DT +><DD +><DL +><DT +>A.1.1. <A +HREF="cust-templates.html#AEN1667" +>What to Edit</A +></DT +><DT +>A.1.2. <A +HREF="cust-templates.html#AEN1690" +>How To Edit Templates</A +></DT +><DT +>A.1.3. <A +HREF="cust-templates.html#AEN1700" +>Template Formats</A +></DT +><DT +>A.1.4. <A +HREF="cust-templates.html#AEN1713" +>Particular Templates</A +></DT +><DT +>A.1.5. <A +HREF="cust-templates.html#template-http-accept" +>Configuring Bugzilla to Detect the User's Language</A +></DT +></DL +></DD +><DT +>A.2. <A +HREF="cust-change-permissions.html" +>Change Permission Customization</A +></DT +><DT +>A.3. <A HREF="dbmodify.html" >Modifying Your Running System</A ></DT ><DT ->B.2. <A +>A.4. <A HREF="dbdoc.html" >MySQL Bugzilla Database Introduction</A ></DT @@ -135,7 +177,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="faq.html" +HREF="integration.html" ACCESSKEY="P" >Prev</A ></TD @@ -153,7 +195,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="dbmodify.html" +HREF="cust-templates.html" ACCESSKEY="N" >Next</A ></TD @@ -163,7 +205,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->The Bugzilla FAQ</TD +>Integrating Bugzilla with Third-Party Tools</TD ><TD WIDTH="34%" ALIGN="center" @@ -173,7 +215,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Modifying Your Running System</TD +>Template Customization</TD ></TR ></TABLE ></DIV diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html index 8f250c0f6..73a7e61c4 100644 --- a/docs/html/dbdoc.html +++ b/docs/html/dbdoc.html @@ -4,19 +4,21 @@ >MySQL Bugzilla Database Introduction</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="The Bugzilla Database" -HREF="database.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="PREVIOUS" TITLE="Modifying Your Running System" HREF="dbmodify.html"><LINK REL="NEXT" -TITLE="Useful Patches and Utilities for Bugzilla" -HREF="patches.html"></HEAD +TITLE="Integrating Bugzilla with Third-Party Tools" +HREF="integration.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix B. The Bugzilla Database</TD +>Chapter 6. Customising Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="patches.html" +HREF="integration.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="dbdoc" ></A ->B.2. MySQL Bugzilla Database Introduction</H1 +>6.4. MySQL Bugzilla Database Introduction</H1 ><P >This information comes straight from my life. I was forced to learn how Bugzilla organizes database because of nitpicky requests from users @@ -134,9 +137,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN2279" +NAME="AEN1719" ></A ->B.2.1. Bugzilla Database Basics</H2 +>6.4.1. Bugzilla Database Basics</H2 ><P >If you were like me, at this point you're totally clueless about the internals of MySQL, and if it weren't for this executive order from @@ -248,9 +251,9 @@ CLASS="section" ><H3 CLASS="section" ><A -NAME="AEN2306" +NAME="AEN1746" ></A ->B.2.1.1. Bugzilla Database Tables</H3 +>6.4.1.1. Bugzilla Database Tables</H3 ><P >Imagine your MySQL database as a series of spreadsheets, and you won't be too far off. If you use this command:</P @@ -514,7 +517,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="patches.html" +HREF="integration.html" ACCESSKEY="N" >Next</A ></TD @@ -530,7 +533,7 @@ WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="database.html" +HREF="customization.html" ACCESSKEY="U" >Up</A ></TD @@ -538,7 +541,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Useful Patches and Utilities for Bugzilla</TD +>Integrating Bugzilla with Third-Party Tools</TD ></TR ></TABLE ></DIV diff --git a/docs/html/dbmodify.html b/docs/html/dbmodify.html index 5d52c3ac8..945408c47 100644 --- a/docs/html/dbmodify.html +++ b/docs/html/dbmodify.html @@ -4,16 +4,18 @@ >Modifying Your Running System</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="The Bugzilla Database" -HREF="database.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="PREVIOUS" -TITLE="The Bugzilla Database" -HREF="database.html"><LINK +TITLE="Customizing Who Can Change What" +HREF="cust-change-permissions.html"><LINK REL="NEXT" TITLE="MySQL Bugzilla Database Introduction" HREF="dbdoc.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="database.html" +HREF="cust-change-permissions.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix B. The Bugzilla Database</TD +>Chapter 6. Customising Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="dbmodify" ></A ->B.1. Modifying Your Running System</H1 +>6.3. Modifying Your Running System</H1 ><P >Bugzilla optimizes database lookups by storing all relatively static information in the @@ -132,7 +135,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="database.html" +HREF="cust-change-permissions.html" ACCESSKEY="P" >Prev</A ></TD @@ -160,13 +163,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->The Bugzilla Database</TD +>Customizing Who Can Change What</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="database.html" +HREF="customization.html" ACCESSKEY="U" >Up</A ></TD diff --git a/docs/html/disclaimer.html b/docs/html/disclaimer.html index 23e255785..2e0444066 100644 --- a/docs/html/disclaimer.html +++ b/docs/html/disclaimer.html @@ -4,9 +4,11 @@ >Disclaimer</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="About This Guide" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -77,7 +80,7 @@ NAME="disclaimer" >1.2. Disclaimer</H1 ><P > No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content at your own risk. + Follow the instructions herein 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 @@ -85,35 +88,20 @@ NAME="disclaimer" war. Proceed with caution. </P ><P -> 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. - </P -><P > 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, + wholeheartedly endorse the use of GNU/Linux; it is an extremely + versatile, stable, and robust operating system that offers an ideal operating environment for Bugzilla. </P ><P -> 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! - </P -><P > 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 + ensure that all exploitable bugs or options have been + fixed, security holes surely exist. Great care should be taken both in + the installation and usage of this software. The Bugzilla development + team members assume no liability for your use of this software. You have + the source code, and are responsible for auditing it yourself to ensure your security needs are met. </P ></DIV diff --git a/docs/html/extraconfig.html b/docs/html/extraconfig.html index ff8540d10..ea07c01c7 100644 --- a/docs/html/extraconfig.html +++ b/docs/html/extraconfig.html @@ -4,16 +4,18 @@ >Optional Additional Configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Installation" HREF="installation.html"><LINK REL="PREVIOUS" -TITLE="Step-by-step Install" -HREF="stepbystep.html"><LINK +TITLE="HTTP Server Configuration" +HREF="http.html"><LINK REL="NEXT" TITLE="OS Specific Installation Notes" HREF="os-specific.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="stepbystep.html" +HREF="http.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,15 +77,15 @@ CLASS="section" ><A NAME="extraconfig" ></A ->4.2. Optional Additional Configuration</H1 +>4.3. Optional Additional Configuration</H1 ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN832" +NAME="AEN852" ></A ->4.2.1. Dependency Charts</H2 +>4.3.1. Dependency Charts</H2 ><P >As well as the text-based dependency graphs, Bugzilla also supports dependency graphing, using a package called 'dot'. @@ -144,9 +147,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN847" +NAME="AEN867" ></A ->4.2.2. Bug Graphs</H2 +>4.3.2. Bug Graphs</H2 ><P >As long as you installed the GD and Graph::Base Perl modules you might as well turn on the nifty Bugzilla bug reporting graphs.</P @@ -203,9 +206,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN860" +NAME="AEN880" ></A ->4.2.3. The Whining Cron</H2 +>4.3.3. The Whining Cron</H2 ><P >By now you have a fully functional Bugzilla, but what good are bugs if they're not annoying? To help make those bugs more annoying you @@ -294,47 +297,11 @@ CLASS="section" ><A NAME="bzldap" ></A ->4.2.4. LDAP Authentication</H2 -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +>4.3.4. LDAP Authentication</H2 ><P ->LDAP authentication has been rewritten for the 2.18 release of - Bugzilla. It no longer requires the Mozilla::LDAP module and now uses - Net::LDAP instead. This rewrite was part of a larger landing that - allowed for additional authentication schemes to be easily added - (<A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=180642" -TARGET="_top" ->bug - 180642</A ->). - </P -><P ->This patch originally landed in 21-Mar-2003 and was included - in the 2.17.4 development release. - </P -></TD -></TR -></TABLE -></DIV +>LDAP authentication is a module for Bugzilla's plugin + authentication architecture. + </P ><P > The existing authentication scheme for Bugzilla uses email addresses as the primary user ID, and a @@ -544,26 +511,26 @@ CLASS="section" ><A NAME="content-type" ></A ->4.2.5. Preventing untrusted Bugzilla content from executing malicious +>4.3.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</H2 ><P ->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 +>It is possible for a Bugzilla attachment to contain malicious + Javascript + code, which would be executed in the domain of your Bugzilla, thereby + making it possible for the attacker to e.g. steal your login cookies. + Due to internationalization concerns, we are unable to + incorporate by default the code changes necessary to fulfill the CERT + advisory requirements mentioned in <A HREF="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3" TARGET="_top" >http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3</A >. - Making the change below will fix the problem if your installation is for - an English speaking audience. + If your installation is for an English speaking audience only, making the + change below will prevent this problem. </P ><P ->Telling Bugzilla to output a charset as part of the HTTP header is - much easier in version 2.18 and higher (including any cvs - pull after 4-May-2003 and development release after 2.17.5) than it was - in previous versions. Simply locate the following line in +>Simply locate the following line in <TT CLASS="filename" >Bugzilla/CGI.pm</TT @@ -578,8 +545,7 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # Make sure that we don't send any charset headers - $self->charset(''); +> $self->charset(''); </PRE ></FONT ></TD @@ -597,8 +563,7 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # Send all data using the ISO-8859-1 charset - $self->charset('ISO-8859-1'); +> $self->charset('ISO-8859-1'); </PRE ></FONT ></TD @@ -606,69 +571,6 @@ CLASS="programlisting" ></TABLE > </P -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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. See - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266" -TARGET="_top" ->bug 126266</A -> - for more information including progress toward making - bugzilla charset aware by default. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="directoryindex" -></A ->4.2.6. <TT -CLASS="filename" ->directoryindex</TT -> for the Bugzilla default page.</H2 -><P ->You should modify the <DirectoryIndex> parameter for - the Apache virtual host running your Bugzilla installation to - allow <TT -CLASS="filename" ->index.cgi</TT -> as the index page for a - directory, as well as the usual <TT -CLASS="filename" ->index.html</TT ->, - <TT -CLASS="filename" ->index.htm</TT ->, and so forth. </P ></DIV ><DIV CLASS="section" @@ -677,7 +579,7 @@ CLASS="section" ><A NAME="mod_perl" ></A ->4.2.7. Bugzilla and <TT +>4.3.6. Bugzilla and <TT CLASS="filename" >mod_perl</TT ></H2 @@ -694,7 +596,7 @@ CLASS="section" ><A NAME="mod-throttle" ></A ->4.2.8. <TT +>4.3.7. <TT CLASS="filename" >mod_throttle</TT > @@ -754,7 +656,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="stepbystep.html" +HREF="http.html" ACCESSKEY="P" >Prev</A ></TD @@ -782,7 +684,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Step-by-step Install</TD +>HTTP Server Configuration</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/faq.html b/docs/html/faq.html index 9ec11cd40..60517a94e 100644 --- a/docs/html/faq.html +++ b/docs/html/faq.html @@ -4,16 +4,18 @@ >The Bugzilla FAQ</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Integrating Bugzilla with Third-Party Tools" HREF="integration.html"><LINK REL="NEXT" -TITLE="The Bugzilla Database" -HREF="database.html"></HEAD +TITLE="Contrib" +HREF="patches.html"></HEAD ><BODY CLASS="appendix" BGCOLOR="#FFFFFF" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -55,7 +58,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="database.html" +HREF="patches.html" ACCESSKEY="N" >Next</A ></TD @@ -86,56 +89,51 @@ HREF="faq.html#faq-general" ><DL ><DT >A.1.1. <A -HREF="faq.html#faq-general-information" -> Where can I find information about Bugzilla?</A -></DT -><DT ->A.1.2. <A HREF="faq.html#faq-general-license" > What license is Bugzilla distributed under? </A ></DT ><DT ->A.1.3. <A +>A.1.2. <A HREF="faq.html#faq-general-support" > How do I get commercial support for Bugzilla? </A ></DT ><DT ->A.1.4. <A +>A.1.3. <A HREF="faq.html#faq-general-companies" > What major companies or projects are currently using Bugzilla for bug-tracking? </A ></DT ><DT ->A.1.5. <A +>A.1.4. <A HREF="faq.html#faq-general-maintainers" > Who maintains Bugzilla? </A ></DT ><DT ->A.1.6. <A +>A.1.5. <A HREF="faq.html#faq-general-compare" > How does Bugzilla stack up against other bug-tracking databases? </A ></DT ><DT ->A.1.7. <A +>A.1.6. <A HREF="faq.html#faq-general-bzmissing" > Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software? </A ></DT ><DT ->A.1.8. <A +>A.1.7. <A HREF="faq.html#faq-general-mysql" > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL. </A ></DT ><DT ->A.1.9. <A +>A.1.8. <A HREF="faq.html#faq-general-bonsaitools" > What is <TT CLASS="filename" @@ -144,7 +142,7 @@ CLASS="filename" </A ></DT ><DT ->A.1.10. <A +>A.1.9. <A HREF="faq.html#faq-general-perlpath" > My perl is not located at <TT CLASS="filename" @@ -154,7 +152,7 @@ CLASS="filename" </A ></DT ><DT ->A.1.11. <A +>A.1.10. <A HREF="faq.html#faq-general-cookie" > Is there an easy way to change the Bugzilla cookie name? </A @@ -177,33 +175,6 @@ HREF="faq.html#faq-phb-client" ></DT ><DT >A.2.2. <A -HREF="faq.html#faq-phb-integration" -> Can Bugzilla integrate with - Perforce (SCM software)? - </A -></DT -><DT ->A.2.3. <A -HREF="faq.html#faq-phb-projects" -> Does Bugzilla allow the user to track multiple projects? - </A -></DT -><DT ->A.2.4. <A -HREF="faq.html#faq-phb-sorting" -> If I am on many projects, and search for all bugs assigned to me, will - Bugzilla list them for me and allow me to sort by project, severity etc? - </A -></DT -><DT ->A.2.5. <A -HREF="faq.html#faq-phb-attachments" -> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, - are there any that are NOT allowed? - </A -></DT -><DT ->A.2.6. <A HREF="faq.html#faq-phb-priorities" > Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and @@ -211,35 +182,28 @@ HREF="faq.html#faq-phb-priorities" </A ></DT ><DT ->A.2.7. <A +>A.2.3. <A HREF="faq.html#faq-phb-reporting" > Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) </A ></DT ><DT ->A.2.8. <A +>A.2.4. <A HREF="faq.html#faq-phb-email" > Is there email notification and if so, what do you see when you get an email? </A ></DT ><DT ->A.2.9. <A -HREF="faq.html#faq-phb-cclist" -> Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? - </A -></DT -><DT ->A.2.10. <A +>A.2.5. <A HREF="faq.html#faq-phb-emailapp" > Do users have to have any particular type of email application? </A ></DT ><DT ->A.2.11. <A +>A.2.6. <A HREF="faq.html#faq-phb-data" > Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be @@ -248,28 +212,21 @@ HREF="faq.html#faq-phb-data" </A ></DT ><DT ->A.2.12. <A +>A.2.7. <A HREF="faq.html#faq-phb-l10n" > Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? </A ></DT ><DT ->A.2.13. <A +>A.2.8. <A HREF="faq.html#faq-phb-reports" > Can a user create and save reports? Can they do this in Word format? Excel format? </A ></DT ><DT ->A.2.14. <A -HREF="faq.html#faq-phb-searching" -> Does Bugzilla have the ability to search by word, phrase, compound - search? - </A -></DT -><DT ->A.2.15. <A +>A.2.9. <A HREF="faq.html#faq-phb-midair" > Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use @@ -277,29 +234,29 @@ HREF="faq.html#faq-phb-midair" </A ></DT ><DT ->A.2.16. <A +>A.2.10. <A HREF="faq.html#faq-phb-backup" > Are there any backup features provided? </A ></DT ><DT ->A.2.17. <A +>A.2.11. <A HREF="faq.html#faq-phb-livebackup" > Can users be on the system while a backup is in progress? </A ></DT ><DT ->A.2.18. <A +>A.2.12. <A HREF="faq.html#faq-phb-maintenance" > What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an - "Out-of-the-Box" solution. + "out-of-the-box" solution? </A ></DT ><DT ->A.2.19. <A +>A.2.13. <A HREF="faq.html#faq-phb-installtime" > What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to @@ -309,7 +266,7 @@ HREF="faq.html#faq-phb-installtime" </A ></DT ><DT ->A.2.20. <A +>A.2.14. <A HREF="faq.html#faq-phb-cost" > Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -337,14 +294,6 @@ HREF="faq.html#faq-security-knownproblems" > Are there any security problems with Bugzilla? </A ></DT -><DT ->A.3.3. <A -HREF="faq.html#faq-security-mysqluser" -> I've implemented the security fixes mentioned in Chris Yeh's security - advisory of 5/10/2000 advising not to run MySQL as root, and am running into - problems with MySQL no longer working correctly. - </A -></DT ></DL ></DD ><DT @@ -371,32 +320,25 @@ HREF="faq.html#faq-email-testing" ><DT >A.4.3. <A HREF="faq.html#faq-email-whine" -> I want whineatnews.pl to whine at something more, or other than, only new +> I want whineatnews.pl to whine at something different to only new bugs. How do I do it? </A ></DT ><DT >A.4.4. <A -HREF="faq.html#faq-email-procmail" -> I don't like/want to use Procmail to hand mail off to bug_email.pl. - What alternatives do I have? - </A -></DT -><DT ->A.4.5. <A HREF="faq.html#faq-email-mailif" > How do I set up the email interface to submit/change bugs via email? </A ></DT ><DT ->A.4.6. <A +>A.4.5. <A HREF="faq.html#faq-email-sendmailnow" > Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives? </A ></DT ><DT ->A.4.7. <A +>A.4.6. <A HREF="faq.html#faq-email-nonreceived" > How come email from Bugzilla changes never reaches me? </A @@ -575,38 +517,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-general-information" -></A -><B ->A.1.1. </B -> - Where can I find information about Bugzilla?</P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You can stay up-to-date with the latest Bugzilla - information at <A -HREF="http://www.bugzilla.org/" -TARGET="_top" ->http://www.bugzilla.org/</A ->. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-general-license" ></A ><B ->A.1.2. </B +>A.1.1. </B > What license is Bugzilla distributed under? </P @@ -635,7 +549,7 @@ CLASS="question" NAME="faq-general-support" ></A ><B ->A.1.3. </B +>A.1.2. </B > How do I get commercial support for Bugzilla? </P @@ -655,16 +569,6 @@ TARGET="_top" as consultants for Bugzilla. </P ><P -> <A -HREF="http://www.collab.net/" -TARGET="_top" ->http://www.collab.net/</A -> offers - Bugzilla as part of their standard offering to large projects. - They do have some minimum fees that are pretty hefty, and generally - aren't interested in small projects. - </P -><P > There are several experienced Bugzilla hackers on the mailing list/newsgroup who are willing to make themselves available for generous compensation. @@ -681,7 +585,7 @@ CLASS="question" NAME="faq-general-companies" ></A ><B ->A.1.4. </B +>A.1.3. </B > What major companies or projects are currently using Bugzilla for bug-tracking? @@ -699,9 +603,9 @@ CLASS="answer" Bugzilla sites to track bugs in their products. We have a fairly complete list available on our website at <A -HREF="http://bugzilla.org/installation_list.html" +HREF="http://bugzilla.org/installation-list/" TARGET="_top" ->http://bugzilla.org/installation_list.html</A +>http://bugzilla.org/installation-list/</A >. If you have an installation of Bugzilla and would like to be added to the list, whether it's a public install or not, simply e-mail @@ -711,11 +615,7 @@ CLASS="email" HREF="mailto:gerv@mozilla.org" >gerv@mozilla.org</A >></TT ->. Keep in mind that it's kinda - difficult to get onto the <SPAN -CLASS="QUOTE" ->"high-profile"</SPAN -> list ;). +>. </P ></DIV ></DIV @@ -728,7 +628,7 @@ CLASS="question" NAME="faq-general-maintainers" ></A ><B ->A.1.5. </B +>A.1.4. </B > Who maintains Bugzilla? </P @@ -758,7 +658,7 @@ CLASS="question" NAME="faq-general-compare" ></A ><B ->A.1.6. </B +>A.1.5. </B > How does Bugzilla stack up against other bug-tracking databases? </P @@ -796,7 +696,7 @@ CLASS="question" NAME="faq-general-bzmissing" ></A ><B ->A.1.7. </B +>A.1.6. </B > Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software? @@ -836,7 +736,7 @@ CLASS="question" NAME="faq-general-mysql" ></A ><B ->A.1.8. </B +>A.1.7. </B > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL. @@ -881,7 +781,7 @@ CLASS="question" NAME="faq-general-bonsaitools" ></A ><B ->A.1.9. </B +>A.1.8. </B > What is <TT CLASS="filename" @@ -923,7 +823,7 @@ CLASS="question" NAME="faq-general-perlpath" ></A ><B ->A.1.10. </B +>A.1.9. </B > My perl is not located at <TT CLASS="filename" @@ -972,7 +872,7 @@ CLASS="question" NAME="faq-general-cookie" ></A ><B ->A.1.11. </B +>A.1.10. </B > Is there an easy way to change the Bugzilla cookie name? </P @@ -995,36 +895,6 @@ CLASS="qandadiv" NAME="faq-phb" ></A >2. Managerial Questions</H3 -><P -> <DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> Questions likely to be asked by managers. :-) - </P -></TD -></TR -></TABLE -></DIV -> - </P ><DIV CLASS="qandaentry" ><DIV @@ -1046,113 +916,7 @@ CLASS="answer" ><B > </B > - It is web and e-mail based. You can edit bugs by sending specially - formatted email to a properly configured Bugzilla, or control via the web. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-integration" -></A -><B ->A.2.2. </B -> - Can Bugzilla integrate with - Perforce (SCM software)? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes! You can find more information elsewhere in "The Bugzilla - Guide" in the "Integration with Third-Party Products" section. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-projects" -></A -><B ->A.2.3. </B -> - Does Bugzilla allow the user to track multiple projects? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Absolutely! You can track any number of Products that can each be - composed of any number of Components. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-sorting" -></A -><B ->A.2.4. </B -> - If I am on many projects, and search for all bugs assigned to me, will - Bugzilla list them for me and allow me to sort by project, severity etc? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-phb-attachments" -></A -><B ->A.2.5. </B -> - Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, - are there any that are NOT allowed? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes - any sort of attachment is allowed, although administrators can - configure a maximum size. - Bugzilla gives the user the option of either using the MIME-type - supplied by the browser, choosing from a pre-defined list or - manually typing any arbitrary MIME-type. + It is web and e-mail based. </P ></DIV ></DIV @@ -1165,7 +929,7 @@ CLASS="question" NAME="faq-phb-priorities" ></A ><B ->A.2.6. </B +>A.2.2. </B > Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and @@ -1202,7 +966,7 @@ CLASS="question" NAME="faq-phb-reporting" ></A ><B ->A.2.7. </B +>A.2.3. </B > Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) @@ -1240,7 +1004,7 @@ CLASS="question" NAME="faq-phb-email" ></A ><B ->A.2.8. </B +>A.2.4. </B > Is there email notification and if so, what do you see when you get an email? @@ -1253,7 +1017,7 @@ CLASS="answer" > </B > Email notification is user-configurable. By default, the bug id and - Summary of the bug report accompany each email notification, along with + summary of the bug report accompany each email notification, along with a list of the changes made. </P ></DIV @@ -1264,35 +1028,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-cclist" -></A -><B ->A.2.9. </B -> - Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - Yes. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-phb-emailapp" ></A ><B ->A.2.10. </B +>A.2.5. </B > Do users have to have any particular type of email application? @@ -1351,7 +1090,7 @@ CLASS="question" NAME="faq-phb-data" ></A ><B ->A.2.11. </B +>A.2.6. </B > Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be @@ -1368,7 +1107,7 @@ CLASS="answer" Bugzilla can output buglists as HTML (the default), CSV or RDF. The link for CSV can be found at the bottom of the buglist in HTML format. This CSV format can easily be imported into MS Excel or - other spread-sheet applications. + other spreadsheet applications. </P ><P > To use the RDF format of the buglist it is necessary to append a @@ -1377,7 +1116,7 @@ CLASS="computeroutput" >&ctype=rdf</TT > to the URL. RDF is meant to be machine readable and thus it is assumed that the - URL would be generated progmatically so there is no user visible + URL would be generated programatically so there is no user visible link to this format. </P ><P @@ -1413,7 +1152,7 @@ CLASS="question" NAME="faq-phb-l10n" ></A ><B ->A.2.12. </B +>A.2.7. </B > Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? @@ -1451,7 +1190,7 @@ CLASS="question" NAME="faq-phb-reports" ></A ><B ->A.2.13. </B +>A.2.8. </B > Can a user create and save reports? Can they do this in Word format? Excel format? @@ -1473,36 +1212,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-phb-searching" -></A -><B ->A.2.14. </B -> - Does Bugzilla have the ability to search by word, phrase, compound - search? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You have no idea. Bugzilla's query interface, particularly with the - advanced Boolean operators, is incredibly versatile. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-phb-midair" ></A ><B ->A.2.15. </B +>A.2.9. </B > Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use @@ -1529,7 +1242,7 @@ CLASS="question" NAME="faq-phb-backup" ></A ><B ->A.2.16. </B +>A.2.10. </B > Are there any backup features provided? </P @@ -1559,7 +1272,7 @@ CLASS="question" NAME="faq-phb-livebackup" ></A ><B ->A.2.17. </B +>A.2.11. </B > Can users be on the system while a backup is in progress? </P @@ -1585,13 +1298,13 @@ CLASS="question" NAME="faq-phb-maintenance" ></A ><B ->A.2.18. </B +>A.2.12. </B > What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an - "Out-of-the-Box" solution. + "out-of-the-box" solution? </P ></DIV ><DIV @@ -1620,7 +1333,7 @@ CLASS="question" NAME="faq-phb-installtime" ></A ><B ->A.2.19. </B +>A.2.13. </B > What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to @@ -1653,7 +1366,7 @@ CLASS="question" NAME="faq-phb-cost" ></A ><B ->A.2.20. </B +>A.2.14. </B > Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -1735,34 +1448,6 @@ CLASS="answer" </P ></DIV ></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A -NAME="faq-security-mysqluser" -></A -><B ->A.3.3. </B -> - I've implemented the security fixes mentioned in Chris Yeh's security - advisory of 5/10/2000 advising not to run MySQL as root, and am running into - problems with MySQL no longer working correctly. - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - This is a common problem, related to running out of file descriptors. - Simply add "ulimit -n unlimited" to the script which starts - mysqld. - </P -></DIV -></DIV ></DIV ><DIV CLASS="qandadiv" @@ -1838,7 +1523,7 @@ NAME="faq-email-whine" ><B >A.4.3. </B > - I want whineatnews.pl to whine at something more, or other than, only new + I want whineatnews.pl to whine at something different to only new bugs. How do I do it? </P ></DIV @@ -1866,49 +1551,10 @@ CLASS="qandaentry" CLASS="question" ><P ><A -NAME="faq-email-procmail" -></A -><B ->A.4.4. </B -> - I don't like/want to use Procmail to hand mail off to bug_email.pl. - What alternatives do I have? - </P -></DIV -><DIV -CLASS="answer" -><P -><B -> </B -> - You can call bug_email.pl directly from your aliases file, with - an entry like this: - <A -NAME="AEN2067" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" -><P -> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" - </P -></BLOCKQUOTE -> - However, this is fairly nasty and subject to problems; you also - need to set up your smrsh (sendmail restricted shell) to allow - it. In a pinch, though, it can work. - </P -></DIV -></DIV -><DIV -CLASS="qandaentry" -><DIV -CLASS="question" -><P -><A NAME="faq-email-mailif" ></A ><B ->A.4.5. </B +>A.4.4. </B > How do I set up the email interface to submit/change bugs via email? </P @@ -1933,7 +1579,7 @@ CLASS="question" NAME="faq-email-sendmailnow" ></A ><B ->A.4.6. </B +>A.4.5. </B > Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives? @@ -1945,7 +1591,21 @@ CLASS="answer" ><B > </B > - If you are using an alternate <A + If you are using <SPAN +CLASS="application" +>sendmail</SPAN +>, try enabling + <TT +CLASS="option" +>sendmailnow</TT +> in <TT +CLASS="filename" +>editparams.cgi</TT +>. + + </P +><P +> If you are using an alternate <A HREF="glossary.html#gloss-mta" ><I CLASS="glossterm" @@ -1969,20 +1629,6 @@ CLASS="literal" >on</TT >. </P -><P -> If you are using <SPAN -CLASS="application" ->sendmail</SPAN ->, try enabling - <TT -CLASS="option" ->sendmailnow</TT -> in <TT -CLASS="filename" ->editparams.cgi</TT ->. - - </P ></DIV ></DIV ><DIV @@ -1994,7 +1640,7 @@ CLASS="question" NAME="faq-email-nonreceived" ></A ><B ->A.4.7. </B +>A.4.6. </B > How come email from Bugzilla changes never reaches me? </P @@ -2011,7 +1657,7 @@ CLASS="answer" button after entering your email address. </P ><P -> If you never receive mail from Bugzilla, chances you do not have +> If you never receive mail from Bugzilla, chances are you do not have sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked to, "/usr/lib/sendmail". </P @@ -2045,11 +1691,12 @@ CLASS="answer" ><B > </B > - Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. + Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle, + but it is now so old as to be obsolete, and is totally unsupported. Red Hat's newer version (based on 2.17.1 and soon to be merged into the main distribution) runs on PostgreSQL. At this time we know of - no recent ports of Bugzilla to Oracle but do intend to support it - in the future (possibly the 2.20 time-frame). + no recent ports of Bugzilla to Oracle; to be honest, Bugzilla + doesn't need what Oracle offers. </P ></DIV ></DIV @@ -2080,10 +1727,9 @@ CLASS="QUOTE" > utility (<TT CLASS="filename" ->./sanitycheck.cgi</TT -> in the - Bugzilla_home directory) from your web browser to see! If - it finishes without errors, you're +>sanitycheck.cgi</TT +>) from your web browser to see! + If it finishes without errors, you're <EM >probably</EM > OK. If it doesn't come back @@ -2328,7 +1974,7 @@ CLASS="answer" ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN2150" +NAME="AEN2062" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -2876,7 +2522,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="database.html" +HREF="patches.html" ACCESSKEY="N" >Next</A ></TD @@ -2896,7 +2542,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->The Bugzilla Database</TD +>Contrib</TD ></TR ></TABLE ></DIV diff --git a/docs/html/gfdl-0.html b/docs/html/gfdl-0.html index 7b7408310..664f95504 100644 --- a/docs/html/gfdl-0.html +++ b/docs/html/gfdl-0.html @@ -4,9 +4,11 @@ >PREAMBLE</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-1.html b/docs/html/gfdl-1.html index 45a1d994a..d5c619887 100644 --- a/docs/html/gfdl-1.html +++ b/docs/html/gfdl-1.html @@ -4,9 +4,11 @@ >APPLICABILITY AND DEFINITIONS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-10.html b/docs/html/gfdl-10.html index 080f8b7f8..eb489176f 100644 --- a/docs/html/gfdl-10.html +++ b/docs/html/gfdl-10.html @@ -4,9 +4,11 @@ >FUTURE REVISIONS OF THIS LICENSE</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-2.html b/docs/html/gfdl-2.html index bd6c41c3f..a56039b58 100644 --- a/docs/html/gfdl-2.html +++ b/docs/html/gfdl-2.html @@ -4,9 +4,11 @@ >VERBATIM COPYING</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-3.html b/docs/html/gfdl-3.html index 0db6ed8af..d4186b136 100644 --- a/docs/html/gfdl-3.html +++ b/docs/html/gfdl-3.html @@ -4,9 +4,11 @@ >COPYING IN QUANTITY</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-4.html b/docs/html/gfdl-4.html index c5d7d5957..76ae39df6 100644 --- a/docs/html/gfdl-4.html +++ b/docs/html/gfdl-4.html @@ -4,9 +4,11 @@ >MODIFICATIONS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-5.html b/docs/html/gfdl-5.html index eed6fc5c4..46d418388 100644 --- a/docs/html/gfdl-5.html +++ b/docs/html/gfdl-5.html @@ -4,9 +4,11 @@ >COMBINING DOCUMENTS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-6.html b/docs/html/gfdl-6.html index 724af41ba..f636bf64d 100644 --- a/docs/html/gfdl-6.html +++ b/docs/html/gfdl-6.html @@ -4,9 +4,11 @@ >COLLECTIONS OF DOCUMENTS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-7.html b/docs/html/gfdl-7.html index d22a95f7f..6f5c35cb0 100644 --- a/docs/html/gfdl-7.html +++ b/docs/html/gfdl-7.html @@ -4,9 +4,11 @@ >AGGREGATION WITH INDEPENDENT WORKS</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-8.html b/docs/html/gfdl-8.html index 8b89b2fed..10a47a714 100644 --- a/docs/html/gfdl-8.html +++ b/docs/html/gfdl-8.html @@ -4,9 +4,11 @@ >TRANSLATION</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-9.html b/docs/html/gfdl-9.html index b23394dc6..3de0c0918 100644 --- a/docs/html/gfdl-9.html +++ b/docs/html/gfdl-9.html @@ -4,9 +4,11 @@ >TERMINATION</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" diff --git a/docs/html/gfdl-howto.html b/docs/html/gfdl-howto.html index 1a45954f3..88d55d42a 100644 --- a/docs/html/gfdl-howto.html +++ b/docs/html/gfdl-howto.html @@ -4,9 +4,11 @@ >How to use this License for your documents</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="GNU Free Documentation License" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix E. GNU Free Documentation License</TD +>Appendix C. GNU Free Documentation License</TD ><TD WIDTH="10%" ALIGN="right" @@ -80,7 +83,7 @@ NAME="gfdl-howto" of the License in the document and put the following copyright and license notices just after the title page:</P ><A -NAME="AEN2484" +NAME="AEN2282" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html index 55e19a9d6..d90c78619 100644 --- a/docs/html/gfdl.html +++ b/docs/html/gfdl.html @@ -4,13 +4,15 @@ >GNU Free Documentation License</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="SourceForge" -HREF="variant-sourceforge.html"><LINK +TITLE="Command-line Search Interface" +HREF="cmdline.html"><LINK REL="NEXT" TITLE="PREAMBLE" HREF="gfdl-0.html"></HEAD @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -41,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="variant-sourceforge.html" +HREF="cmdline.html" ACCESSKEY="P" >Prev</A ></TD @@ -70,7 +73,7 @@ CLASS="appendix" ><A NAME="gfdl" ></A ->Appendix E. GNU Free Documentation License</H1 +>Appendix C. GNU Free Documentation License</H1 ><DIV CLASS="TOC" ><DL @@ -143,7 +146,7 @@ HREF="gfdl-howto.html" ><P >Version 1.1, March 2000</P ><A -NAME="AEN2394" +NAME="AEN2192" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -170,7 +173,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="variant-sourceforge.html" +HREF="cmdline.html" ACCESSKEY="P" >Prev</A ></TD @@ -198,7 +201,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->SourceForge</TD +>Command-line Search Interface</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/glossary.html b/docs/html/glossary.html index 1eb4e732b..65916c3fb 100644 --- a/docs/html/glossary.html +++ b/docs/html/glossary.html @@ -4,9 +4,11 @@ >Glossary</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" TITLE="How to use this License for your documents" @@ -30,7 +32,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -69,7 +72,7 @@ CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A -NAME="AEN2489" +NAME="AEN2287" ></A >0-9, high ascii</H1 ><DL @@ -239,7 +242,7 @@ TARGET="_top" >For more information about how to configure Apache for Bugzilla, see <A HREF="http.html#http-apache" ->Section 4.4.1</A +>Section 4.2.1</A >. </P ></DD @@ -632,7 +635,7 @@ TARGET="_top" >Much more detailed information about the suggestions in <A HREF="security.html#security-mysql" ->Section 5.6.2</A +>Section 4.5.2</A >. </P ></DD @@ -933,7 +936,7 @@ NAME="gloss-zarro" Terry had the following to say: </P ><A -NAME="AEN2724" +NAME="AEN2522" ></A ><TABLE BORDER="0" diff --git a/docs/html/groups.html b/docs/html/groups.html index 2f5415477..e278da714 100644 --- a/docs/html/groups.html +++ b/docs/html/groups.html @@ -4,9 +4,11 @@ >Groups and Group Security</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Voting" HREF="voting.html"><LINK REL="NEXT" -TITLE="Bugzilla Security" -HREF="security.html"></HEAD +TITLE="Upgrading to New Releases" +HREF="upgrading.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="security.html" +HREF="upgrading.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="groups" ></A ->5.5. Groups and Group Security</H1 +>5.8. Groups and Group Security</H1 ><P >Groups allow the administrator to isolate bugs or products that should only be seen by certain people. @@ -213,9 +216,10 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->The User Regexp is a perl regexp and, if not anchored, will match - any part of an address. So, if you do not want to grant access - into 'mycompany.com' to 'badperson@mycompany.com.hacker.net', use +>If specifying a domain in the regexp, make sure you end + the regexp with a $. Otherwise, when granting access to + "@mycompany\.com", you will allow access to + 'badperson@mycompany.com.cracker.net'. You need to use '@mycompany\.com$' as the regexp.</P ></TD ></TR @@ -283,7 +287,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="security.html" +HREF="upgrading.html" ACCESSKEY="N" >Next</A ></TD @@ -307,7 +311,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Bugzilla Security</TD +>Upgrading to New Releases</TD ></TR ></TABLE ></DIV diff --git a/docs/html/hintsandtips.html b/docs/html/hintsandtips.html index c3b2ed8e4..ee796c9cf 100644 --- a/docs/html/hintsandtips.html +++ b/docs/html/hintsandtips.html @@ -4,16 +4,18 @@ >Hints and Tips</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Using Bugzilla" HREF="using.html"><LINK REL="PREVIOUS" -TITLE="How do I use Bugzilla?" -HREF="how.html"><LINK +TITLE="Patch Viewer" +HREF="patchviewer.html"><LINK REL="NEXT" TITLE="User Preferences" HREF="userpreferences.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="how.html" +HREF="patchviewer.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="hintsandtips" ></A ->3.2. Hints and Tips</H1 +>3.7. Hints and Tips</H1 ><P >This section distills some Bugzilla tips and best practices that have been developed.</P @@ -83,15 +86,15 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN407" +NAME="AEN358" ></A ->3.2.1. Autolinkification</H2 +>3.7.1. Autolinkification</H2 ><P ->Bugzilla comments are plain text - so posting HTML will result - in literal HTML tags rather than being interpreted by a browser. +>Bugzilla comments are plain text - so typing <U> will + produce less-than, U, greater-than rather than underlined text. 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" will be turned into a link: <A HREF="http://www.bugzilla.org" TARGET="_top" @@ -109,6 +112,10 @@ BORDER="0" ></TR ><TR ><TD +>comment 7</TD +></TR +><TR +><TD >bug 23456, comment 53</TD ></TR ><TR @@ -150,7 +157,7 @@ CLASS="section" ><A NAME="quicksearch" ></A ->3.2.2. Quicksearch</H2 +>3.7.2. Quicksearch</H2 ><P >Quicksearch is a single-text-box query tool which uses metacharacters to indicate what is to be searched. For example, typing @@ -183,7 +190,7 @@ CLASS="section" ><A NAME="commenting" ></A ->3.2.3. Comments</H2 +>3.7.3. Comments</H2 ><P >If you are changing the fields on a bug, only comment if either you have something pertinent to say, or Bugzilla requires it. @@ -196,7 +203,7 @@ NAME="commenting" </P ><P > 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 + if you do it out of habit, but full mail/news-style four line ASCII art creations are not. </P ></DIV @@ -207,7 +214,7 @@ CLASS="section" ><A NAME="attachments" ></A ->3.2.4. Attachments</H2 +>3.7.4. Attachments</H2 ><P > Use attachments, rather than comments, for large chunks of ASCII data, such as trace, debugging output files, or log files. That way, it doesn't @@ -231,9 +238,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN436" +NAME="AEN388" ></A ->3.2.5. Filing Bugs</H2 +>3.7.5. Filing Bugs</H2 ><P >Try to make sure that everything said in the summary is also said in the first comment. Summaries are often updated and this will @@ -268,7 +275,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="how.html" +HREF="patchviewer.html" ACCESSKEY="P" >Prev</A ></TD @@ -296,7 +303,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->How do I use Bugzilla?</TD +>Patch Viewer</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/how.html b/docs/html/how.html index 9b0f26f48..1b8a87910 100644 --- a/docs/html/how.html +++ b/docs/html/how.html @@ -4,9 +4,11 @@ >How do I use Bugzilla?</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Using Bugzilla" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD diff --git a/docs/html/http.html b/docs/html/http.html index 8f3b76d05..a950acce5 100644 --- a/docs/html/http.html +++ b/docs/html/http.html @@ -4,19 +4,21 @@ >HTTP Server Configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Installation" HREF="installation.html"><LINK REL="PREVIOUS" -TITLE="OS Specific Installation Notes" -HREF="os-specific.html"><LINK +TITLE="Step-by-step Install" +HREF="stepbystep.html"><LINK REL="NEXT" -TITLE="Troubleshooting" -HREF="troubleshooting.html"></HEAD +TITLE="Optional Additional Configuration" +HREF="extraconfig.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="os-specific.html" +HREF="stepbystep.html" ACCESSKEY="P" >Prev</A ></TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="troubleshooting.html" +HREF="extraconfig.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="http" ></A ->4.4. HTTP Server Configuration</H1 +>4.2. HTTP Server Configuration</H1 ><P >The Bugzilla Team recommends Apache when using Bugzilla, however, any web server that can be configured to run <A @@ -88,7 +91,7 @@ CLASS="glossterm" especially if you choose something other than Apache, you should be sure to read <A HREF="security.html#security-access" ->Section 5.6.4</A +>Section 4.5.4</A >. </P ><P @@ -102,13 +105,12 @@ CLASS="section" ><A NAME="http-apache" ></A ->4.4.1. Apache <SPAN +>4.2.1. Apache <SPAN CLASS="productname" >httpd</SPAN ></H2 ><P ->As mentioned above, the Bugzilla Team recommends Apache for use - with Bugzilla. You will have to make sure that Apache is properly +>You will have to make sure that Apache is properly configured to run the Bugzilla CGI scripts. You also need to make sure that the <TT CLASS="filename" @@ -117,41 +119,21 @@ CLASS="filename" <B CLASS="command" >./checksetup.pl</B -> (shown in <A -HREF="http.html#http-apache-htaccess" ->Example 4-2</A -> - for the curious) are allowed to override Apache's normal access +> are allowed to override Apache's normal access permissions or else important password information may be exposed to the Internet. </P ><P ->Many Apache installations are not configured to run scripts - anywhere but in the <TT -CLASS="filename" ->cgi-bin</TT -> - directory; however, we recommend that Bugzilla not be installed in the +>You need to configure Apache to run .cgi files outside the <TT CLASS="filename" >cgi-bin</TT ->, otherwise the static - files such as images and <A -HREF="glossary.html#gloss-javascript" -><I -CLASS="glossterm" ->JavaScript</I -></A -> - will not work correctly. To allow scripts to run in the normal - web space, the following changes should be made to your +> directory. + Open your <TT CLASS="filename" >httpd.conf</TT -> file. - </P -><P ->To allow files with a .cgi extension to be run, make sure the +> file and make sure the following line exists and is uncommented:</P ><TABLE BORDER="0" @@ -199,6 +181,21 @@ AllowOverride Limit ></TD ></TR ></TABLE +><P +>You should modify the <DirectoryIndex> parameter for + the Apache virtual host running your Bugzilla installation to + allow <TT +CLASS="filename" +>index.cgi</TT +> as the index page for a + directory, as well as the usual <TT +CLASS="filename" +>index.html</TT +>, + <TT +CLASS="filename" +>index.htm</TT +>, and so forth. </P ><DIV CLASS="note" ><P @@ -233,165 +230,6 @@ CLASS="glossterm" ></TR ></TABLE ></DIV -><DIV -CLASS="example" -><A -NAME="http-apache-htaccess" -></A -><P -><B ->Example 4-2. <TT -CLASS="filename" ->.htaccess</TT -> files for Apache</B -></P -><P -><TT -CLASS="filename" ->$BUGZILLA_HOME/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # don't allow people to retrieve non-cgi executable files or our private data -<FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$> - deny from all -</FilesMatch> -<FilesMatch ^(localconfig.js|localconfig.rdf)$> - allow from all -</FilesMatch> - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -><P -><TT -CLASS="filename" ->$BUGZILLA_HOME/data/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory; the only exception is duplicates.rdf, which is used by -# duplicates.xul and must be loadable over the web -deny from all -<Files duplicates.rdf> - allow from all -</Files> - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -><P -><TT -CLASS="filename" ->$BUGZILLA_HOME/data/webdot</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # Restrict access to .dot files to the public webdot server at research.att.com -# if research.att.com ever changed their IP, or if you use a different -# webdot server, you'll need to edit this -<FilesMatch ^[0-9]+\.dot$> - Allow from 192.20.225.10 - Deny from all -</FilesMatch> - -# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and -# .map files -<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> - Allow from all -</FilesMatch> - -# And no directory listings, either. -Deny from all - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -><P -><TT -CLASS="filename" ->$BUGZILLA_HOME/Bugzilla/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -><P -><TT -CLASS="filename" ->$BUGZILLA_HOME/template/.htaccess</TT -> - <TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="programlisting" -> # nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all - </PRE -></FONT -></TD -></TR -></TABLE -> - </P -></DIV ></DIV ><DIV CLASS="section" @@ -400,7 +238,7 @@ CLASS="section" ><A NAME="http-iis" ></A ->4.4.2. Microsoft <SPAN +>4.2.2. Microsoft <SPAN CLASS="productname" >Internet Information Services</SPAN ></H2 @@ -446,7 +284,7 @@ CLASS="filename" > directory are secured as described in <A HREF="security.html#security-access" ->Section 5.6.4</A +>Section 4.5.4</A >. </P ></DIV @@ -457,7 +295,7 @@ CLASS="section" ><A NAME="http-aol" ></A ->4.4.3. AOL Server</H2 +>4.2.3. AOL Server</H2 ><P >Ben FrantzDale reported success using AOL Server with Bugzilla. He reported his experience and what appears below is based on that. @@ -646,7 +484,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="os-specific.html" +HREF="stepbystep.html" ACCESSKEY="P" >Prev</A ></TD @@ -664,7 +502,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="troubleshooting.html" +HREF="extraconfig.html" ACCESSKEY="N" >Next</A ></TD @@ -674,7 +512,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->OS Specific Installation Notes</TD +>Step-by-step Install</TD ><TD WIDTH="34%" ALIGN="center" @@ -688,7 +526,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Troubleshooting</TD +>Optional Additional Configuration</TD ></TR ></TABLE ></DIV diff --git a/docs/html/index.html b/docs/html/index.html index 3c91d11aa..61cce5ee5 100644 --- a/docs/html/index.html +++ b/docs/html/index.html @@ -1,10 +1,12 @@ <HTML ><HEAD ><TITLE ->The Bugzilla Guide - 2.17.5 Development Release</TITLE +>The Bugzilla Guide - 2.17.5 + Development Release</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="NEXT" TITLE="About This Guide" HREF="about.html"><META @@ -45,61 +47,36 @@ CLASS="title" ><A NAME="AEN2" ></A ->The Bugzilla Guide - 2.17.5 Development Release</H1 -><H3 -CLASS="author" -><A -NAME="AEN5" -></A ->Matthew P. Barnson</H3 -><H3 -CLASS="author" -><A -NAME="AEN9" -></A ->Jacob Steenhagen</H3 +>The Bugzilla Guide - 2.17.5 + Development Release</H1 ><H3 CLASS="corpauthor" >The Bugzilla Team</H3 ><P CLASS="pubdate" ->2003-11-01<BR></P +>2004-01-15<BR></P ><DIV ><DIV CLASS="abstract" ><A -NAME="AEN14" +NAME="AEN7" ></A ><P ></P ><P -> This is the documentation for Bugzilla, the mozilla.org - bug-tracking system. +> This is the documentation for Bugzilla, a + bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software - that powers issue-tracking for hundreds of - organizations around the world, tracking millions of bugs. - </P -><P -> - 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 the <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A -> component. + that tracks millions of bugs and issues for hundreds of + organizations around the world. </P ><P ->This is a development version of this guide. Information in it - is subject to change before the 2.18 release of this guide - (which will correspond with the 2.18 release of Bugzilla). - </P -><P > The most current version of this document can always be found on the <A HREF="http://www.bugzilla.org/documentation.html" TARGET="_top" ->Bugzilla Documentation Page</A +>Bugzilla + Documentation Page</A >. </P ><P @@ -157,13 +134,18 @@ HREF="introduction.html" ><DL ><DT >2.1. <A -HREF="whatis.html" +HREF="what-is-bugzilla.html" >What is Bugzilla?</A ></DT ><DT >2.2. <A -HREF="why.html" ->Why Should We Use Bugzilla?</A +HREF="why-tracking.html" +>Why use a bug-tracking system?</A +></DT +><DT +>2.3. <A +HREF="why-bugzilla.html" +>Why use Bugzilla?</A ></DT ></DL ></DD @@ -176,19 +158,49 @@ HREF="using.html" ><DL ><DT >3.1. <A -HREF="how.html" ->How do I use Bugzilla?</A +HREF="myaccount.html" +>Create a Bugzilla Account</A ></DT ><DT >3.2. <A +HREF="bug_page.html" +>Anatomy of a Bug</A +></DT +><DT +>3.3. <A +HREF="query.html" +>Searching for Bugs</A +></DT +><DT +>3.4. <A +HREF="list.html" +>Bug Lists</A +></DT +><DT +>3.5. <A +HREF="bugreports.html" +>Filing Bugs</A +></DT +><DT +>3.6. <A +HREF="patchviewer.html" +>Patch Viewer</A +></DT +><DT +>3.7. <A HREF="hintsandtips.html" >Hints and Tips</A ></DT ><DT ->3.3. <A +>3.8. <A HREF="userpreferences.html" >User Preferences</A ></DT +><DT +>3.9. <A +HREF="reporting.html" +>Reports</A +></DT ></DL ></DD ><DT @@ -205,21 +217,26 @@ HREF="stepbystep.html" ></DT ><DT >4.2. <A +HREF="http.html" +>HTTP Server Configuration</A +></DT +><DT +>4.3. <A HREF="extraconfig.html" >Optional Additional Configuration</A ></DT ><DT ->4.3. <A +>4.4. <A HREF="os-specific.html" >OS Specific Installation Notes</A ></DT ><DT ->4.4. <A -HREF="http.html" ->HTTP Server Configuration</A +>4.5. <A +HREF="security.html" +>Bugzilla Security</A ></DT ><DT ->4.5. <A +>4.6. <A HREF="troubleshooting.html" >Troubleshooting</A ></DT @@ -244,136 +261,96 @@ HREF="useradmin.html" ></DT ><DT >5.3. <A -HREF="programadmin.html" ->Product, Component, Milestone, and Version Administration</A +HREF="products.html" +>Products</A ></DT ><DT >5.4. <A -HREF="voting.html" ->Voting</A +HREF="components.html" +>Components</A ></DT ><DT >5.5. <A -HREF="groups.html" ->Groups and Group Security</A +HREF="versions.html" +>Versions</A ></DT ><DT >5.6. <A -HREF="security.html" ->Bugzilla Security</A +HREF="milestones.html" +>Milestones</A ></DT ><DT >5.7. <A -HREF="cust-templates.html" ->Template Customization</A +HREF="voting.html" +>Voting</A ></DT ><DT >5.8. <A -HREF="cust-change-permissions.html" ->Change Permission Customization</A +HREF="groups.html" +>Groups and Group Security</A ></DT ><DT >5.9. <A HREF="upgrading.html" >Upgrading to New Releases</A ></DT -><DT ->5.10. <A -HREF="integration.html" ->Integrating Bugzilla with Third-Party Tools</A -></DT ></DL ></DD ><DT ->A. <A -HREF="faq.html" ->The Bugzilla FAQ</A -></DT -><DT ->B. <A -HREF="database.html" ->The Bugzilla Database</A +>6. <A +HREF="customization.html" +>Customising Bugzilla</A ></DT ><DD ><DL ><DT ->B.1. <A -HREF="dbmodify.html" ->Modifying Your Running System</A +>6.1. <A +HREF="cust-templates.html" +>Template Customization</A ></DT ><DT ->B.2. <A -HREF="dbdoc.html" ->MySQL Bugzilla Database Introduction</A +>6.2. <A +HREF="cust-change-permissions.html" +>Customizing Who Can Change What</A ></DT -></DL -></DD ><DT ->C. <A -HREF="patches.html" ->Useful Patches and Utilities for Bugzilla</A +>6.3. <A +HREF="dbmodify.html" +>Modifying Your Running System</A ></DT -><DD -><DL ><DT ->C.1. <A -HREF="rewrite.html" ->Apache - <TT -CLASS="filename" ->mod_rewrite</TT -> - - magic</A +>6.4. <A +HREF="dbdoc.html" +>MySQL Bugzilla Database Introduction</A ></DT ><DT ->C.2. <A -HREF="cmdline.html" ->Command-line Bugzilla Queries</A +>6.5. <A +HREF="integration.html" +>Integrating Bugzilla with Third-Party Tools</A ></DT ></DL ></DD ><DT ->D. <A -HREF="variants.html" ->Bugzilla Variants and Competitors</A -></DT -><DD -><DL -><DT ->D.1. <A -HREF="variant-redhat.html" ->Red Hat Bugzilla</A -></DT -><DT ->D.2. <A -HREF="variant-fenris.html" ->Loki Bugzilla (Fenris)</A -></DT -><DT ->D.3. <A -HREF="variant-issuezilla.html" ->Issuezilla</A -></DT -><DT ->D.4. <A -HREF="variant-scarab.html" ->Scarab</A +>A. <A +HREF="faq.html" +>The Bugzilla FAQ</A ></DT ><DT ->D.5. <A -HREF="variant-perforce.html" ->Perforce SCM</A +>B. <A +HREF="patches.html" +>Contrib</A ></DT +><DD +><DL ><DT ->D.6. <A -HREF="variant-sourceforge.html" ->SourceForge</A +>B.1. <A +HREF="cmdline.html" +>Command-line Search Interface</A ></DT ></DL ></DD ><DT ->E. <A +>C. <A HREF="gfdl.html" >GNU Free Documentation License</A ></DT @@ -487,14 +464,6 @@ HREF="stepbystep.html#install-perlmodules-cpan" >Installing perl modules with CPAN</A ></DT ><DT ->4-2. <A -HREF="http.html#http-apache-htaccess" -><TT -CLASS="filename" ->.htaccess</TT -> files for Apache</A -></DT -><DT >5-1. <A HREF="upgrading.html#upgrade-cvs" >Upgrading using CVS</A diff --git a/docs/html/installation.html b/docs/html/installation.html index ac764366b..7377de3f7 100644 --- a/docs/html/installation.html +++ b/docs/html/installation.html @@ -4,13 +4,15 @@ >Installation</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="User Preferences" -HREF="userpreferences.html"><LINK +TITLE="Reports" +HREF="reporting.html"><LINK REL="NEXT" TITLE="Step-by-step Install" HREF="stepbystep.html"></HEAD @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -41,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="userpreferences.html" +HREF="reporting.html" ACCESSKEY="P" >Prev</A ></TD @@ -87,92 +90,109 @@ HREF="stepbystep.html" ><DL ><DT >4.1.1. <A -HREF="stepbystep.html#install-mysql" ->MySQL</A -></DT -><DT ->4.1.2. <A HREF="stepbystep.html#install-perl" >Perl</A ></DT ><DT ->4.1.3. <A -HREF="stepbystep.html#install-perlmodules" ->Perl Modules</A +>4.1.2. <A +HREF="stepbystep.html#install-mysql" +>MySQL</A ></DT ><DT ->4.1.4. <A +>4.1.3. <A HREF="stepbystep.html#install-webserver" >HTTP Server</A ></DT ><DT ->4.1.5. <A +>4.1.4. <A HREF="stepbystep.html#install-bzfiles" >Bugzilla</A ></DT ><DT ->4.1.6. <A -HREF="stepbystep.html#install-setupdatabase" ->Setting Up the MySQL Database</A +>4.1.5. <A +HREF="stepbystep.html#install-perlmodules" +>Perl Modules</A ></DT ><DT ->4.1.7. <A -HREF="stepbystep.html#AEN795" +>4.1.6. <A +HREF="stepbystep.html#AEN748" ><TT CLASS="filename" >checksetup.pl</TT ></A ></DT ><DT ->4.1.8. <A -HREF="stepbystep.html#AEN826" +>4.1.7. <A +HREF="stepbystep.html#AEN778" >Configuring Bugzilla</A ></DT ></DL ></DD ><DT >4.2. <A +HREF="http.html" +>HTTP Server Configuration</A +></DT +><DD +><DL +><DT +>4.2.1. <A +HREF="http.html#http-apache" +>Apache <SPAN +CLASS="productname" +>httpd</SPAN +></A +></DT +><DT +>4.2.2. <A +HREF="http.html#http-iis" +>Microsoft <SPAN +CLASS="productname" +>Internet Information Services</SPAN +></A +></DT +><DT +>4.2.3. <A +HREF="http.html#http-aol" +>AOL Server</A +></DT +></DL +></DD +><DT +>4.3. <A HREF="extraconfig.html" >Optional Additional Configuration</A ></DT ><DD ><DL ><DT ->4.2.1. <A -HREF="extraconfig.html#AEN832" +>4.3.1. <A +HREF="extraconfig.html#AEN852" >Dependency Charts</A ></DT ><DT ->4.2.2. <A -HREF="extraconfig.html#AEN847" +>4.3.2. <A +HREF="extraconfig.html#AEN867" >Bug Graphs</A ></DT ><DT ->4.2.3. <A -HREF="extraconfig.html#AEN860" +>4.3.3. <A +HREF="extraconfig.html#AEN880" >The Whining Cron</A ></DT ><DT ->4.2.4. <A +>4.3.4. <A HREF="extraconfig.html#bzldap" >LDAP Authentication</A ></DT ><DT ->4.2.5. <A +>4.3.5. <A HREF="extraconfig.html#content-type" >Preventing untrusted Bugzilla content from executing malicious Javascript code</A ></DT ><DT ->4.2.6. <A -HREF="extraconfig.html#directoryindex" -><TT -CLASS="filename" ->directoryindex</TT -> for the Bugzilla default page.</A -></DT -><DT ->4.2.7. <A +>4.3.6. <A HREF="extraconfig.html#mod_perl" >Bugzilla and <TT CLASS="filename" @@ -180,7 +200,7 @@ CLASS="filename" ></A ></DT ><DT ->4.2.8. <A +>4.3.7. <A HREF="extraconfig.html#mod-throttle" ><TT CLASS="filename" @@ -192,19 +212,19 @@ CLASS="filename" ></DL ></DD ><DT ->4.3. <A +>4.4. <A HREF="os-specific.html" >OS Specific Installation Notes</A ></DT ><DD ><DL ><DT ->4.3.1. <A +>4.4.1. <A HREF="os-specific.html#os-win32" >Microsoft Windows</A ></DT ><DT ->4.3.2. <A +>4.4.2. <A HREF="os-specific.html#os-macosx" ><SPAN CLASS="productname" @@ -212,66 +232,65 @@ CLASS="productname" ></A ></DT ><DT ->4.3.3. <A +>4.4.3. <A HREF="os-specific.html#os-mandrake" >Linux-Mandrake 8.0</A ></DT ></DL ></DD ><DT ->4.4. <A -HREF="http.html" ->HTTP Server Configuration</A +>4.5. <A +HREF="security.html" +>Bugzilla Security</A ></DT ><DD ><DL ><DT ->4.4.1. <A -HREF="http.html#http-apache" ->Apache <SPAN -CLASS="productname" ->httpd</SPAN -></A +>4.5.1. <A +HREF="security.html#security-networking" +>TCP/IP Ports</A ></DT ><DT ->4.4.2. <A -HREF="http.html#http-iis" ->Microsoft <SPAN -CLASS="productname" ->Internet Information Services</SPAN -></A +>4.5.2. <A +HREF="security.html#security-mysql" +>MySQL</A ></DT ><DT ->4.4.3. <A -HREF="http.html#http-aol" ->AOL Server</A +>4.5.3. <A +HREF="security.html#security-daemon" +>Daemon Accounts</A +></DT +><DT +>4.5.4. <A +HREF="security.html#security-access" +>Web Server Access Controls</A ></DT ></DL ></DD ><DT ->4.5. <A +>4.6. <A HREF="troubleshooting.html" >Troubleshooting</A ></DT ><DD ><DL ><DT ->4.5.1. <A -HREF="troubleshooting.html#AEN1157" +>4.6.1. <A +HREF="troubleshooting.html#AEN1215" >Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A ></DT ><DT ->4.5.2. <A -HREF="troubleshooting.html#AEN1162" +>4.6.2. <A +HREF="troubleshooting.html#AEN1220" >DBD::Sponge::db prepare failed</A ></DT ><DT ->4.5.3. <A +>4.6.3. <A HREF="troubleshooting.html#paranoid-security" >cannot chdir(/var/spool/mqueue)</A ></DT ><DT ->4.5.4. <A +>4.6.4. <A HREF="troubleshooting.html#trouble-filetemp" >Your vendor has not defined Fcntl macro O_NOINHERIT</A ></DT @@ -296,7 +315,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="userpreferences.html" +HREF="reporting.html" ACCESSKEY="P" >Prev</A ></TD @@ -324,7 +343,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->User Preferences</TD +>Reports</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/integration.html b/docs/html/integration.html index 95de9c9ed..afa57d6c9 100644 --- a/docs/html/integration.html +++ b/docs/html/integration.html @@ -4,16 +4,18 @@ >Integrating Bugzilla with Third-Party Tools</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="Administering Bugzilla" -HREF="administration.html"><LINK +TITLE="Customising Bugzilla" +HREF="customization.html"><LINK REL="PREVIOUS" -TITLE="Upgrading to New Releases" -HREF="upgrading.html"><LINK +TITLE="MySQL Bugzilla Database Introduction" +HREF="dbdoc.html"><LINK REL="NEXT" TITLE="The Bugzilla FAQ" HREF="faq.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="upgrading.html" +HREF="dbdoc.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 5. Administering Bugzilla</TD +>Chapter 6. Customising Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="integration" ></A ->5.10. Integrating Bugzilla with Third-Party Tools</H1 +>6.5. Integrating Bugzilla with Third-Party Tools</H1 ><DIV CLASS="section" ><H2 @@ -82,7 +85,7 @@ CLASS="section" ><A NAME="bonsai" ></A ->5.10.1. Bonsai</H2 +>6.5.1. Bonsai</H2 ><P >Bonsai is a web-based tool for managing <A @@ -108,7 +111,7 @@ CLASS="section" ><A NAME="cvs" ></A ->5.10.2. CVS</H2 +>6.5.2. CVS</H2 ><P >CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P @@ -144,7 +147,7 @@ CLASS="section" ><A NAME="scm" ></A ->5.10.3. Perforce SCM</H2 +>6.5.3. Perforce SCM</H2 ><P >You can find the project page for Bugzilla and Teamtrack Perforce integration (p4dti) at: @@ -184,9 +187,22 @@ CLASS="section" ><A NAME="tinderbox" ></A ->5.10.4. Tinderbox/Tinderbox2</H2 +>6.5.4. Tinderbox/Tinderbox2</H2 ><P ->We need Tinderbox integration information.</P +>Tinderbox is a continuous-build system which can integrate with + Bugzilla - see + <A +HREF="http://www.mozilla.org/projects/tinderbox" +TARGET="_top" +>http://www.mozilla.org/projects/tinderbox</A +> for details + of Tinderbox, and + <A +HREF="http://tinderbox.mozilla.org/showbuilds.cgi" +TARGET="_top" +>http://tinderbox.mozilla.org/showbuilds.cgi</A +> to see it + in action.</P ></DIV ></DIV ><DIV @@ -205,7 +221,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="upgrading.html" +HREF="dbdoc.html" ACCESSKEY="P" >Prev</A ></TD @@ -233,13 +249,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Upgrading to New Releases</TD +>MySQL Bugzilla Database Introduction</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="administration.html" +HREF="customization.html" ACCESSKEY="U" >Up</A ></TD diff --git a/docs/html/introduction.html b/docs/html/introduction.html index f29b8c9c7..b64b61df1 100644 --- a/docs/html/introduction.html +++ b/docs/html/introduction.html @@ -4,16 +4,18 @@ >Introduction</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Document Conventions" HREF="conventions.html"><LINK REL="NEXT" TITLE="What is Bugzilla?" -HREF="whatis.html"></HEAD +HREF="what-is-bugzilla.html"></HEAD ><BODY CLASS="chapter" BGCOLOR="#FFFFFF" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -55,7 +58,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="whatis.html" +HREF="what-is-bugzilla.html" ACCESSKEY="N" >Next</A ></TD @@ -80,13 +83,18 @@ CLASS="TOC" ></DT ><DT >2.1. <A -HREF="whatis.html" +HREF="what-is-bugzilla.html" >What is Bugzilla?</A ></DT ><DT >2.2. <A -HREF="why.html" ->Why Should We Use Bugzilla?</A +HREF="why-tracking.html" +>Why use a bug-tracking system?</A +></DT +><DT +>2.3. <A +HREF="why-bugzilla.html" +>Why use Bugzilla?</A ></DT ></DL ></DIV @@ -125,7 +133,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="whatis.html" +HREF="what-is-bugzilla.html" ACCESSKEY="N" >Next</A ></TD diff --git a/docs/html/list.html b/docs/html/list.html new file mode 100644 index 000000000..6f6be44db --- /dev/null +++ b/docs/html/list.html @@ -0,0 +1,209 @@ +<HTML +><HEAD +><TITLE +>Bug Lists</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Searching for Bugs" +HREF="query.html"><LINK +REL="NEXT" +TITLE="Filing Bugs" +HREF="bugreports.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="query.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="bugreports.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="list" +></A +>3.4. Bug Lists</H1 +><P +>If you run a search, a list of matching bugs will be returned. + </P +><P +>The format of the list is configurable. For example, it can be + sorted by clicking the column headings. Other useful features can be + accessed using the links at the bottom of the list: + <P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +> <EM +>Long Format:</EM +> + + this gives you a large page with a non-editable summary of the fields + of each bug.</TD +></TR +><TR +><TD +> <EM +>Change Columns:</EM +> + + change the bug attributes which appear in the list.</TD +></TR +><TR +><TD +> <EM +>Change several bugs at once:</EM +> + + If your account is sufficiently empowered, you can make the same + change to all the bugs in the list - for example, changing their + owner.</TD +></TR +><TR +><TD +> <EM +>Send mail to bug owners:</EM +> + + Sends mail to the owners of all bugs on the list.</TD +></TR +><TR +><TD +> <EM +>Edit this query:</EM +> + + 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.</TD +></TR +></TBODY +></TABLE +><P +></P +> + </P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="query.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="bugreports.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Searching for Bugs</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Filing Bugs</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/milestones.html b/docs/html/milestones.html new file mode 100644 index 000000000..8188a3d43 --- /dev/null +++ b/docs/html/milestones.html @@ -0,0 +1,210 @@ +<HTML +><HEAD +><TITLE +>Milestones</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Administering Bugzilla" +HREF="administration.html"><LINK +REL="PREVIOUS" +TITLE="Versions" +HREF="versions.html"><LINK +REL="NEXT" +TITLE="Voting" +HREF="voting.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="versions.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 5. Administering Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="voting.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="milestones" +></A +>5.6. Milestones</H1 +><P +>Milestones are "targets" that you plan to get a bug fixed by. For + example, you have a bug that you plan to fix for your 3.0 release, it + would be assigned the milestone of 3.0.</P +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Milestone options will only appear for a Product if you turned + on the "usetargetmilestone" Param in the "Edit Parameters" screen. + </P +></TD +></TR +></TABLE +></DIV +><P +>To create new Milestones, set Default Milestones, and set + Milestone URL:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>Select "Edit milestones" from the "Edit product" page.</P +></LI +><LI +><P +>Select "Add" in the bottom right corner. + text</P +></LI +><LI +><P +>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".</P +></LI +><LI +><P +>From the Edit product screen, you can enter the URL of a + page which gives information about your milestones and what + they mean. </P +></LI +></OL +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="versions.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="voting.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Versions</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="administration.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Voting</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/myaccount.html b/docs/html/myaccount.html new file mode 100644 index 000000000..17ba42dda --- /dev/null +++ b/docs/html/myaccount.html @@ -0,0 +1,207 @@ +<HTML +><HEAD +><TITLE +>Create a Bugzilla Account</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="NEXT" +TITLE="Anatomy of a Bug" +HREF="bug_page.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="using.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="bug_page.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="myaccount" +></A +>3.1. Create a Bugzilla Account</H1 +><P +>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: + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/" +TARGET="_top" +>http://landfill.bugzilla.org/bugzilla-tip/</A +>. + </P +><P +></P +><OL +TYPE="1" +><LI +><P +>Click the + <SPAN +CLASS="QUOTE" +>"Open a new Bugzilla account"</SPAN +> + + link, enter your email address and, optionally, your name in the + spaces provided, then click + <SPAN +CLASS="QUOTE" +>"Create Account"</SPAN +> + + .</P +></LI +><LI +><P +>Within moments, you should receive an email to the address + you provided, which contains your login name (generally the + same as the email address), and a password. + This password is randomly generated, but can be + changed to something more memorable.</P +></LI +><LI +><P +>Click the + <SPAN +CLASS="QUOTE" +>"Log In"</SPAN +> + link in the footer at the bottom of the page in your browser, + enter your email address and password into the spaces provided, and + click + <SPAN +CLASS="QUOTE" +>"Login"</SPAN +>. + </P +></LI +></OL +><P +>You are now logged in. Bugzilla uses cookies to remember you are + logged in so, unless you have cookies disabled or your IP address changes, + you should not have to log in again.</P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="bug_page.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Using Bugzilla</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Anatomy of a Bug</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/newversions.html b/docs/html/newversions.html index 4648dd842..9dad859db 100644 --- a/docs/html/newversions.html +++ b/docs/html/newversions.html @@ -4,9 +4,11 @@ >New Versions</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="About This Guide" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -79,31 +82,17 @@ NAME="newversions" > This is the 2.17.5 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. - This version of the guide, like its associated Bugzilla version is a - development version. Information is subject to change between now and - when 2.18 is released. + This version of the guide, like its associated Bugzilla version, is a + development version. - 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. </P ><P > The newest version of this guide can always be found at <A HREF="http://www.bugzilla.org" TARGET="_top" >http://www.bugzilla.org</A ->; including - documentation for past releases and the current development version. - </P -><P -> The documentation for the most recent stable release of Bugzilla can also - be found at - <A -HREF="http://www.tldp.org" -TARGET="_top" ->The Linux Documentation Project</A ->. +>; however, you should read the version + which came with the Bugzilla release you are using. </P ><P > The latest version of this document can always be checked out via CVS. diff --git a/docs/html/os-specific.html b/docs/html/os-specific.html index f3d786844..425fc5b6b 100644 --- a/docs/html/os-specific.html +++ b/docs/html/os-specific.html @@ -4,9 +4,11 @@ >OS Specific Installation Notes</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Installation" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Optional Additional Configuration" HREF="extraconfig.html"><LINK REL="NEXT" -TITLE="HTTP Server Configuration" -HREF="http.html"></HEAD +TITLE="Bugzilla Security" +HREF="security.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="http.html" +HREF="security.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="os-specific" ></A ->4.3. OS Specific Installation Notes</H1 +>4.4. OS Specific Installation Notes</H1 ><P >Many aspects of the Bugzilla installation can be affected by the the operating system you choose to install it on. Sometimes it can be made @@ -97,9 +100,9 @@ CLASS="section" ><A NAME="os-win32" ></A ->4.3.1. Microsoft Windows</H2 +>4.4.1. Microsoft Windows</H2 ><P ->Making Bugzilla work on windows is still a very painful processes. +>Making Bugzilla work on windows is still a painful processes. The Bugzilla Team is working to make it easier, but that goal is not considered a top priority. If you wish to run Bugzilla, we still recommend doing so on a Unix based system such as GNU/Linux. As of this @@ -123,7 +126,7 @@ CLASS="section" ><A NAME="win32-perl" ></A ->4.3.1.1. Win32 Perl</H3 +>4.4.1.1. Win32 Perl</H3 ><P >Perl for Windows can be obtained from <A HREF="http://www.activestate.com/" @@ -144,12 +147,12 @@ CLASS="section" ><A NAME="win32-perlmodules" ></A ->4.3.1.2. Perl Modules on Win32</H3 +>4.4.1.2. Perl Modules on Win32</H3 ><P >Bugzilla on Windows requires the same perl modules found in <A HREF="stepbystep.html#install-perlmodules" ->Section 4.1.3</A +>Section 4.1.5</A >. The main difference is that windows uses <A HREF="glossary.html#gloss-ppm" @@ -256,18 +259,11 @@ CLASS="section" ><A NAME="win32-code-changes" ></A ->4.3.1.3. Code changes required to run on win32</H3 +>4.4.1.3. Code changes required to run on win32</H3 ><P ->Unfortunately, Bugzilla still doesn't run "out of the box" on - Windows. There is work in progress to make this easier, but until that - happens code will have to be modified. This section is an attempt to - list the required changes. It is an attempt to be all inclusive, but - there may be other changes required. If you find something is missing, - please file a bug in <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. +>As Bugzilla still doesn't run "out of the box" on + Windows, code has to be modified. This section is an attempt to + list the required changes. </P ><DIV CLASS="section" @@ -276,7 +272,7 @@ CLASS="section" ><A NAME="win32-code-checksetup" ></A ->4.3.1.3.1. Changes to <TT +>4.4.1.3.1. Changes to <TT CLASS="filename" >checksetup.pl</TT ></H4 @@ -363,7 +359,7 @@ CLASS="section" ><A NAME="win32-code-bugmail" ></A ->4.3.1.3.2. Changes to <TT +>4.4.1.3.2. Changes to <TT CLASS="filename" >BugMail.pm</TT ></H4 @@ -375,11 +371,8 @@ TARGET="_top" >bug 84876</A > lands), the - simplest way is to have Net::SMTP installed and change this (in - <TT -CLASS="filename" ->Bugzilla/BugMail.pm</TT ->):</P + simplest way is to have the Net::SMTP Perl module installed and + change this:</P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -444,19 +437,19 @@ CLASS="section" ><A NAME="win32-http" ></A ->4.3.1.4. Serving the web pages</H3 +>4.4.1.4. Serving the web pages</H3 ><P >As is the case on Unix based systems, any web server should be able to handle Bugzilla; however, the Bugzilla Team still recommends Apache whenever asked. No matter what web server you choose, be sure to pay attention to the security notes in <A HREF="security.html#security-access" ->Section 5.6.4</A +>Section 4.5.4</A >. More information on configuring specific web servers can be found in <A HREF="http.html" ->Section 4.4</A +>Section 4.2</A >. </P ><DIV @@ -505,7 +498,7 @@ CLASS="section" ><A NAME="os-macosx" ></A ->4.3.2. <SPAN +>4.4.2. <SPAN CLASS="productname" >Mac OS X</SPAN ></H2 @@ -699,7 +692,7 @@ CLASS="section" ><A NAME="os-mandrake" ></A ->4.3.3. Linux-Mandrake 8.0</H2 +>4.4.3. Linux-Mandrake 8.0</H2 ><P >Linux-Mandrake 8.0 includes every required and optional library for Bugzilla. The easiest way to install them is by using the @@ -826,7 +819,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="http.html" +HREF="security.html" ACCESSKEY="N" >Next</A ></TD @@ -850,7 +843,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->HTTP Server Configuration</TD +>Bugzilla Security</TD ></TR ></TABLE ></DIV diff --git a/docs/html/parameters.html b/docs/html/parameters.html index 3cb7af23f..ce3c39b48 100644 --- a/docs/html/parameters.html +++ b/docs/html/parameters.html @@ -4,9 +4,11 @@ >Bugzilla Configuration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -164,7 +167,7 @@ CLASS="command" standard type, and Bugzilla does not yet take advantage of features such as transactions which would justify this speed decrease. The Bugzilla team are, however, happy to hear about any experiences with - row level locking and Bugzilla</P + row level locking and Bugzilla.</P ><P >The <SPAN CLASS="QUOTE" @@ -177,7 +180,7 @@ CLASS="QUOTE" an enormous performance improvement when implemented on extremely high-traffic Bugzilla databases.</P ><P -> As a guide, mozilla.org began needing +> As a guide, on reasonably old hardware, mozilla.org began needing <SPAN CLASS="QUOTE" >"shadowdb"</SPAN diff --git a/docs/html/patches.html b/docs/html/patches.html index c2791a34c..201d896ef 100644 --- a/docs/html/patches.html +++ b/docs/html/patches.html @@ -1,22 +1,21 @@ <HTML ><HEAD ><TITLE ->Useful Patches and Utilities for Bugzilla</TITLE +>Contrib</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="MySQL Bugzilla Database Introduction" -HREF="dbdoc.html"><LINK +TITLE="The Bugzilla FAQ" +HREF="faq.html"><LINK REL="NEXT" -TITLE="Apache - mod_rewrite - - magic" -HREF="rewrite.html"></HEAD +TITLE="Command-line Search Interface" +HREF="cmdline.html"></HEAD ><BODY CLASS="appendix" BGCOLOR="#FFFFFF" @@ -36,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="dbdoc.html" +HREF="faq.html" ACCESSKEY="P" >Prev</A ></TD @@ -58,7 +58,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="rewrite.html" +HREF="cmdline.html" ACCESSKEY="N" >Next</A ></TD @@ -73,35 +73,14 @@ CLASS="appendix" ><A NAME="patches" ></A ->Appendix C. Useful Patches and Utilities for Bugzilla</H1 -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->C.1. <A -HREF="rewrite.html" ->Apache - <TT +>Appendix B. Contrib</H1 +><P +>There are a number of unofficial Bugzilla add-ons in the + <TT CLASS="filename" ->mod_rewrite</TT +>$BUGZILLA_ROOT/contrib/</TT > - - magic</A -></DT -><DT ->C.2. <A -HREF="cmdline.html" ->Command-line Bugzilla Queries</A -></DT -></DL -></DIV -><P ->Are you looking for a way to put your Bugzilla into overdrive? Catch - some of the niftiest tricks here in this section.</P + directory. This section documents them.</P ></DIV ><DIV CLASS="NAVFOOTER" @@ -119,7 +98,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="dbdoc.html" +HREF="faq.html" ACCESSKEY="P" >Prev</A ></TD @@ -137,7 +116,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="rewrite.html" +HREF="cmdline.html" ACCESSKEY="N" >Next</A ></TD @@ -147,7 +126,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->MySQL Bugzilla Database Introduction</TD +>The Bugzilla FAQ</TD ><TD WIDTH="34%" ALIGN="center" @@ -157,13 +136,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Apache - <TT -CLASS="filename" ->mod_rewrite</TT -> - - magic</TD +>Command-line Search Interface</TD ></TR ></TABLE ></DIV diff --git a/docs/html/patchviewer.html b/docs/html/patchviewer.html new file mode 100644 index 000000000..8ef1267b4 --- /dev/null +++ b/docs/html/patchviewer.html @@ -0,0 +1,303 @@ +<HTML +><HEAD +><TITLE +>Patch Viewer</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Filing Bugs" +HREF="bugreports.html"><LINK +REL="NEXT" +TITLE="Hints and Tips" +HREF="hintsandtips.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="bugreports.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="hintsandtips.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="patchviewer" +></A +>3.6. Patch Viewer</H1 +><P +>Viewing and reviewing patches in Bugzilla is often difficult due to + lack of context, improper format and the inherent readability issues that + raw patches present. Patch Viewer is an enhancement to Bugzilla designed + to fix that by offering increased context, linking to sections, and + integrating with Bonsai, LXR and CVS.</P +><P +>Patch viewer allows you to:</P +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +>View patches in color, with side-by-side view rather than trying + to interpret the contents of the patch.</TD +></TR +><TR +><TD +>See the difference between two patches.</TD +></TR +><TR +><TD +>Get more context in a patch.</TD +></TR +><TR +><TD +>Collapse and expand sections of a patch for easy + reading.</TD +></TR +><TR +><TD +>Link to a particular section of a patch for discussion or + review</TD +></TR +><TR +><TD +>Go to Bonsai or LXR to see more context, blame, and + cross-references for the part of the patch you are looking at</TD +></TR +><TR +><TD +>Create a rawtext unified format diff out of any patch, no + matter what format it came from</TD +></TR +></TBODY +></TABLE +><P +></P +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_view" +></A +>3.6.1. Viewing Patches in Patch Viewer</H2 +><P +>The main way to view a patch in patch viewer is to click on the + "Diff" link next to a patch in the Attachments list on a bug. You may + also do this within the edit window by clicking the "View Attachment As + Diff" button in the Edit Attachment screen.</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_diff" +></A +>3.6.2. Seeing the Difference Between Two Patches</H2 +><P +>To see the difference between two patches, you must first view the + newer patch in Patch Viewer. Then select the older patch from the + dropdown at the top of the page ("Differences between [dropdown] and + this patch") and click the "Diff" button. This will show you what + is new or changed in the newer patch.</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_context" +></A +>3.6.3. Getting More Context in a Patch</H2 +><P +>To get more context in a patch, you put a number in the textbox at + the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. + This will give you that many lines of context before and after each + change. Alternatively, you can click on the "File" link there and it + will show each change in the full context of the file. This feature only + works against files that were diffed using "cvs diff".</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_collapse" +></A +>3.6.4. Collapsing and Expanding Sections of a Patch</H2 +><P +>To view only a certain set of files in a patch (for example, if a + patch is absolutely huge and you want to only review part of it at a + time), you can click the "(+)" and "(-)" links next to each file (to + expand it or collapse it). If you want to collapse all files or expand + all files, you can click the "Collapse All" and "Expand All" links at the + top of the page.</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_link" +></A +>3.6.5. Linking to a Section of a Patch</H2 +><P +>To link to a section of a patch (for example, if you want to be + able to give someone a URL to show them which part you are talking + about) you simply click the "Link Here" link on the section header. The + resulting URL can be copied and used in discussion. (Copy Link + Location in Mozilla works as well.)</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_bonsai_lxr" +></A +>3.6.6. Going to Bonsai and LXR</H2 +><P +>To go to Bonsai to get blame for the lines you are interested in, + you can click the "Lines XX-YY" link on the section header you are + interested in. This works even if the patch is against an old + version of the file, since Bonsai stores all versions of the file.</P +><P +>To go to LXR, you click on the filename on the file header + (unfortunately, since LXR only does the most recent version, line + numbers are likely to rot).</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="patchviewer_unified_diff" +></A +>3.6.7. Creating a Unified Diff</H2 +><P +>If the patch is not in a format that you like, you can turn it + into a unified diff format by clicking the "Raw Unified" link at the top + of the page.</P +></DIV +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="bugreports.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="hintsandtips.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Filing Bugs</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Hints and Tips</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/products.html b/docs/html/products.html new file mode 100644 index 000000000..7debc465f --- /dev/null +++ b/docs/html/products.html @@ -0,0 +1,193 @@ +<HTML +><HEAD +><TITLE +>Products</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Administering Bugzilla" +HREF="administration.html"><LINK +REL="PREVIOUS" +TITLE="User Administration" +HREF="useradmin.html"><LINK +REL="NEXT" +TITLE="Components" +HREF="components.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="useradmin.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 5. Administering Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="components.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="products" +></A +>5.3. Products</H1 +><P +> <A +HREF="glossary.html#gloss-product" +><I +CLASS="glossterm" +> Products</I +></A +> + + 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...)</P +><P +>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.</P +><P +>To create a new product:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>Select "products" from the footer</P +></LI +><LI +><P +>Select the "Add" link in the bottom right</P +></LI +><LI +><P +>Enter the name of the product and a description. The + Description field may contain HTML.</P +></LI +></OL +><P +>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. + </P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="useradmin.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="components.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>User Administration</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="administration.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Components</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html index f72058bfd..119131417 100644 --- a/docs/html/programadmin.html +++ b/docs/html/programadmin.html @@ -4,9 +4,11 @@ >Product, Component, Milestone, and Version Administration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD diff --git a/docs/html/query.html b/docs/html/query.html new file mode 100644 index 000000000..0fd4fc182 --- /dev/null +++ b/docs/html/query.html @@ -0,0 +1,167 @@ +<HTML +><HEAD +><TITLE +>Searching for Bugs</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="Anatomy of a Bug" +HREF="bug_page.html"><LINK +REL="NEXT" +TITLE="Bug Lists" +HREF="list.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="bug_page.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="list.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="query" +></A +>3.3. Searching for Bugs</H1 +><P +>The Bugzilla Search page is is the interface where you can find + any bug report, comment, or patch currently in the Bugzilla system. You + can play with it here: + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi" +TARGET="_top" +>http://landfill.bugzilla.org/bugzilla-tip/query.cgi</A +>.</P +><P +>The Search page has controls for selecting different possible + values for all of the fields in a bug, as described above. For some + fields, multiple values can be selected. In those cases, Bugzilla + returns bugs where the content of the field matches any one of the selected + values. If none is selected, then the field can take any value.</P +><P +>Once you've run a search, you can save it as a Saved Search, which + appears in the page footer.</P +><P +>Highly advanced querying is done using Boolean Charts. See the + Boolean Charts help link on the Search page for more information.</P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="bug_page.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="list.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Anatomy of a Bug</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Bug Lists</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/reporting.html b/docs/html/reporting.html new file mode 100644 index 000000000..df5d9d0ce --- /dev/null +++ b/docs/html/reporting.html @@ -0,0 +1,150 @@ +<HTML +><HEAD +><TITLE +>Reports</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Using Bugzilla" +HREF="using.html"><LINK +REL="PREVIOUS" +TITLE="User Preferences" +HREF="userpreferences.html"><LINK +REL="NEXT" +TITLE="Installation" +HREF="installation.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="userpreferences.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 3. Using Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="installation.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="reporting" +></A +>3.9. Reports</H1 +><P +><EM +>To be written</EM +></P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="userpreferences.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="installation.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>User Preferences</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Installation</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/rewrite.html b/docs/html/rewrite.html index e986b814e..61e76de03 100644 --- a/docs/html/rewrite.html +++ b/docs/html/rewrite.html @@ -7,9 +7,11 @@ magic</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Useful Patches and Utilities for Bugzilla" @@ -39,7 +41,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -55,7 +58,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix C. Useful Patches and Utilities for Bugzilla</TD +>Appendix B. Useful Patches and Utilities for Bugzilla</TD ><TD WIDTH="10%" ALIGN="right" @@ -77,7 +80,7 @@ CLASS="section" ><A NAME="rewrite" ></A ->C.1. Apache +>B.1. Apache <TT CLASS="filename" >mod_rewrite</TT diff --git a/docs/html/security.html b/docs/html/security.html index c3fa07499..4bf56506e 100644 --- a/docs/html/security.html +++ b/docs/html/security.html @@ -4,19 +4,21 @@ >Bugzilla Security</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" -TITLE="Administering Bugzilla" -HREF="administration.html"><LINK +TITLE="Installation" +HREF="installation.html"><LINK REL="PREVIOUS" -TITLE="Groups and Group Security" -HREF="groups.html"><LINK +TITLE="OS Specific Installation Notes" +HREF="os-specific.html"><LINK REL="NEXT" -TITLE="Template Customization" -HREF="cust-templates.html"></HEAD +TITLE="Troubleshooting" +HREF="troubleshooting.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="groups.html" +HREF="os-specific.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 5. Administering Bugzilla</TD +>Chapter 4. Installation</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="cust-templates.html" +HREF="troubleshooting.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="security" ></A ->5.6. Bugzilla Security</H1 +>4.5. Bugzilla Security</H1 ><DIV CLASS="warning" ><P @@ -101,66 +104,10 @@ VALIGN="TOP" guidelines seriously, even for Bugzilla machines hidden away behind your firewall. 80% of all computer trespassers are insiders, not anonymous crackers.</P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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 <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. - </P -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="warning" -><P -></P -><TABLE -CLASS="warning" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/warning.gif" -HSPACE="5" -ALT="Warning"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ><P >This is not meant to be a comprehensive list of every possible - security issue regarding the tools mentioned in this section. There is + security issue pertaining to the software mentioned in this section. + There is no subsitute for reading the information written by the authors of any software running on your system. </P @@ -175,10 +122,10 @@ CLASS="section" ><A NAME="security-networking" ></A ->5.6.1. TCP/IP Ports</H2 +>4.5.1. TCP/IP Ports</H2 ><P >TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla - only needs 1... 2 if you need to use features that require e-mail such + only needs 1, or 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 @@ -193,7 +140,7 @@ CLASS="section" ><A NAME="security-mysql" ></A ->5.6.2. MySQL</H2 +>4.5.2. MySQL</H2 ><P >MySQL ships by default with many settings that should be changed. By defaults it allows anybody to connect from localhost without a @@ -322,7 +269,7 @@ CLASS="section" ><A NAME="security-daemon" ></A ->5.6.3. Daemon Accounts</H2 +>4.5.3. Daemon Accounts</H2 ><P >Many daemons, such as Apache's httpd and MySQL's mysqld default to running as either <SPAN @@ -344,8 +291,8 @@ CLASS="QUOTE" <SPAN CLASS="QUOTE" >"nobody"</SPAN -> and one of them gets comprimised, they all get - comprimised. For this reason it is recommended that you create a user +> and one of them gets compromised, they all get + compromised. For this reason it is recommended that you create a user account for each daemon. </P ><DIV @@ -397,20 +344,17 @@ CLASS="section" ><A NAME="security-access" ></A ->5.6.4. Web Server Access Controls</H2 +>4.5.4. Web Server Access Controls</H2 ><P >There are many files that are placed in the Bugzilla directory area that should not be accessable from the web. Because of the way - 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 - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659" -TARGET="_top" -> bug 44659</A -> for more information. + Bugzilla is currently laid out, the list of what should and should + not be accessible is rather complicated. + </P +><P +>Users of Apache don't need to worry about this, however, because + Bugzilla ships with .htaccess files which restrict access to all the + sensitive files in this section. Users of other webservers, read on. </P ><P ></P @@ -588,49 +532,6 @@ COMPACT="COMPACT" ></UL ></LI ></UL -><DIV -CLASS="tip" -><P -></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Bugzilla ships with the ability to generate - <TT -CLASS="filename" ->.htaccess</TT -> files instructing - <A -HREF="glossary.html#gloss-apache" -><I -CLASS="glossterm" ->Apache</I -></A -> which files - should and should not be accessible. For more information, see - <A -HREF="http.html#http-apache" ->Section 4.4.1</A ->. - </P -></TD -></TR -></TABLE -></DIV ><P >You should test to make sure that the files mentioned above are not accessible from the Internet, especially your @@ -706,7 +607,7 @@ VALIGN="TOP" ><P >You should check <A HREF="http.html" ->Section 4.4</A +>Section 4.2</A > to see if instructions have been included for your web server. You should also compare those instructions with this list to make sure everything is properly @@ -734,7 +635,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="groups.html" +HREF="os-specific.html" ACCESSKEY="P" >Prev</A ></TD @@ -752,7 +653,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="cust-templates.html" +HREF="troubleshooting.html" ACCESSKEY="N" >Next</A ></TD @@ -762,13 +663,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Groups and Group Security</TD +>OS Specific Installation Notes</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="administration.html" +HREF="installation.html" ACCESSKEY="U" >Up</A ></TD @@ -776,7 +677,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Template Customization</TD +>Troubleshooting</TD ></TR ></TABLE ></DIV diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html index 48e443702..dfbf1a14b 100644 --- a/docs/html/stepbystep.html +++ b/docs/html/stepbystep.html @@ -4,9 +4,11 @@ >Step-by-step Install</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Installation" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Installation" HREF="installation.html"><LINK REL="NEXT" -TITLE="Optional Additional Configuration" -HREF="extraconfig.html"></HEAD +TITLE="HTTP Server Configuration" +HREF="http.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="extraconfig.html" +HREF="http.html" ACCESSKEY="N" >Next</A ></TD @@ -86,7 +89,7 @@ CLASS="productname" that make it harder. We have tried to collect that information in <A HREF="os-specific.html" ->Section 4.3</A +>Section 4.4</A >, so be sure to check out that section before you start your installation. </P @@ -116,7 +119,7 @@ VALIGN="TOP" to install Bugzilla on Windows, be sure to see <A HREF="os-specific.html#os-win32" ->Section 4.3.1</A +>Section 4.4.1</A >. </P ></TD @@ -163,6 +166,10 @@ VALIGN="TOP" with administrative access to install it for you. </P ><P +> You are strongly recommended to make a backup of your system + before installing Bugzilla and at regular intervals thereafter. + </P +><P >The listing below is a basic step-by-step list. More information can be found in the sections below. Minimum versions will be included in parenthesis where appropriate. @@ -174,15 +181,6 @@ TYPE="1" ><LI ><P ><A -HREF="stepbystep.html#install-mysql" ->Install MySQL</A -> - (3.23.41) - </P -></LI -><LI -><P -><A HREF="stepbystep.html#install-perl" >Install Perl</A > @@ -192,9 +190,10 @@ HREF="stepbystep.html#install-perl" ><LI ><P ><A -HREF="stepbystep.html#install-perlmodules" ->Install Perl Modules</A +HREF="stepbystep.html#install-mysql" +>Install MySQL</A > + (3.23.41) </P ></LI ><LI @@ -216,6 +215,14 @@ HREF="stepbystep.html#install-bzfiles" ><LI ><P ><A +HREF="stepbystep.html#install-perlmodules" +>Install Perl Modules</A +> + </P +></LI +><LI +><P +><A HREF="stepbystep.html#install-setupdatabase" >Setup the MySQL Database</A > @@ -228,9 +235,31 @@ CLASS="section" ><H2 CLASS="section" ><A +NAME="install-perl" +></A +>4.1.1. Perl</H2 +><P +>Any machine that doesn't have Perl on it is a sad machine indeed. + Perl can be got in source form from <A +HREF="http://www.perl.com" +TARGET="_top" +>http://www.perl.com</A +>. + There are also binary versions available for many platforms, most of which + are linked to from perl.com. + Although Bugzilla runs with perl 5.6, + 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.8.</P +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A NAME="install-mysql" ></A ->4.1.1. MySQL</H2 +>4.1.2. MySQL</H2 ><P >Visit the MySQL homepage at <A @@ -335,31 +364,327 @@ CLASS="option" > option as mentioned in <A HREF="security.html#security-mysql" ->Section 5.6.2</A +>Section 4.5.2</A > for the added security. </P +><DIV +CLASS="section" +><H3 +CLASS="section" +><A +NAME="install-setupdatabase" +></A +>4.1.2.1. Configuring MySQL</H3 +><P +>This first thing you'll want to do is make sure you've given the + <SPAN +CLASS="QUOTE" +>"root"</SPAN +> user a password as suggested in + <A +HREF="security.html#security-mysql" +>Section 4.5.2</A +>. For clarity, these instructions will + assume that your MySQL user for Bugzilla will be <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +>, + the database will be called <SPAN +CLASS="QUOTE" +>"bugs_db"</SPAN +> and the password for + the <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> user is <SPAN +CLASS="QUOTE" +>"bugs_password"</SPAN +>. You + should, of course, substitute the values you intend to use for your site. + </P +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Most people use <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> for both the user and + database name. + </P +></TD +></TR +></TABLE +></DIV +><P +>Next, we use an SQL <B +CLASS="command" +>GRANT</B +> command to create a + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + user, and grant sufficient permissions for checksetup.pl, which we'll + use later, to work its magic. This also restricts the + <SPAN +CLASS="QUOTE" +>"bugs_user"</SPAN +> + user to operations within a database called + <SPAN +CLASS="QUOTE" +>"bugs_db"</SPAN +>, and only allows the account to connect from + <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +>. + Modify it to reflect your setup if you will be connecting from + another machine or as a different user.</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="screen" +> <TT +CLASS="prompt" +>mysql></TT +> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, + DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost + IDENTIFIED BY 'bugs_password'; + <TT +CLASS="prompt" +>mysql></TT +> FLUSH PRIVILEGES; + </PRE +></FONT +></TD +></TR +></TABLE +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>If you are using MySQL 4, the bugs user also needs to be granted + the <TT +CLASS="computeroutput" +>LOCK TABLES</TT +> and + <TT +CLASS="computeroutput" +>CREATE TEMPORARY TABLES</TT +> permissions. + </P +></TD +></TR +></TABLE +></DIV +></DIV ></DIV ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="install-perl" +NAME="install-webserver" ></A ->4.1.2. Perl</H2 +>4.1.3. HTTP Server</H2 ><P ->Any machine that doesn't have Perl on it is a sad machine indeed. - Perl can be got in source form from <A -HREF="http://www.perl.com" +>You have freedom of choice here, pretty much any web server that + is capable of running <A +HREF="glossary.html#gloss-cgi" +><I +CLASS="glossterm" +>CGI</I +></A +> + scripts will work. <A +HREF="http.html" +>Section 4.2</A +> has more information about + configuring web servers to work with Bugzilla. + </P +><DIV +CLASS="note" +><P +></P +><TABLE +CLASS="note" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>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 by filing a bug in <A +HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" TARGET="_top" ->http://www.perl.com</A +>Bugzilla Documentation</A >. - There are also binary versions available for many platforms, most of which - are linked to from perl.com. - Although Bugzilla runs with perl 5.6, - 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.8.</P + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="section" +><H2 +CLASS="section" +><A +NAME="install-bzfiles" +></A +>4.1.4. Bugzilla</H2 +><P +>You should untar the Bugzilla files into a directory that you're + willing to make writable by the default web server user (probably + <SPAN +CLASS="QUOTE" +>"nobody"</SPAN +>). + You may decide to put the files in the main web space for your + web server or perhaps in + <TT +CLASS="filename" +>/usr/local</TT +> + with a symbolic link in the web space that points to the Bugzilla + directory.</P +><DIV +CLASS="tip" +><P +></P +><TABLE +CLASS="tip" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/tip.gif" +HSPACE="5" +ALT="Tip"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>If you symlink the bugzilla directory into your Apache's HTML + hierarchy, you may receive + <SPAN +CLASS="errorname" +>Forbidden</SPAN +> + errors unless you add the + <SPAN +CLASS="QUOTE" +>"FollowSymLinks"</SPAN +> + directive to the <Directory> entry for the HTML root + in httpd.conf.</P +></TD +></TR +></TABLE +></DIV +><P +>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 + <TT +CLASS="filename" +>checksetup.pl</TT +> + script, which locks down your installation.</P +><DIV +CLASS="caution" +><P +></P +><TABLE +CLASS="caution" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/caution.gif" +HSPACE="5" +ALT="Caution"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>The default Bugzilla distribution is not designed to be placed + in a <TT +CLASS="filename" +>cgi-bin</TT +> directory (this + includes any directory which is configured using the + <TT +CLASS="option" +>ScriptAlias</TT +> directive of Apache). + </P +></TD +></TR +></TABLE +></DIV ></DIV ><DIV CLASS="section" @@ -368,7 +693,7 @@ CLASS="section" ><A NAME="install-perlmodules" ></A ->4.1.3. Perl Modules</H2 +>4.1.5. Perl Modules</H2 ><P >Perl modules can be found using <A @@ -396,7 +721,7 @@ HREF="stepbystep.html#install-perlmodules-cpan" > for CPAN and <A HREF="os-specific.html#win32-perlmodules" ->Section 4.3.1.2</A +>Section 4.4.1.2</A > for PPM. </P ><DIV @@ -522,7 +847,7 @@ BORDER="0" ALT="(2)"></A ></DT ><DD ->The process of untaring the module as defined in +>The process of untarring the module as defined in <A HREF="stepbystep.html#cpan-moduletar" ><A @@ -773,7 +1098,7 @@ CLASS="section" ><A NAME="install-modules-bundle-bugzilla" ></A ->4.1.3.1. Bundle::Bugzilla</H3 +>4.1.5.1. Bundle::Bugzilla</H3 ><P >If you are running at least perl 5.6.1, you can save yourself a lot of time by using Bundle::Bugzilla. This bundle contains every module @@ -852,7 +1177,7 @@ CLASS="section" ><A NAME="install-modules-appconfig" ></A ->4.1.3.2. AppConfig (1.52)</H3 +>4.1.5.2. AppConfig (1.52)</H3 ><P >Dependency for Template Toolkit. We probably don't need to specifically check for it anymore. @@ -865,7 +1190,7 @@ CLASS="section" ><A NAME="install-modules-cgi" ></A ->4.1.3.3. CGI (2.88)</H3 +>4.1.5.3. CGI (2.88)</H3 ><P >The CGI module parses form elements and cookies and does many other usefule things. It come as a part of recent perl distributions, but @@ -898,7 +1223,7 @@ CLASS="section" ><A NAME="install-modules-data-dumper" ></A ->4.1.3.4. Data::Dumper (any)</H3 +>4.1.5.4. Data::Dumper (any)</H3 ><P >The Data::Dumper module provides data structure persistence for Perl (similar to Java's serialization). It comes with later @@ -932,7 +1257,7 @@ CLASS="section" ><A NAME="install-modules-date-format" ></A ->4.1.3.5. TimeDate modules (2.21)</H3 +>4.1.5.5. TimeDate modules (2.21)</H3 ><P >Many of the more common date/time/calendar related Perl modules have been grouped into a bundle similar to the MySQL modules bundle. @@ -967,7 +1292,7 @@ CLASS="section" ><A NAME="install-modules-dbi" ></A ->4.1.3.6. DBI (1.32)</H3 +>4.1.5.6. DBI (1.32)</H3 ><P >The DBI module is a generic Perl module used the MySQL-related modules. As long as your Perl installation was done @@ -1001,7 +1326,7 @@ CLASS="section" ><A NAME="install-modules-dbd-mysql" ></A ->4.1.3.7. MySQL-related modules</H3 +>4.1.5.7. MySQL-related modules</H3 ><P >The Perl/MySQL interface requires a few mutually-dependent Perl modules. These modules are grouped together into the the @@ -1046,7 +1371,7 @@ CLASS="section" ><A NAME="install-file-spec" ></A ->4.1.3.8. File::Spec (0.82)</H3 +>4.1.5.8. File::Spec (0.82)</H3 ><P >File::Spec is a perl module that allows file operations, such as generating full path names, to work cross platform. @@ -1078,7 +1403,7 @@ CLASS="section" ><A NAME="install-modules-file-temp" ></A ->4.1.3.9. File::Temp (any)</H3 +>4.1.5.9. File::Temp (any)</H3 ><P >File::Temp is used to generate a temporary filename that is guaranteed to be unique. It comes as a standard part of perl @@ -1110,7 +1435,7 @@ CLASS="section" ><A NAME="install-modules-template" ></A ->4.1.3.10. Template Toolkit (2.08)</H3 +>4.1.5.10. Template Toolkit (2.08)</H3 ><P >When you install Template Toolkit, you'll get asked various questions about features to enable. The defaults are fine, except @@ -1144,7 +1469,7 @@ CLASS="section" ><A NAME="install-modules-text-wrap" ></A ->4.1.3.11. Text::Wrap (2001.0131)</H3 +>4.1.5.11. Text::Wrap (2001.0131)</H3 ><P >Text::Wrap is designed to proved intelligent text wrapping. </P @@ -1170,7 +1495,7 @@ CLASS="section" ><A NAME="install-modules-gd" ></A ->4.1.3.12. GD (1.20) [optional]</H3 +>4.1.5.12. GD (1.20) [optional]</H3 ><P >The GD library was written by Thomas Boutell a long while ago to programmatically generate images in C. Since then it's become the @@ -1280,7 +1605,7 @@ CLASS="section" ><A NAME="install-modules-chart-base" ></A ->4.1.3.13. Chart::Base (0.99c) [optional]</H3 +>4.1.5.13. Chart::Base (0.99c) [optional]</H3 ><P >The Chart module provides Bugzilla with on-the-fly charting abilities. It can be installed in the usual fashion after it has been @@ -1309,7 +1634,7 @@ CLASS="section" ><A NAME="install-modules-xml-parser" ></A ->4.1.3.14. XML::Parser (any) [Optional]</H3 +>4.1.5.14. XML::Parser (any) [Optional]</H3 ><P >XML::Parser is used by the <TT CLASS="filename" @@ -1344,7 +1669,7 @@ CLASS="section" ><A NAME="install-modules-gd-graph" ></A ->4.1.3.15. GD::Graph (any) [Optional]</H3 +>4.1.5.15. GD::Graph (any) [Optional]</H3 ><P >In addition to GD listed above, the reporting interface of Bugzilla needs to have the GD::Graph module installed. @@ -1376,7 +1701,7 @@ CLASS="section" ><A NAME="install-modules-gd-text-align" ></A ->4.1.3.16. GD::Text::Align (any) [Optional]</H3 +>4.1.5.16. GD::Text::Align (any) [Optional]</H3 ><P >GD::Text::Align, as the name implies, is used to draw aligned strings of text. It is needed by the reporting interface. @@ -1408,7 +1733,7 @@ CLASS="section" ><A NAME="install-modules-mime-parser" ></A ->4.1.3.17. MIME::Parser (any) [Optional]</H3 +>4.1.5.17. MIME::Parser (any) [Optional]</H3 ><P >MIME::Parser is only needed if you want to use the e-mail interface located in the <TT @@ -1443,7 +1768,7 @@ CLASS="section" ><A NAME="install-modules-patchreader" ></A ->4.1.3.18. PatchReader (0.9.1) [Optional]</H3 +>4.1.5.18. PatchReader (0.9.1) [Optional]</H3 ><P >PatchReader is only needed if you want to use Patch Viewer, a Bugzilla feature to format patches in a pretty HTML fashion. There are a @@ -1479,350 +1804,15 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="install-webserver" -></A ->4.1.4. HTTP Server</H2 -><P ->You have freedom of choice here, pretty much any web server that - is capable of running <A -HREF="glossary.html#gloss-cgi" -><I -CLASS="glossterm" ->CGI</I -></A -> - scripts will work. <A -HREF="http.html" ->Section 4.4</A -> has more information about - configuring web servers to work with Bugzilla. - </P -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->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 by filing a bug in <A -HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation" -TARGET="_top" ->Bugzilla Documentation</A ->. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="install-bzfiles" -></A ->4.1.5. Bugzilla</H2 -><P ->You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <SPAN -CLASS="QUOTE" ->"nobody"</SPAN ->). - You may decide to put the files in the main web space for your - web server or perhaps in - <TT -CLASS="filename" ->/usr/local</TT -> - with a symbolic link in the web space that points to the Bugzilla - directory.</P -><DIV -CLASS="tip" -><P -></P -><TABLE -CLASS="tip" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->If you symlink the bugzilla directory into your Apache's HTML - hierarchy, you may receive - <SPAN -CLASS="errorname" ->Forbidden</SPAN -> - errors unless you add the - <SPAN -CLASS="QUOTE" ->"FollowSymLinks"</SPAN -> - directive to the <Directory> entry for the HTML root - in httpd.conf.</P -></TD -></TR -></TABLE -></DIV -><P ->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 - <TT -CLASS="filename" ->checksetup.pl</TT -> - script, which locks down your installation.</P -><DIV -CLASS="caution" -><P -></P -><TABLE -CLASS="caution" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/caution.gif" -HSPACE="5" -ALT="Caution"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->The default Bugzilla distribution is not designed to be placed - in a <TT -CLASS="filename" ->cgi-bin</TT -> directory (this - includes any directory which is configured using the - <TT -CLASS="option" ->ScriptAlias</TT -> directive of Apache). This will probably - change as part of - <A -HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659" -TARGET="_top" ->bug - 44659</A ->. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="install-setupdatabase" +NAME="AEN748" ></A ->4.1.6. Setting Up the MySQL Database</H2 -><P ->After you've gotten all the software installed and working you're - ready to start preparing the database for its life as the back end to - a high quality bug tracker.</P -><P ->This first thing you'll want to do is make sure you've given the - <SPAN -CLASS="QUOTE" ->"root"</SPAN -> user a password as suggested in - <A -HREF="security.html#security-mysql" ->Section 5.6.2</A ->. For clarity, these instructions will - assume that your MySQL user for Bugzilla will be <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN ->, - the database will be called <SPAN -CLASS="QUOTE" ->"bugs_db"</SPAN -> and the password for - the <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> user is <SPAN -CLASS="QUOTE" ->"bugs_password"</SPAN ->. You - should, of course, substitute the values you intend to use for your site. - </P -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->Most people use <SPAN -CLASS="QUOTE" ->"bugs"</SPAN -> for both the user and - database name. - </P -></TD -></TR -></TABLE -></DIV -><P ->Next, we use an SQL <B -CLASS="command" ->GRANT</B -> command to create a - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> - user, and grant sufficient permissions for checksetup.pl, which we'll - use later, to work its magic. This also restricts the - <SPAN -CLASS="QUOTE" ->"bugs_user"</SPAN -> - user to operations within a database called - <SPAN -CLASS="QUOTE" ->"bugs_db"</SPAN ->, and only allows the account to connect from - <SPAN -CLASS="QUOTE" ->"localhost"</SPAN ->. - Modify it to reflect your setup if you will be connecting from - another machine or as a different user.</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="screen" -> <TT -CLASS="prompt" ->mysql></TT -> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, - DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost - IDENTIFIED BY 'bugs_password'; -<TT -CLASS="prompt" ->mysql></TT -> FLUSH PRIVILEGES; - </PRE -></FONT -></TD -></TR -></TABLE -><DIV -CLASS="note" -><P -></P -><TABLE -CLASS="note" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->If you are using MySQL 4, the bugs user also needs to be granted - the <TT -CLASS="computeroutput" ->LOCK TABLES</TT -> and - <TT -CLASS="computeroutput" ->CREATE TEMPORARY TABLES</TT -> permissions. - </P -></TD -></TR -></TABLE -></DIV -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="AEN795" -></A ->4.1.7. <TT +>4.1.6. <TT CLASS="filename" >checksetup.pl</TT ></H2 ><P ->Next, run the magic checksetup.pl script. (Many thanks to - <A -HREF="mailto:holgerschurig@nikocity.de" -TARGET="_top" ->Holger Schurig</A -> - for writing this script!) - This script is designed to make sure your perl modules are the correct +>Next, run the magic checksetup.pl script. + This is designed to make sure your perl modules are the correct version and your MySQL database and other configuration options are consistent with the Bugzilla CGI files. It will make sure Bugzilla files and directories have reasonable @@ -1958,9 +1948,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN826" +NAME="AEN778" ></A ->4.1.8. Configuring Bugzilla</H2 +>4.1.7. Configuring Bugzilla</H2 ><P > You should run through the parameters on the Edit Parameters page (link in the footer) and set them all to appropriate values. @@ -2005,7 +1995,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="extraconfig.html" +HREF="http.html" ACCESSKEY="N" >Next</A ></TD @@ -2029,7 +2019,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Optional Additional Configuration</TD +>HTTP Server Configuration</TD ></TR ></TABLE ></DIV diff --git a/docs/html/troubleshooting.html b/docs/html/troubleshooting.html index 07bfcda23..420ff29aa 100644 --- a/docs/html/troubleshooting.html +++ b/docs/html/troubleshooting.html @@ -4,16 +4,18 @@ >Troubleshooting</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Installation" HREF="installation.html"><LINK REL="PREVIOUS" -TITLE="HTTP Server Configuration" -HREF="http.html"><LINK +TITLE="Bugzilla Security" +HREF="security.html"><LINK REL="NEXT" TITLE="Administering Bugzilla" HREF="administration.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="http.html" +HREF="security.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="troubleshooting" ></A ->4.5. Troubleshooting</H1 +>4.6. Troubleshooting</H1 ><P >This section gives solutions to common Bugzilla installation problems. @@ -84,9 +87,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1157" +NAME="AEN1215" ></A ->4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 +>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2 ><P > Try executing <B CLASS="command" @@ -109,9 +112,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="AEN1162" +NAME="AEN1220" ></A ->4.5.2. DBD::Sponge::db prepare failed</H2 +>4.6.2. DBD::Sponge::db prepare failed</H2 ><P > The following error message may appear due to a bug in DBD::mysql (over which the Bugzilla team have no control): @@ -197,7 +200,7 @@ CLASS="section" ><A NAME="paranoid-security" ></A ->4.5.3. cannot chdir(/var/spool/mqueue)</H2 +>4.6.3. cannot chdir(/var/spool/mqueue)</H2 ><P >If you are installing Bugzilla on SuSE Linux, or some other distributions with @@ -255,7 +258,7 @@ CLASS="section" ><A NAME="trouble-filetemp" ></A ->4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 +>4.6.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2 ><P >This is caused by a bug in the version of <SPAN @@ -375,7 +378,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="http.html" +HREF="security.html" ACCESSKEY="P" >Prev</A ></TD @@ -403,7 +406,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->HTTP Server Configuration</TD +>Bugzilla Security</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/upgrading.html b/docs/html/upgrading.html index c4ce31cb1..e2956299d 100644 --- a/docs/html/upgrading.html +++ b/docs/html/upgrading.html @@ -4,19 +4,21 @@ >Upgrading to New Releases</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" HREF="administration.html"><LINK REL="PREVIOUS" -TITLE="Change Permission Customization" -HREF="cust-change-permissions.html"><LINK +TITLE="Groups and Group Security" +HREF="groups.html"><LINK REL="NEXT" -TITLE="Integrating Bugzilla with Third-Party Tools" -HREF="integration.html"></HEAD +TITLE="Customising Bugzilla" +HREF="customization.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="cust-change-permissions.html" +HREF="groups.html" ACCESSKEY="P" >Prev</A ></TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="integration.html" +HREF="customization.html" ACCESSKEY="N" >Next</A ></TD @@ -512,8 +515,8 @@ NAME="upgrade-patches" revisions to go from the most recent revision to the new one. You could also read the release notes and grab the patches attached to the mentioned bug, but it is safer to use the released patch file as - sometimes patches get changed before they get checked in (for minor - spelling fixes and the like). It is also theorectically possible to + sometimes patches get changed before they get checked in. + It is also theoretically possible to scour the fixed bug list and pick and choose which patches to apply from a point release, but this is not recommended either as what you'll end up with is a hodge podge Bugzilla that isn't really any version. @@ -613,7 +616,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="cust-change-permissions.html" +HREF="groups.html" ACCESSKEY="P" >Prev</A ></TD @@ -631,7 +634,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="integration.html" +HREF="customization.html" ACCESSKEY="N" >Next</A ></TD @@ -641,7 +644,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Change Permission Customization</TD +>Groups and Group Security</TD ><TD WIDTH="34%" ALIGN="center" @@ -655,7 +658,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Integrating Bugzilla with Third-Party Tools</TD +>Customising Bugzilla</TD ></TR ></TABLE ></DIV diff --git a/docs/html/useradmin.html b/docs/html/useradmin.html index af4df1315..12781474c 100644 --- a/docs/html/useradmin.html +++ b/docs/html/useradmin.html @@ -4,9 +4,11 @@ >User Administration</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Bugzilla Configuration" HREF="parameters.html"><LINK REL="NEXT" -TITLE="Product, Component, Milestone, and Version Administration" -HREF="programadmin.html"></HEAD +TITLE="Products" +HREF="products.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="programadmin.html" +HREF="products.html" ACCESSKEY="N" >Next</A ></TD @@ -295,7 +298,7 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->Don't disable the administrator account!</P +>Don't disable all the administrator accounts!</P ></TD ></TR ></TABLE @@ -466,7 +469,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="programadmin.html" +HREF="products.html" ACCESSKEY="N" >Next</A ></TD @@ -490,7 +493,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Product, Component, Milestone, and Version Administration</TD +>Products</TD ></TR ></TABLE ></DIV diff --git a/docs/html/userpreferences.html b/docs/html/userpreferences.html index d6bbde5d0..b68244461 100644 --- a/docs/html/userpreferences.html +++ b/docs/html/userpreferences.html @@ -4,9 +4,11 @@ >User Preferences</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Using Bugzilla" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Hints and Tips" HREF="hintsandtips.html"><LINK REL="NEXT" -TITLE="Installation" -HREF="installation.html"></HEAD +TITLE="Reports" +HREF="reporting.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -58,7 +61,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="installation.html" +HREF="reporting.html" ACCESSKEY="N" >Next</A ></TD @@ -74,11 +77,11 @@ CLASS="section" ><A NAME="userpreferences" ></A ->3.3. User Preferences</H1 +>3.8. User Preferences</H1 ><P >Once you have logged in, you can customise various aspects of Bugzilla via the "Edit prefs" link in the page footer. - The preferences are split into four tabs:</P + The preferences are split into three tabs:</P ><DIV CLASS="section" ><H2 @@ -86,7 +89,7 @@ CLASS="section" ><A NAME="accountsettings" ></A ->3.3.1. Account Settings</H2 +>3.8.1. Account Settings</H2 ><P >On this tab, you can change your basic account information, including your password, email address and real name. For security @@ -111,13 +114,19 @@ CLASS="section" ><A NAME="emailsettings" ></A ->3.3.2. Email Settings</H2 +>3.8.2. Email Settings</H2 ><P >On this tab you can reduce or increase the amount of email sent you from Bugzilla, opting in our out depending on your relationship to - 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.)</P + the bug and the change that was made to it. + </P +><P +> You can also do further filtering on the client side by + using the X-Bugzilla-Reason mail header which Bugzilla + adds to all bugmail. This tells you what relationship you have to the + bug in question, + and can be any of Owner, Reporter, QAcontact, CClist, Voter and + WatchingComponent.</P ><P >By entering user email names, delineated by commas, into the "Users to watch" text entry box you can receive a copy of all the @@ -158,23 +167,9 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="footersettings" -></A ->3.3.3. Page Footer</H2 -><P ->On the Search page, you can store queries in Bugzilla, so if you - regularly run a particular query it is just a drop-down menu away. - Once you have a stored query, you can come - here to request that it also be displayed in your page footer.</P -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A NAME="permissionsettings" ></A ->3.3.4. Permissions</H2 +>3.8.3. Permissions</H2 ><P >This is a purely informative page which outlines your current permissions on this installation of Bugzilla - what product groups you @@ -216,7 +211,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="installation.html" +HREF="reporting.html" ACCESSKEY="N" >Next</A ></TD @@ -240,7 +235,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Installation</TD +>Reports</TD ></TR ></TABLE ></DIV diff --git a/docs/html/using.html b/docs/html/using.html index ce518187a..24b7c5c78 100644 --- a/docs/html/using.html +++ b/docs/html/using.html @@ -4,16 +4,18 @@ >Using Bugzilla</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Why Should We Use Bugzilla?" -HREF="why.html"><LINK +TITLE="Why use Bugzilla?" +HREF="why-bugzilla.html"><LINK REL="NEXT" -TITLE="How do I use Bugzilla?" -HREF="how.html"></HEAD +TITLE="Create a Bugzilla Account" +HREF="myaccount.html"></HEAD ><BODY CLASS="chapter" BGCOLOR="#FFFFFF" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -41,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="why.html" +HREF="why-bugzilla.html" ACCESSKEY="P" >Prev</A ></TD @@ -55,7 +58,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="how.html" +HREF="myaccount.html" ACCESSKEY="N" >Next</A ></TD @@ -80,108 +83,150 @@ CLASS="TOC" ></DT ><DT >3.1. <A -HREF="how.html" ->How do I use Bugzilla?</A -></DT -><DD -><DL -><DT ->3.1.1. <A -HREF="how.html#myaccount" +HREF="myaccount.html" >Create a Bugzilla Account</A ></DT ><DT ->3.1.2. <A -HREF="how.html#bug_page" +>3.2. <A +HREF="bug_page.html" >Anatomy of a Bug</A ></DT ><DT ->3.1.3. <A -HREF="how.html#query" +>3.3. <A +HREF="query.html" >Searching for Bugs</A ></DT ><DT ->3.1.4. <A -HREF="how.html#list" +>3.4. <A +HREF="list.html" >Bug Lists</A ></DT ><DT ->3.1.5. <A -HREF="how.html#bugreports" +>3.5. <A +HREF="bugreports.html" >Filing Bugs</A ></DT ><DT ->3.1.6. <A -HREF="how.html#patchviewer" +>3.6. <A +HREF="patchviewer.html" >Patch Viewer</A ></DT +><DD +><DL +><DT +>3.6.1. <A +HREF="patchviewer.html#patchviewer_view" +>Viewing Patches in Patch Viewer</A +></DT +><DT +>3.6.2. <A +HREF="patchviewer.html#patchviewer_diff" +>Seeing the Difference Between Two Patches</A +></DT +><DT +>3.6.3. <A +HREF="patchviewer.html#patchviewer_context" +>Getting More Context in a Patch</A +></DT +><DT +>3.6.4. <A +HREF="patchviewer.html#patchviewer_collapse" +>Collapsing and Expanding Sections of a Patch</A +></DT +><DT +>3.6.5. <A +HREF="patchviewer.html#patchviewer_link" +>Linking to a Section of a Patch</A +></DT +><DT +>3.6.6. <A +HREF="patchviewer.html#patchviewer_bonsai_lxr" +>Going to Bonsai and LXR</A +></DT +><DT +>3.6.7. <A +HREF="patchviewer.html#patchviewer_unified_diff" +>Creating a Unified Diff</A +></DT ></DL ></DD ><DT ->3.2. <A +>3.7. <A HREF="hintsandtips.html" >Hints and Tips</A ></DT ><DD ><DL ><DT ->3.2.1. <A -HREF="hintsandtips.html#AEN407" +>3.7.1. <A +HREF="hintsandtips.html#AEN358" >Autolinkification</A ></DT ><DT ->3.2.2. <A +>3.7.2. <A HREF="hintsandtips.html#quicksearch" >Quicksearch</A ></DT ><DT ->3.2.3. <A +>3.7.3. <A HREF="hintsandtips.html#commenting" >Comments</A ></DT ><DT ->3.2.4. <A +>3.7.4. <A HREF="hintsandtips.html#attachments" >Attachments</A ></DT ><DT ->3.2.5. <A -HREF="hintsandtips.html#AEN436" +>3.7.5. <A +HREF="hintsandtips.html#AEN388" >Filing Bugs</A ></DT ></DL ></DD ><DT ->3.3. <A +>3.8. <A HREF="userpreferences.html" >User Preferences</A ></DT ><DD ><DL ><DT ->3.3.1. <A +>3.8.1. <A HREF="userpreferences.html#accountsettings" >Account Settings</A ></DT ><DT ->3.3.2. <A +>3.8.2. <A HREF="userpreferences.html#emailsettings" >Email Settings</A ></DT ><DT ->3.3.3. <A -HREF="userpreferences.html#footersettings" ->Page Footer</A -></DT -><DT ->3.3.4. <A +>3.8.3. <A HREF="userpreferences.html#permissionsettings" >Permissions</A ></DT ></DL ></DD +><DT +>3.9. <A +HREF="reporting.html" +>Reports</A +></DT ></DL ></DIV +><P +>This section contains information for end-users of Bugzilla. + There is a Bugzilla test installation, called + <A +HREF="http://landfill.bugzilla.org/bugzilla-tip/" +TARGET="_top" +>Landfill</A +>, + which you are welcome to play with (if it's up.) + However, it does not necessarily + have all Bugzilla features enabled, and runs an up-to-the-minute version, + so some things may not quite work as this document describes.</P ></DIV ><DIV CLASS="NAVFOOTER" @@ -199,7 +244,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="why.html" +HREF="why-bugzilla.html" ACCESSKEY="P" >Prev</A ></TD @@ -217,7 +262,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="how.html" +HREF="myaccount.html" ACCESSKEY="N" >Next</A ></TD @@ -227,7 +272,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Why Should We Use Bugzilla?</TD +>Why use Bugzilla?</TD ><TD WIDTH="34%" ALIGN="center" @@ -237,7 +282,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->How do I use Bugzilla?</TD +>Create a Bugzilla Account</TD ></TR ></TABLE ></DIV diff --git a/docs/html/variant-fenris.html b/docs/html/variant-fenris.html index 13afcbcc2..d5b8c5386 100644 --- a/docs/html/variant-fenris.html +++ b/docs/html/variant-fenris.html @@ -4,9 +4,11 @@ >Loki Bugzilla (Fenris)</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD diff --git a/docs/html/variant-issuezilla.html b/docs/html/variant-issuezilla.html index 599b04a7e..f6a455cf2 100644 --- a/docs/html/variant-issuezilla.html +++ b/docs/html/variant-issuezilla.html @@ -4,9 +4,11 @@ >Issuezilla</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD diff --git a/docs/html/variant-perforce.html b/docs/html/variant-perforce.html index 7f90944f7..59ee72177 100644 --- a/docs/html/variant-perforce.html +++ b/docs/html/variant-perforce.html @@ -4,9 +4,11 @@ >Perforce SCM</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD diff --git a/docs/html/variant-redhat.html b/docs/html/variant-redhat.html index 8560dac6c..ff0872544 100644 --- a/docs/html/variant-redhat.html +++ b/docs/html/variant-redhat.html @@ -4,9 +4,11 @@ >Red Hat Bugzilla</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" @@ -15,8 +17,8 @@ REL="PREVIOUS" TITLE="Bugzilla Variants and Competitors" HREF="variants.html"><LINK REL="NEXT" -TITLE="Loki Bugzilla (Fenris)" -HREF="variant-fenris.html"></HEAD +TITLE="Scarab" +HREF="variant-scarab.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -52,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix D. Bugzilla Variants and Competitors</TD +>Appendix C. Bugzilla Variants and Competitors</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="variant-fenris.html" +HREF="variant-scarab.html" ACCESSKEY="N" >Next</A ></TD @@ -74,22 +77,19 @@ CLASS="section" ><A NAME="variant-redhat" ></A ->D.1. Red Hat Bugzilla</H1 +>C.1. Red Hat Bugzilla</H1 ><P ->Red Hat's old fork of Bugzilla which was based on version 2.8 is now - obsolete. The newest version in use is based on version 2.17.1 and is in - the process of being integrated into the main Bugzilla source tree. The +>Red Hat's has its own version of Bugzilla based on version 2.17.1. + The main changes are that the back-end is modified to work with PostgreSQL instead of MySQL and they have - custom templates to get their desired look and feel, but other than that it - is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of - effort to make sure that the changes he made could be integrated back into - the main tree. + custom templates to get their desired look and feel. + Dave Lawrence of Red Hat has filed <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304" TARGET="_top" ->Bug 98304</A +>bug 98304</A > - exists to track this integration. + exists to track the integration of his PostgreSQL support. </P ><P >URL: <A @@ -135,7 +135,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="variant-fenris.html" +HREF="variant-scarab.html" ACCESSKEY="N" >Next</A ></TD @@ -159,7 +159,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Loki Bugzilla (Fenris)</TD +>Scarab</TD ></TR ></TABLE ></DIV diff --git a/docs/html/variant-scarab.html b/docs/html/variant-scarab.html index d7684ed26..c54a431c5 100644 --- a/docs/html/variant-scarab.html +++ b/docs/html/variant-scarab.html @@ -4,19 +4,21 @@ >Scarab</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" HREF="variants.html"><LINK REL="PREVIOUS" -TITLE="Issuezilla" -HREF="variant-issuezilla.html"><LINK +TITLE="Red Hat Bugzilla" +HREF="variant-redhat.html"><LINK REL="NEXT" -TITLE="Perforce SCM" -HREF="variant-perforce.html"></HEAD +TITLE="SourceForge" +HREF="variant-sourceforge.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="variant-issuezilla.html" +HREF="variant-redhat.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,13 +55,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix D. Bugzilla Variants and Competitors</TD +>Appendix C. Bugzilla Variants and Competitors</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="variant-perforce.html" +HREF="variant-sourceforge.html" ACCESSKEY="N" >Next</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="variant-scarab" ></A ->D.4. Scarab</H1 +>C.2. Scarab</H1 ><P >Scarab is a new open source bug-tracking system built using Java Servlet technology. It is currently at version 1.0 beta 13.</P @@ -104,7 +107,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="variant-issuezilla.html" +HREF="variant-redhat.html" ACCESSKEY="P" >Prev</A ></TD @@ -122,7 +125,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="variant-perforce.html" +HREF="variant-sourceforge.html" ACCESSKEY="N" >Next</A ></TD @@ -132,7 +135,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Issuezilla</TD +>Red Hat Bugzilla</TD ><TD WIDTH="34%" ALIGN="center" @@ -146,7 +149,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Perforce SCM</TD +>SourceForge</TD ></TR ></TABLE ></DIV diff --git a/docs/html/variant-sourceforge.html b/docs/html/variant-sourceforge.html index b9601607f..f610427b3 100644 --- a/docs/html/variant-sourceforge.html +++ b/docs/html/variant-sourceforge.html @@ -4,16 +4,18 @@ >SourceForge</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Bugzilla Variants and Competitors" HREF="variants.html"><LINK REL="PREVIOUS" -TITLE="Perforce SCM" -HREF="variant-perforce.html"><LINK +TITLE="Scarab" +HREF="variant-scarab.html"><LINK REL="NEXT" TITLE="GNU Free Documentation License" HREF="gfdl.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="variant-perforce.html" +HREF="variant-scarab.html" ACCESSKEY="P" >Prev</A ></TD @@ -52,7 +55,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Appendix D. Bugzilla Variants and Competitors</TD +>Appendix C. Bugzilla Variants and Competitors</TD ><TD WIDTH="10%" ALIGN="right" @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="variant-sourceforge" ></A ->D.6. SourceForge</H1 +>C.3. SourceForge</H1 ><P >SourceForge is a way of coordinating geographically distributed free software and open source projects over the Internet. @@ -105,7 +108,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="variant-perforce.html" +HREF="variant-scarab.html" ACCESSKEY="P" >Prev</A ></TD @@ -133,7 +136,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Perforce SCM</TD +>Scarab</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/variants.html b/docs/html/variants.html index 731738863..3491e1c30 100644 --- a/docs/html/variants.html +++ b/docs/html/variants.html @@ -4,9 +4,11 @@ >Bugzilla Variants and Competitors</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Command-line Bugzilla Queries" @@ -33,7 +35,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -70,7 +73,7 @@ CLASS="appendix" ><A NAME="variants" ></A ->Appendix D. Bugzilla Variants and Competitors</H1 +>Appendix C. Bugzilla Variants and Competitors</H1 ><DIV CLASS="TOC" ><DL @@ -79,32 +82,17 @@ CLASS="TOC" >Table of Contents</B ></DT ><DT ->D.1. <A +>C.1. <A HREF="variant-redhat.html" >Red Hat Bugzilla</A ></DT ><DT ->D.2. <A -HREF="variant-fenris.html" ->Loki Bugzilla (Fenris)</A -></DT -><DT ->D.3. <A -HREF="variant-issuezilla.html" ->Issuezilla</A -></DT -><DT ->D.4. <A +>C.2. <A HREF="variant-scarab.html" >Scarab</A ></DT ><DT ->D.5. <A -HREF="variant-perforce.html" ->Perforce SCM</A -></DT -><DT ->D.6. <A +>C.3. <A HREF="variant-sourceforge.html" >SourceForge</A ></DT diff --git a/docs/html/versions.html b/docs/html/versions.html new file mode 100644 index 000000000..9e5fc8b5f --- /dev/null +++ b/docs/html/versions.html @@ -0,0 +1,173 @@ +<HTML +><HEAD +><TITLE +>Versions</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Administering Bugzilla" +HREF="administration.html"><LINK +REL="PREVIOUS" +TITLE="Components" +HREF="components.html"><LINK +REL="NEXT" +TITLE="Milestones" +HREF="milestones.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="components.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 5. Administering Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="milestones.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="versions" +></A +>5.5. Versions</H1 +><P +>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 earliest version known to have + the bug. + </P +><P +>To create and edit Versions:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>From the "Edit product" screen, select "Edit Versions"</P +></LI +><LI +><P +>You will notice that the product already has the default + version "undefined". Click the "Add" link in the bottom right.</P +></LI +><LI +><P +>Enter the name of the Version. This field takes text only. + Then click the "Add" button.</P +></LI +></OL +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="components.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="milestones.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Components</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="administration.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Milestones</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/voting.html b/docs/html/voting.html index f791108b0..3e01dd181 100644 --- a/docs/html/voting.html +++ b/docs/html/voting.html @@ -4,16 +4,18 @@ >Voting</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Administering Bugzilla" HREF="administration.html"><LINK REL="PREVIOUS" -TITLE="Product, Component, Milestone, and Version Administration" -HREF="programadmin.html"><LINK +TITLE="Milestones" +HREF="milestones.html"><LINK REL="NEXT" TITLE="Groups and Group Security" HREF="groups.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="programadmin.html" +HREF="milestones.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,7 +77,7 @@ CLASS="section" ><A NAME="voting" ></A ->5.4. Voting</H1 +>5.7. Voting</H1 ><P >Voting allows users to be given a pot of votes which they can allocate to bugs, to indicate that they'd like them fixed. @@ -145,7 +148,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="programadmin.html" +HREF="milestones.html" ACCESSKEY="P" >Prev</A ></TD @@ -173,7 +176,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Product, Component, Milestone, and Version Administration</TD +>Milestones</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/what-is-bugzilla.html b/docs/html/what-is-bugzilla.html new file mode 100644 index 000000000..0c6f1e4ee --- /dev/null +++ b/docs/html/what-is-bugzilla.html @@ -0,0 +1,155 @@ +<HTML +><HEAD +><TITLE +>What is Bugzilla?</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Introduction" +HREF="introduction.html"><LINK +REL="PREVIOUS" +TITLE="Introduction" +HREF="introduction.html"><LINK +REL="NEXT" +TITLE="Why use a bug-tracking system?" +HREF="why-tracking.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="introduction.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 2. Introduction</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="why-tracking.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="what-is-bugzilla" +></A +>2.1. What is Bugzilla?</H1 +><P +> Bugzilla is a bug- or issue-tracking system. Bug-tracking + systems allow individual or groups of developers effectively to keep track + of outstanding problems with their products. + </P +><P +><EM +>Do we need more here?</EM +></P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="why-tracking.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Introduction</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Why use a bug-tracking system?</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/whatis.html b/docs/html/whatis.html index e92d899a3..a4f0cb41f 100644 --- a/docs/html/whatis.html +++ b/docs/html/whatis.html @@ -4,9 +4,11 @@ >What is Bugzilla?</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Introduction" @@ -15,7 +17,7 @@ REL="PREVIOUS" TITLE="Introduction" HREF="introduction.html"><LINK REL="NEXT" -TITLE="Why Should We Use Bugzilla?" +TITLE="Why use a bug-tracking system?" HREF="why.html"></HEAD ><BODY CLASS="section" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -78,73 +81,7 @@ NAME="whatis" ><P > 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. - </P -><P ->Bugzilla boasts many advanced features. These include: - <P -></P -><UL -><LI -><P ->Powerful searching</P -></LI -><LI -><P ->User-configurable email notifications of bug changes</P -></LI -><LI -><P ->Full change history</P -></LI -><LI -><P ->Inter-bug dependency tracking and graphing</P -></LI -><LI -><P ->Excellent attachment management</P -></LI -><LI -><P ->Integrated, product-based, granular security schema</P -></LI -><LI -><P ->Fully security-audited, and runs under Perl's taint mode</P -></LI -><LI -><P ->A robust, stable RDBMS back-end</P -></LI -><LI -><P ->Web, XML, email and console interfaces</P -></LI -><LI -><P ->Completely customisable and/or localisable web user - interface</P -></LI -><LI -><P ->Extensive configurability</P -></LI -><LI -><P ->Smooth upgrade pathway between versions</P -></LI -></UL -> + of outstanding problems with their products. </P ></DIV ><DIV @@ -205,7 +142,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Why Should We Use Bugzilla?</TD +>Why use a bug-tracking system?</TD ></TR ></TABLE ></DIV diff --git a/docs/html/why-bugzilla.html b/docs/html/why-bugzilla.html new file mode 100644 index 000000000..f3da40066 --- /dev/null +++ b/docs/html/why-bugzilla.html @@ -0,0 +1,227 @@ +<HTML +><HEAD +><TITLE +>Why use Bugzilla?</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Introduction" +HREF="introduction.html"><LINK +REL="PREVIOUS" +TITLE="Why use a bug-tracking system?" +HREF="why-tracking.html"><LINK +REL="NEXT" +TITLE="Using Bugzilla" +HREF="using.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="why-tracking.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 2. Introduction</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="using.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="why-bugzilla" +></A +>2.3. Why use Bugzilla?</H1 +><P +>Bugzilla boasts many advanced features. These include: + <P +></P +><UL +><LI +><P +>Powerful searching</P +></LI +><LI +><P +>User-configurable email notifications of bug changes</P +></LI +><LI +><P +>Full change history</P +></LI +><LI +><P +>Inter-bug dependency tracking and graphing</P +></LI +><LI +><P +>Excellent attachment management</P +></LI +><LI +><P +>Integrated, product-based, granular security schema</P +></LI +><LI +><P +>Fully security-audited, and runs under Perl's taint mode</P +></LI +><LI +><P +>A robust, stable RDBMS back-end</P +></LI +><LI +><P +>Web, XML, email and console interfaces</P +></LI +><LI +><P +>Completely customisable and/or localisable web user + interface</P +></LI +><LI +><P +>Extensive configurability</P +></LI +><LI +><P +>Smooth upgrade pathway between versions</P +></LI +></UL +> + </P +><P +>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 + <A +HREF="http://www.cvshome.org" +TARGET="_top" +>CVS</A +>, + <A +HREF="http://www.mozilla.org/bonsai.html" +TARGET="_top" +>Bonsai</A +>, or + <A +HREF="http://www.perforce.com" +TARGET="_top" +>Perforce SCM</A +>, Bugzilla + provides a powerful, easy-to-use solution to configuration management and + replication problems.</P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="why-tracking.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="using.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Why use a bug-tracking system?</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Using Bugzilla</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/why-tracking.html b/docs/html/why-tracking.html new file mode 100644 index 000000000..bb22e0020 --- /dev/null +++ b/docs/html/why-tracking.html @@ -0,0 +1,164 @@ +<HTML +><HEAD +><TITLE +>Why use a bug-tracking system?</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" +HREF="index.html"><LINK +REL="UP" +TITLE="Introduction" +HREF="introduction.html"><LINK +REL="PREVIOUS" +TITLE="What is Bugzilla?" +HREF="what-is-bugzilla.html"><LINK +REL="NEXT" +TITLE="Why use Bugzilla?" +HREF="why-bugzilla.html"></HEAD +><BODY +CLASS="section" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="NAVHEADER" +><TABLE +SUMMARY="Header navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TH +COLSPAN="3" +ALIGN="center" +>The Bugzilla Guide - 2.17.5 + Development Release</TH +></TR +><TR +><TD +WIDTH="10%" +ALIGN="left" +VALIGN="bottom" +><A +HREF="what-is-bugzilla.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 2. Introduction</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="why-bugzilla.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="section" +><H1 +CLASS="section" +><A +NAME="why-tracking" +></A +>2.2. Why use a bug-tracking system?</H1 +><P +>For many years, defect-tracking software was principally + the domain of large software development houses. Most smaller shops + simply relied on + shared lists and email to monitor the status of defects. This procedure + was error-prone and tended to cause those bugs judged least significant by + developers to be dropped or ignored.</P +><P +>Integrated + defect-tracking systems reduce downtime, increase productivity, and raise + customer satisfaction with their systems. Along with full disclosure, an + open bug-tracker allows you to keep in touch with your 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 method for accounting for unusual system or software + issues.</P +></DIV +><DIV +CLASS="NAVFOOTER" +><HR +ALIGN="LEFT" +WIDTH="100%"><TABLE +SUMMARY="Footer navigation table" +WIDTH="100%" +BORDER="0" +CELLPADDING="0" +CELLSPACING="0" +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +><A +HREF="what-is-bugzilla.html" +ACCESSKEY="P" +>Prev</A +></TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="index.html" +ACCESSKEY="H" +>Home</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +><A +HREF="why-bugzilla.html" +ACCESSKEY="N" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>What is Bugzilla?</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="introduction.html" +ACCESSKEY="U" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Why use Bugzilla?</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/why.html b/docs/html/why.html index d1e3b813e..6c46ddf44 100644 --- a/docs/html/why.html +++ b/docs/html/why.html @@ -1,19 +1,21 @@ <HTML ><HEAD ><TITLE ->Why Should We Use Bugzilla?</TITLE +>Why use Bugzilla?</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Introduction" HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="What is Bugzilla?" -HREF="whatis.html"><LINK +TITLE="Why use a bug-tracking system?" +HREF="why.html"><LINK REL="NEXT" TITLE="Using Bugzilla" HREF="using.html"></HEAD @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -44,7 +47,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="whatis.html" +HREF="why.html" ACCESSKEY="P" >Prev</A ></TD @@ -74,32 +77,64 @@ CLASS="section" ><A NAME="why" ></A ->2.2. Why Should We Use Bugzilla?</H1 +>2.3. Why use Bugzilla?</H1 ><P ->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.</P +>Bugzilla boasts many advanced features. These include: + <P +></P +><UL +><LI ><P ->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.</P +>Powerful searching</P +></LI +><LI ><P ->But why should - <EM ->you</EM +>User-configurable email notifications of bug changes</P +></LI +><LI +><P +>Full change history</P +></LI +><LI +><P +>Inter-bug dependency tracking and graphing</P +></LI +><LI +><P +>Excellent attachment management</P +></LI +><LI +><P +>Integrated, product-based, granular security schema</P +></LI +><LI +><P +>Fully security-audited, and runs under Perl's taint mode</P +></LI +><LI +><P +>A robust, stable RDBMS back-end</P +></LI +><LI +><P +>Web, XML, email and console interfaces</P +></LI +><LI +><P +>Completely customisable and/or localisable web user + interface</P +></LI +><LI +><P +>Extensive configurability</P +></LI +><LI +><P +>Smooth upgrade pathway between versions</P +></LI +></UL > - - use Bugzilla?</P + </P ><P >Bugzilla is very adaptable to various situations. Known uses currently include IT support queues, Systems Administration deployment @@ -124,22 +159,6 @@ TARGET="_top" >, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems.</P -><P ->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 - <EM ->something</EM -> - 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.</P -><P ->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.</P ></DIV ><DIV CLASS="NAVFOOTER" @@ -157,7 +176,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="whatis.html" +HREF="why.html" ACCESSKEY="P" >Prev</A ></TD @@ -185,7 +204,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->What is Bugzilla?</TD +>Why use a bug-tracking system?</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt index 39b249eba..d7cf3974c 100644 --- a/docs/txt/Bugzilla-Guide.txt +++ b/docs/txt/Bugzilla-Guide.txt @@ -1,25 +1,14 @@ -The Bugzilla Guide - 2.17.5 Development Release - -Matthew P. Barnson -Jacob Steenhagen +The Bugzilla Guide - 2.17.5 Development Release The Bugzilla Team - 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 the Bugzilla Documentation component. + 2004-01-15 - This is a development version of this guide. Information in it is - subject to change before the 2.18 release of this guide (which will - correspond with the 2.18 release of Bugzilla). + This is the documentation for Bugzilla, a bug-tracking system from + mozilla.org. Bugzilla is an enterprise-class piece of software that + tracks millions of bugs and issues for hundreds of organizations + around the world. The most current version of this document can always be found on the Bugzilla Documentation Page. @@ -37,56 +26,56 @@ The Bugzilla Team 2. Introduction 2.1. What is Bugzilla? - 2.2. Why Should We Use Bugzilla? + 2.2. Why use a bug-tracking system? + 2.3. Why use Bugzilla? 3. Using Bugzilla - 3.1. How do I use Bugzilla? - 3.2. Hints and Tips - 3.3. User Preferences + 3.1. Create a Bugzilla Account + 3.2. Anatomy of a Bug + 3.3. Searching for Bugs + 3.4. Bug Lists + 3.5. Filing Bugs + 3.6. Patch Viewer + 3.7. Hints and Tips + 3.8. User Preferences + 3.9. Reports 4. Installation 4.1. Step-by-step Install - 4.2. Optional Additional Configuration - 4.3. OS Specific Installation Notes - 4.4. HTTP Server Configuration - 4.5. Troubleshooting + 4.2. HTTP Server Configuration + 4.3. Optional Additional Configuration + 4.4. OS Specific Installation Notes + 4.5. Bugzilla Security + 4.6. Troubleshooting 5. Administering Bugzilla 5.1. Bugzilla Configuration 5.2. User Administration - 5.3. Product, Component, Milestone, and Version Administration - 5.4. Voting - 5.5. Groups and Group Security - 5.6. Bugzilla Security - 5.7. Template Customization - 5.8. Change Permission Customization + 5.3. Products + 5.4. Components + 5.5. Versions + 5.6. Milestones + 5.7. Voting + 5.8. Groups and Group Security 5.9. Upgrading to New Releases - 5.10. Integrating Bugzilla with Third-Party Tools - - A. The Bugzilla FAQ - B. The Bugzilla Database - B.1. Modifying Your Running System - B.2. MySQL Bugzilla Database Introduction + 6. Customising Bugzilla - C. Useful Patches and Utilities for Bugzilla + 6.1. Template Customization + 6.2. Customizing Who Can Change What + 6.3. Modifying Your Running System + 6.4. MySQL Bugzilla Database Introduction + 6.5. Integrating Bugzilla with Third-Party Tools - C.1. Apache mod_rewrite magic - C.2. Command-line Bugzilla Queries - - D. Bugzilla Variants and Competitors + A. The Bugzilla FAQ + B. Contrib - D.1. Red Hat Bugzilla - D.2. Loki Bugzilla (Fenris) - D.3. Issuezilla - D.4. Scarab - D.5. Perforce SCM - D.6. SourceForge + B.1. Command-line Search Interface - E. GNU Free Documentation License + C. GNU Free Documentation License 0. PREAMBLE 1. APPLICABILITY AND DEFINITIONS @@ -110,7 +99,6 @@ The Bugzilla Team List of Examples 4-1. Installing perl modules with CPAN - 4-2. .htaccess files for Apache 5-1. Upgrading using CVS 5-2. Upgrading using the tarball 5-3. Upgrading using patches @@ -122,72 +110,52 @@ Chapter 1. About This Guide - 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. + 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 C. - --Copyright (c) 2000-2003 Matthew P. Barnson and The Bugzilla Team + --Copyright (c) 2000-2004 The Bugzilla Team If you have any questions regarding this document, its copyright, or - publishing this document in non-electronic form, please contact The + publishing this document in non-electronic form, please contact the Bugzilla Team. _________________________________________________________________ 1.2. Disclaimer - No liability for the contents of this document can be accepted. Use - the concepts, examples, and other content at your own risk. This - document may contain errors and inaccuracies that may damage your - system, cause your partner to leave you, your boss to fire you, your - cats to pee on your furniture and clothing, and global thermonuclear - war. Proceed with caution. - - All copyrights are held by their respective owners, unless - specifically noted otherwise. Use of a term in this document should - not be regarded as affecting the validity of any trademark or service - mark. + No liability for the contents of this document can be accepted. Follow + the instructions herein 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. 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! + wholeheartedly endorse the use of GNU/Linux; it is an extremely + versatile, stable, and robust operating system that offers an ideal + operating environment for Bugzilla. 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. + that all exploitable bugs or options have been fixed, security holes + surely exist. Great care should be taken both in the installation and + usage of this software. The Bugzilla development team members assume + no liability for your use of this software. You have the source code, + and are responsible for auditing it yourself to ensure your security + needs are met. _________________________________________________________________ 1.3. New Versions This is the 2.17.5 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. This version of the guide, like - its associated Bugzilla version is a development version. Information - is subject to change between now and when 2.18 is released. 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. + its associated Bugzilla version, is a development version. The newest version of this guide can always be found at - http://www.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. + http://www.bugzilla.org; however, you should read the version which + came with the Bugzilla release you are using. The latest version of this document can always be checked out via CVS. Please follow the Mozilla CVS instructions and check out the @@ -204,41 +172,14 @@ Chapter 1. About This Guide efforts, numerous e-mail and IRC support sessions, and overall excellent contribution to the Bugzilla community: - Matthew P. Barnson <mbarnson@sisna.com> - for the Herculaean task of pulling together the Bugzilla Guide - and shepherding it to 2.14. - - Terry Weissman <terry@mozilla.org> - for initially writing Bugzilla and creating the README upon - which the UNIX installation documentation is largely based. - - Tara Hernandez <tara@tequilarists.org> - for keeping Bugzilla development going strong after Terry left - mozilla.org and for running landfill. - - Dave Lawrence <dkl@redhat.com> - for providing insight into the key differences between Red - Hat's customized Bugzilla, and being largely responsible for - Section D.1. - - Dawn Endico <endico@mozilla.org> - for being a hacker extraordinaire and putting up with Matthew's - incessant questions and arguments on irc.mozilla.org in - #mozwebtools - - Jacob Steenhagen <jake@bugzilla.org> - for taking over documentation during the 2.17 development - period. + Matthew P. Barnson, Kevin Brannen, Dawn Endico, Ben FrantzDale, Eric + Hanson, Tara Hernandez, Dave Lawrence, Zach Lipton, Gervase Markham, + Andrew Pearson, Joe Robins, Spencer Smith, Jacob Steenhagen, Ron + Teitelbaum, Terry Weissman, Martin Wulffeld. 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, - Martin Wulffeld, Ron Teitelbaum, Spencer Smith, Zach Liption . + netscape.public.mozilla.webtools newsgroup. Without your discussions, + insight, suggestions, and patches, this could never have happened. _________________________________________________________________ 1.5. Document Conventions @@ -248,42 +189,40 @@ Chapter 1. About This Guide Descriptions Appearance Warnings - Caution - Don't run with scissors! + Don't run with scissors! Hint - Tip - Would you like a breath mint? + Would you like a breath mint? Notes - Note - Dear John... + Dear John... Information requiring special attention - Warning - Read this or the cat gets it. - File Names filename - Directory Names directory + Read this or the cat gets it. + File and directory names filename Commands to be typed command - Applications Names application + 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 + Environment variables VARIABLE Term found in the glossary Bugzilla - Code Example - <para> - Beginning and end of paragraph - </para> + Code example +<para> +Beginning and end of paragraph +</para> + + 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 the Bugzilla Documentation component. _________________________________________________________________ Chapter 2. Introduction @@ -292,16 +231,31 @@ Chapter 2. Introduction 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. + outstanding problems with their products. + + Do we need more here? + _________________________________________________________________ + +2.2. Why use a bug-tracking system? + + For many years, defect-tracking software was principally the domain of + large software development houses. Most smaller shops simply relied on + shared lists and email to monitor the status of defects. This + procedure was error-prone and tended to cause those bugs judged least + significant by developers to be dropped or ignored. + + Integrated defect-tracking systems reduce downtime, increase + productivity, and raise customer satisfaction with their systems. + Along with full disclosure, an open bug-tracker allows you to keep in + touch with your 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 method for accounting for unusual + system or software issues. + _________________________________________________________________ + +2.3. Why use Bugzilla? Bugzilla boasts many advanced features. These include: @@ -317,29 +271,6 @@ Chapter 2. Introduction * Completely customisable and/or localisable web user interface * Extensive configurability * Smooth upgrade pathway between versions - _________________________________________________________________ - -2.2. Why Should We Use Bugzilla? - - For many years, defect-tracking software has remained principally the - domain of large software development houses. Even then, most shops - never bothered with bug-tracking software, and instead simply relied - on shared lists and email to monitor the status of defects. This - procedure is error-prone and tends to cause those bugs judged least - significant by developers to be dropped or ignored. - - These days, many companies are finding that integrated defect-tracking - systems reduce downtime, increase productivity, and raise customer - satisfaction with their systems. Along with full disclosure, an open - bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout - the data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support - accountability, telephone support knowledge bases, and a common, - well-understood system for accounting for unusual system or software - issues. - - But why should you use Bugzilla? Bugzilla is very adaptable to various situations. Known uses currently include IT support queues, Systems Administration deployment @@ -349,34 +280,18 @@ Chapter 2. Introduction Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems. - - Bugzilla can dramatically increase the productivity and accountability - of individual employees by providing a documented workflow and - positive feedback for good performance. How many times do you wake up - in the morning, remembering that you were supposed to do something - today, but you just can't quite remember? Put it in Bugzilla, and you - have a record of it from which you can extrapolate milestones, predict - product versions for integration, and follow the discussion trail that - led to critical decisions. - - Ultimately, Bugzilla puts the power in your hands to improve your - value to your employer or business while providing a usable framework - for your natural attention to detail and knowledge store to flourish. _________________________________________________________________ Chapter 3. Using Bugzilla -3.1. How do I use Bugzilla? - This section contains information for end-users of Bugzilla. There is a Bugzilla test installation, called Landfill, which you are welcome to play with (if it's up.) However, it does not necessarily have all - Bugzilla features enabled, and often runs cutting-edge versions of - Bugzilla for testing, so some things may work slightly differently - than mentioned here. + Bugzilla features enabled, and runs an up-to-the-minute version, so + some things may not quite work as this document describes. _________________________________________________________________ -3.1.1. Create a Bugzilla Account +3.1. Create a Bugzilla Account If you want to use Bugzilla, first you need to create an account. Consult with the administrator responsible for your installation of @@ -388,19 +303,19 @@ Chapter 3. Using Bugzilla address and, optionally, your name in the spaces provided, then click "Create Account" . 2. 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. - 3. 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". + provided, which contains your login name (generally the same as + the email address), and a password. This password is randomly + generated, but can be changed to something more memorable. + 3. Click the "Log In" link in the footer 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. + You are now logged in. Bugzilla uses cookies to remember you are + logged in so, unless you have cookies disabled or your IP address + changes, you should not have to log in again. _________________________________________________________________ -3.1.2. Anatomy of a Bug +3.2. Anatomy of a Bug The core of Bugzilla is the screen which displays a particular bug. It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill @@ -415,22 +330,22 @@ Chapter 3. Using Bugzilla several Components: Administration: Administration of a Bugzilla installation. - Bugzilla-General: Anything that doesn't fit in the other components, - or spans multiple components. + 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. + 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. + 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. + 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. 2. 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 @@ -476,7 +391,7 @@ Chapter 3. Using Bugzilla discussion here, if you have something worthwhile to say. _________________________________________________________________ -3.1.3. Searching for Bugs +3.3. Searching for Bugs The Bugzilla Search page is is the interface where you can find any bug report, comment, or patch currently in the Bugzilla system. You @@ -486,21 +401,19 @@ Chapter 3. Using Bugzilla The Search page has controls for selecting different possible values for all of the fields in a bug, as described above. For some fields, multiple values can be selected. In those cases, Bugzilla returns bugs - where the content of the field matches one of the selected values. If - none is selected, then the field can take any value. + where the content of the field matches any one of the selected values. + If none is selected, then the field can take any value. - 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. + Once you've run a search, you can save it as a Saved Search, which + appears in the page footer. - Highly advanced querying is done using Boolean Charts. + Highly advanced querying is done using Boolean Charts. See the Boolean + Charts help link on the Search page for more information. _________________________________________________________________ -3.1.4. Bug Lists +3.4. Bug Lists - If you run a search, a list of matching bugs will be returned. The - default search is to return all open bugs on the system - don't try - running this search on a Bugzilla installation with a lot of bugs! + If you run a search, a list of matching bugs will be returned. The format of the list is configurable. For example, it can be sorted by clicking the column headings. Other useful features can be accessed @@ -520,7 +433,7 @@ Chapter 3. Using Bugzilla accurate results. _________________________________________________________________ -3.1.5. Filing Bugs +3.5. Filing Bugs Years of bug writing experience has been distilled for your reading pleasure into the Bug Writing Guidelines. While some of the advice is @@ -541,7 +454,7 @@ Chapter 3. Using Bugzilla 4. Select "Commit" and send in your bug report. _________________________________________________________________ -3.1.6. Patch Viewer +3.6. Patch Viewer Viewing and reviewing patches in Bugzilla is often difficult due to lack of context, improper format and the inherent readability issues @@ -563,7 +476,7 @@ Chapter 3. Using Bugzilla format it came from _________________________________________________________________ -3.1.6.1. Viewing Patches in Patch Viewer +3.6.1. Viewing Patches in Patch Viewer The main way to view a patch in patch viewer is to click on the "Diff" link next to a patch in the Attachments list on a bug. You may also do @@ -571,7 +484,7 @@ Chapter 3. Using Bugzilla button in the Edit Attachment screen. _________________________________________________________________ -3.1.6.2. Seeing the Difference Between Two Patches +3.6.2. Seeing the Difference Between Two Patches To see the difference between two patches, you must first view the newer patch in Patch Viewer. Then select the older patch from the @@ -580,7 +493,7 @@ Chapter 3. Using Bugzilla new or changed in the newer patch. _________________________________________________________________ -3.1.6.3. Getting More Context in a Patch +3.6.3. Getting More Context in a Patch To get more context in a patch, you put a number in the textbox at the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. This @@ -590,7 +503,7 @@ Chapter 3. Using Bugzilla against files that were diffed using "cvs diff". _________________________________________________________________ -3.1.6.4. Collapsing and Expanding Sections of a Patch +3.6.4. Collapsing and Expanding Sections of a Patch To view only a certain set of files in a patch (for example, if a patch is absolutely huge and you want to only review part of it at a @@ -600,7 +513,7 @@ Chapter 3. Using Bugzilla the top of the page. _________________________________________________________________ -3.1.6.5. Linking to a Section of a Patch +3.6.5. Linking to a Section of a Patch To link to a section of a patch (for example, if you want to be able to give someone a URL to show them which part you are talking about) @@ -609,7 +522,7 @@ Chapter 3. Using Bugzilla Location in Mozilla works as well.) _________________________________________________________________ -3.1.6.6. Going to Bonsai and LXR +3.6.6. Going to Bonsai and LXR To go to Bonsai to get blame for the lines you are interested in, you can click the "Lines XX-YY" link on the section header you are @@ -621,29 +534,30 @@ Chapter 3. Using Bugzilla numbers are likely to rot). _________________________________________________________________ -3.1.6.7. Creating a Unified Diff +3.6.7. Creating a Unified Diff If the patch is not in a format that you like, you can turn it into a unified diff format by clicking the "Raw Unified" link at the top of the page. _________________________________________________________________ -3.2. Hints and Tips +3.7. Hints and Tips This section distills some Bugzilla tips and best practices that have been developed. _________________________________________________________________ -3.2.1. Autolinkification +3.7.1. Autolinkification - Bugzilla comments are plain text - so posting HTML will result in - literal HTML tags rather than being interpreted by a browser. However, + Bugzilla comments are plain text - so typing <U> will produce + less-than, U, greater-than rather than underlined text. 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: + text in comments. For example, the text "http://www.bugzilla.org" will + be turned into a link: http://www.bugzilla.org. Other strings which + get linkified in the obvious manner are: bug 12345 + comment 7 bug 23456, comment 53 attachment 4321 mailto:george@example.com @@ -656,7 +570,7 @@ Chapter 3. Using Bugzilla convenience of others. _________________________________________________________________ -3.2.2. Quicksearch +3.7.2. Quicksearch Quicksearch is a single-text-box query tool which uses metacharacters to indicate what is to be searched. For example, typing "foo|bar" into @@ -668,7 +582,7 @@ Chapter 3. Using Bugzilla Help link which details how to use it. _________________________________________________________________ -3.2.3. Comments +3.7.3. Comments If you are changing the fields on a bug, only comment if either you have something pertinent to say, or Bugzilla requires it. Otherwise, @@ -680,11 +594,11 @@ Chapter 3. Using Bugzilla mail they would otherwise have avoided. Don't use sigs in comments. Signing your name ("Bill") is acceptable, - particularly if you do it out of habit, but full mail/news-style four - line ASCII art creations are not. + if you do it out of habit, but full mail/news-style four line ASCII + art creations are not. _________________________________________________________________ -3.2.4. Attachments +3.7.4. Attachments Use attachments, rather than comments, for large chunks of ASCII data, such as trace, debugging output files, or log files. That way, it @@ -700,7 +614,7 @@ Chapter 3. Using Bugzilla way, the test case works immediately out of the bug. _________________________________________________________________ -3.2.5. Filing Bugs +3.7.5. Filing Bugs Try to make sure that everything said in the summary is also said in the first comment. Summaries are often updated and this will ensure @@ -715,14 +629,14 @@ Chapter 3. Using Bugzilla Feel free to CC the person who duped it if they are not already CCed. _________________________________________________________________ -3.3. User Preferences +3.8. User Preferences Once you have logged in, you can customise various aspects of Bugzilla via the "Edit prefs" link in the page footer. The preferences are - split into four tabs: + split into three tabs: _________________________________________________________________ -3.3.1. Account Settings +3.8.1. Account Settings On this tab, you can change your basic account information, including your password, email address and real name. For security reasons, in @@ -733,13 +647,17 @@ Chapter 3. Using Bugzilla change. This helps to prevent account hijacking. _________________________________________________________________ -3.3.2. Email Settings +3.8.2. Email Settings On this tab you can reduce or increase the amount of email sent you from Bugzilla, opting in our out depending on your relationship to the - bug and the change that was made to it. (Note that you can also do - client-side filtering using the X-Bugzilla-Reason header which - Bugzilla adds to all bugmail.) + bug and the change that was made to it. + + You can also do further filtering on the client side by using the + X-Bugzilla-Reason mail header which Bugzilla adds to all bugmail. This + tells you what relationship you have to the bug in question, and can + be any of Owner, Reporter, QAcontact, CClist, Voter and + WatchingComponent. 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 @@ -749,19 +667,11 @@ Chapter 3. Using Bugzilla Note - The ability to watch other users may not be available in all Bugzilla - installations. If you can't see it, ask your administrator. - _________________________________________________________________ - -3.3.3. Page Footer - - On the Search page, you can store queries in Bugzilla, so if you - regularly run a particular query it is just a drop-down menu away. - Once you have a stored query, you can come here to request that it - also be displayed in your page footer. + The ability to watch other users may not be available in all Bugzilla + installations. If you can't see it, ask your administrator. _________________________________________________________________ -3.3.4. Permissions +3.8.3. Permissions This is a purely informative page which outlines your current permissions on this installation of Bugzilla - what product groups you @@ -769,6 +679,11 @@ Chapter 3. Using Bugzilla administration functions. _________________________________________________________________ +3.9. Reports + + To be written + _________________________________________________________________ + Chapter 4. Installation 4.1. Step-by-step Install @@ -777,23 +692,23 @@ Chapter 4. Installation operating systems including almost all Unix clones and Microsoft Windows. Many operating systems have utilities that make installation easier or quirks that make it harder. We have tried to collect that - information in Section 4.3, so be sure to check out that section + information in Section 4.4, so be sure to check out that section before you start your installation. Note - Windows is one of those operating systems that has many quirks and is - not yet officially supported by the Bugzilla team. If you wish to - install Bugzilla on Windows, be sure to see Section 4.3.1. + Windows is one of those operating systems that has many quirks and is + not yet officially supported by the Bugzilla team. If you wish to + install Bugzilla on Windows, be sure to see Section 4.4.1. - Warning + Warning - While installing Bugzilla, it is a good idea to ensure that there is - some kind of firewall between you and the rest of the Internet as 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. + While installing Bugzilla, it is a good idea to ensure that there is + some kind of firewall between you and the rest of the Internet as 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. This guide assumes that you already have your operating system installed, network configured, and have administrative access to the @@ -802,29 +717,42 @@ Chapter 4. Installation have to either make sure all the required software is installed or get somebody with administrative access to install it for you. + You are strongly recommended to make a backup of your system before + installing Bugzilla and at regular intervals thereafter. + The listing below is a basic step-by-step list. More information can be found in the sections below. Minimum versions will be included in parenthesis where appropriate. - 1. Install MySQL (3.23.41) - 2. Install Perl (5.6) - 3. Install Perl Modules - 4. Install a Webserver - 5. Put Bugzilla in the Webspace + 1. Install Perl (5.6) + 2. Install MySQL (3.23.41) + 3. Install a Webserver + 4. Put Bugzilla in the Webspace + 5. Install Perl Modules 6. Setup the MySQL Database _________________________________________________________________ -4.1.1. MySQL +4.1.1. Perl + + Any machine that doesn't have Perl on it is a sad machine indeed. Perl + can be got in source form from http://www.perl.com. There are also + binary versions available for many platforms, most of which are linked + to from perl.com. Although Bugzilla runs with perl 5.6, 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.8. + _________________________________________________________________ + +4.1.2. MySQL Visit the MySQL homepage at http://www.mysql.com to grab and install the latest stable release of the server. Note - 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. + 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 a packaging/installation system (such as .rpm, .dep, .exe, or .msi) you will need to configure @@ -838,26 +766,88 @@ Chapter 4. Installation set this value to be slightly larger than that parameter. Figure 4-1. Set Max Packet Size in MySQL - [mysqld] - # Allow packets up to 1M - set-variable = max_allowed_packet=1M +[mysqld] +# Allow packets up to 1M +set-variable = max_allowed_packet=1M If you are running Bugzilla and MySQL on the same machine, you may also wish to utilize the skip-networking option as mentioned in - Section 5.6.2 for the added security. + Section 4.5.2 for the added security. _________________________________________________________________ -4.1.2. Perl +4.1.2.1. Configuring MySQL - Any machine that doesn't have Perl on it is a sad machine indeed. Perl - can be got in source form from http://www.perl.com. There are also - binary versions available for many platforms, most of which are linked - to from perl.com. Although Bugzilla runs with perl 5.6, 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.8. + This first thing you'll want to do is make sure you've given the + "root" user a password as suggested in Section 4.5.2. For clarity, + these instructions will assume that your MySQL user for Bugzilla will + be "bugs_user", the database will be called "bugs_db" and the password + for the "bugs_user" user is "bugs_password". You should, of course, + substitute the values you intend to use for your site. + + Note + + Most people use "bugs" for both the user and database name. + + Next, we use an SQL GRANT command to create a "bugs_user" user, and + grant sufficient permissions for checksetup.pl, which we'll use later, + to work its magic. This also restricts the "bugs_user" user to + operations within a database called "bugs_db", 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. + mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, + DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost + IDENTIFIED BY 'bugs_password'; + mysql> FLUSH PRIVILEGES; + + Note + + If you are using MySQL 4, the bugs user also needs to be granted the + LOCK TABLES and CREATE TEMPORARY TABLES permissions. + _________________________________________________________________ + +4.1.3. HTTP Server + + You have freedom of choice here, pretty much any web server that is + capable of running CGI scripts will work. Section 4.2 has more + information about configuring web servers to work with Bugzilla. + + Note + + 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 by filing a bug in Bugzilla + Documentation. _________________________________________________________________ -4.1.3. Perl Modules +4.1.4. Bugzilla + + You should untar the Bugzilla files into a directory that you're + willing to make writable by the default web server user (probably + "nobody"). You may decide to put the files in the main web space for + your web server or perhaps in /usr/local with a symbolic link in the + web space that points to the Bugzilla directory. + + Tip + + If you symlink the bugzilla directory into your Apache's HTML + hierarchy, 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. + + Caution + + The default Bugzilla distribution is not designed to be placed in a + cgi-bin directory (this includes any directory which is configured + using the ScriptAlias directive of Apache). + _________________________________________________________________ + +4.1.5. Perl Modules Perl modules can be found using CPAN on Unix based systems or PPM on Win32. The root servers have a real tendency to bog down, so please @@ -865,39 +855,39 @@ Chapter 4. Installation Good instuctions can be found for using each of these services on their respective websites. The basics can be found in Example 4-1 for - CPAN and Section 4.3.1.2 for PPM. + CPAN and Section 4.4.1.2 for PPM. Example 4-1. Installing perl modules with CPAN The easy way: - bash# perl -MCPAN -e 'install "<modulename>"' +bash# perl -MCPAN -e 'install "<modulename>"' Or the hard way: - bash# tar xzvf <module>.tar.gz (1) - bash# cd <module> (2) - bash# perl Makefile.PL - bash# make - bash# make test - bash# make install - - (1) +bash# tar xzvf <module>.tar.gz (1) +bash# cd <module> (2) +bash# perl Makefile.PL +bash# make +bash# make test +bash# make install + + (1) This assumes that you've already downloaded the <module>.tar.gz to the current working directory. - (2) - The process of untaring the module as defined in (1) will + (2) + The process of untarring the module as defined in (1) will create the <module> directory. Tip - 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. + 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. Perl Modules (minimum version): @@ -924,7 +914,7 @@ Chapter 4. Installation 7. PatchReader (0.9.1) for pretty HTML view of patches _________________________________________________________________ -4.1.3.1. Bundle::Bugzilla +4.1.5.1. Bundle::Bugzilla If you are running at least perl 5.6.1, you can save yourself a lot of time by using Bundle::Bugzilla. This bundle contains every module @@ -935,25 +925,25 @@ Chapter 4. Installation Assuming your perl was installed with CPAN (most unix installations are), using Bundle::Bugzilla is really easy. Simply follow along with the commands below. - bash# perl -MCPAN -eshell (1) - cpan shell -- CPAN exploration and modules installation (v1.63) - ReadLine support enabled +bash# perl -MCPAN -eshell (1) +cpan shell -- CPAN exploration and modules installation (v1.63) +ReadLine support enabled - cpan> +cpan> - (1) + (1) At this point, unless you've used CPAN on this machine before, you'll have to go through a series of configuration steps. _________________________________________________________________ -4.1.3.2. AppConfig (1.52) +4.1.5.2. AppConfig (1.52) Dependency for Template Toolkit. We probably don't need to specifically check for it anymore. _________________________________________________________________ -4.1.3.3. CGI (2.88) +4.1.5.3. CGI (2.88) The CGI module parses form elements and cookies and does many other usefule things. It come as a part of recent perl distributions, but @@ -965,7 +955,7 @@ Chapter 4. Installation Documentation: http://www.perldoc.com/perl5.8.0/lib/CGI.html _________________________________________________________________ -4.1.3.4. Data::Dumper (any) +4.1.5.4. Data::Dumper (any) The Data::Dumper module provides data structure persistence for Perl (similar to Java's serialization). It comes with later sub-releases of @@ -979,7 +969,7 @@ Chapter 4. Installation r.html _________________________________________________________________ -4.1.3.5. TimeDate modules (2.21) +4.1.5.5. TimeDate modules (2.21) Many of the more common date/time/calendar related Perl modules have been grouped into a bundle similar to the MySQL modules bundle. This @@ -994,7 +984,7 @@ Chapter 4. Installation ormat.pm _________________________________________________________________ -4.1.3.6. DBI (1.32) +4.1.5.6. DBI (1.32) The DBI module is a generic Perl module used the MySQL-related modules. As long as your Perl installation was done correctly the DBI @@ -1007,7 +997,7 @@ Chapter 4. Installation Documentation: http://dbi.perl.org/doc/ _________________________________________________________________ -4.1.3.7. MySQL-related modules +4.1.5.7. MySQL-related modules The Perl/MySQL interface requires a few mutually-dependent Perl modules. These modules are grouped together into the the @@ -1032,7 +1022,7 @@ Chapter 4. Installation ysql.pod _________________________________________________________________ -4.1.3.8. File::Spec (0.82) +4.1.5.8. File::Spec (0.82) File::Spec is a perl module that allows file operations, such as generating full path names, to work cross platform. @@ -1044,7 +1034,7 @@ Chapter 4. Installation html _________________________________________________________________ -4.1.3.9. File::Temp (any) +4.1.5.9. File::Temp (any) File::Temp is used to generate a temporary filename that is guaranteed to be unique. It comes as a standard part of perl @@ -1056,7 +1046,7 @@ Chapter 4. Installation html _________________________________________________________________ -4.1.3.10. Template Toolkit (2.08) +4.1.5.10. Template Toolkit (2.08) When you install Template Toolkit, you'll get asked various questions about features to enable. The defaults are fine, except that it is @@ -1070,7 +1060,7 @@ Chapter 4. Installation Documentation: http://www.template-toolkit.org/docs.html _________________________________________________________________ -4.1.3.11. Text::Wrap (2001.0131) +4.1.5.11. Text::Wrap (2001.0131) Text::Wrap is designed to proved intelligent text wrapping. @@ -1080,7 +1070,7 @@ Chapter 4. Installation html _________________________________________________________________ -4.1.3.12. GD (1.20) [optional] +4.1.5.12. GD (1.20) [optional] The GD library was written by Thomas Boutell a long while ago to programmatically generate images in C. Since then it's become the @@ -1092,16 +1082,16 @@ Chapter 4. Installation Note - 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 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. Tip - The version of the GD perl module you need is very closely tied to the - libgd version installed on your system. If you have a version 1.x of - libgd the 2.x versions of the GD perl module won't work for you. + The version of the GD perl module you need is very closely tied to the + libgd version installed on your system. If you have a version 1.x of + libgd the 2.x versions of the GD perl module won't work for you. CPAN Download Page: http://search.cpan.org/dist/GD/ PPM Download Link: http://ppm.activestate.com/PPMPackages/zips @@ -1109,7 +1099,7 @@ Chapter 4. Installation Documentation: http://stein.cshl.org/WWW/software/GD/ _________________________________________________________________ -4.1.3.13. Chart::Base (0.99c) [optional] +4.1.5.13. Chart::Base (0.99c) [optional] The Chart module provides Bugzilla with on-the-fly charting abilities. It can be installed in the usual fashion after it has been fetched @@ -1121,7 +1111,7 @@ Chapter 4. Installation /6xx-builds-only/Chart.zip _________________________________________________________________ -4.1.3.14. XML::Parser (any) [Optional] +4.1.5.14. XML::Parser (any) [Optional] XML::Parser is used by the importxml.pl script. You only need it if you are going to be importing bugs (such as for bug moving). @@ -1133,7 +1123,7 @@ Chapter 4. Installation .html _________________________________________________________________ -4.1.3.15. GD::Graph (any) [Optional] +4.1.5.15. GD::Graph (any) [Optional] In addition to GD listed above, the reporting interface of Bugzilla needs to have the GD::Graph module installed. @@ -1144,7 +1134,7 @@ Chapter 4. Installation Documentation: http://search.cpan.org/dist/GDGraph/Graph.pm _________________________________________________________________ -4.1.3.16. GD::Text::Align (any) [Optional] +4.1.5.16. GD::Text::Align (any) [Optional] GD::Text::Align, as the name implies, is used to draw aligned strings of text. It is needed by the reporting interface. @@ -1156,7 +1146,7 @@ Chapter 4. Installation gn.pm _________________________________________________________________ -4.1.3.17. MIME::Parser (any) [Optional] +4.1.5.17. MIME::Parser (any) [Optional] MIME::Parser is only needed if you want to use the e-mail interface located in the contrib directory. @@ -1168,7 +1158,7 @@ Chapter 4. Installation /Parser.pm _________________________________________________________________ -4.1.3.18. PatchReader (0.9.1) [Optional] +4.1.5.18. PatchReader (0.9.1) [Optional] PatchReader is only needed if you want to use Patch Viewer, a Bugzilla feature to format patches in a pretty HTML fashion. There are a number @@ -1186,93 +1176,15 @@ Chapter 4. Installation html _________________________________________________________________ -4.1.4. HTTP Server - - You have freedom of choice here, pretty much any web server that is - capable of running CGI scripts will work. Section 4.4 has more - information about configuring web servers to work with Bugzilla. - - Note - - 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 by filing a bug in Bugzilla - Documentation. - _________________________________________________________________ - -4.1.5. Bugzilla - - You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - "nobody"). You may decide to put the files in the main web space for - your web server or perhaps in /usr/local with a symbolic link in the - web space that points to the Bugzilla directory. - - Tip - - If you symlink the bugzilla directory into your Apache's HTML - hierarchy, 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. - - Caution - - The default Bugzilla distribution is not designed to be placed in a - cgi-bin directory (this includes any directory which is configured - using the ScriptAlias directive of Apache). This will probably change - as part of bug 44659. - _________________________________________________________________ - -4.1.6. Setting Up the MySQL Database - - After you've gotten all the software installed and working you're - ready to start preparing the database for its life as the back end to - a high quality bug tracker. - - This first thing you'll want to do is make sure you've given the - "root" user a password as suggested in Section 5.6.2. For clarity, - these instructions will assume that your MySQL user for Bugzilla will - be "bugs_user", the database will be called "bugs_db" and the password - for the "bugs_user" user is "bugs_password". You should, of course, - substitute the values you intend to use for your site. - - Note - - Most people use "bugs" for both the user and database name. - - Next, we use an SQL GRANT command to create a "bugs_user" user, and - grant sufficient permissions for checksetup.pl, which we'll use later, - to work its magic. This also restricts the "bugs_user" user to - operations within a database called "bugs_db", 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. - mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, - DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost - IDENTIFIED BY 'bugs_password'; - mysql> FLUSH PRIVILEGES; - - Note - - If you are using MySQL 4, the bugs user also needs to be granted the - LOCK TABLES and CREATE TEMPORARY TABLES permissions. - _________________________________________________________________ - -4.1.7. checksetup.pl +4.1.6. checksetup.pl - Next, run the magic checksetup.pl script. (Many thanks to Holger - Schurig for writing this script!) This script is designed to make sure - your perl modules are the correct version and your MySQL database and - other configuration options are consistent with the Bugzilla CGI + Next, run the magic checksetup.pl script. This is designed to make + sure your perl modules are the correct version and your MySQL database + and other configuration options are consistent with the Bugzilla CGI files. It will make sure Bugzilla files and directories have reasonable permissions, set up the data directory, and create all the MySQL tables. - bash# ./checksetup.pl +bash# ./checksetup.pl The first time you run it, it will create a file called localconfig. @@ -1296,21 +1208,123 @@ Chapter 4. Installation Note - 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. + 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. _________________________________________________________________ -4.1.8. Configuring Bugzilla +4.1.7. Configuring Bugzilla You should run through the parameters on the Edit Parameters page (link in the footer) and set them all to appropriate values. They key parameters are documented in Section 5.1. _________________________________________________________________ -4.2. Optional Additional Configuration +4.2. HTTP Server Configuration + + The Bugzilla Team recommends Apache when using Bugzilla, however, any + web server that can be configured to run CGI scripts should be able to + handle Bugzilla. No matter what web server you choose, but especially + if you choose something other than Apache, you should be sure to read + Section 4.5.4. + + The plan for this section is to eventually document the specifics of + how to lock down permissions on individual web servers. + _________________________________________________________________ + +4.2.1. Apache httpd + + You will have to make sure that Apache is properly configured to run + the Bugzilla CGI scripts. You also need to make sure that the + .htaccess files created by ./checksetup.pl are allowed to override + Apache's normal access permissions or else important password + information may be exposed to the Internet. + + You need to configure Apache to run .cgi files outside the cgi-bin + directory. Open your httpd.conf file and make sure the following line + exists and is uncommented: +AddHandler cgi-script .cgi + + To allow .htaccess files to override permissions and .cgi files to run + in the Bugzilla directory, make sure the following two lines are in a + Directory directive that applies to the Bugzilla directory on your + system (either the Bugzilla directory or one of its parents). +Options +ExecCGI +AllowOverride Limit + + You should modify the <DirectoryIndex> parameter for the Apache + virtual host running your Bugzilla installation to allow index.cgi as + the index page for a directory, as well as the usual index.html, + index.htm, and so forth. + + Note + + For more information on Apache and its directives, see the glossary + entry on Apache. + _________________________________________________________________ + +4.2.2. Microsoft Internet Information Services + + If you need, or for some reason even want, to use Microsoft's Internet + Information Services or Personal Web Server you should be able to. You + will need to configure them to know how to run CGI scripts, however. + This is described in Microsoft Knowledge Base article Q245225 for + Internet Information Services and Q231998 for Personal Web Server. + + Also, and this can't be stressed enough, make sure that files such as + localconfig and your data directory are secured as described in + Section 4.5.4. + _________________________________________________________________ + +4.2.3. AOL Server + + Ben FrantzDale reported success using AOL Server with Bugzilla. He + reported his experience and what appears below is based on that. + + AOL Server will have to be configured to run CGI scripts, please + consult the documentation that came with your server for more + information on how to do this. + + Because AOL Server doesn't support .htaccess files, you'll have to + create a TCL script. You should create an + aolserver/modules/tcl/filter.tcl file (the filename shouldn't matter) + with the following contents (change /bugzilla/ to the web-based path + to your Bugzilla installation): +ns_register_filter preauth GET /bugzilla/localconfig filter_deny +ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny +ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny +ns_register_filter preauth GET /bugzilla/*.pl filter_deny +ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny +ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny +ns_register_filter preauth GET /bugzilla/data/* filter_deny +ns_register_filter preauth GET /bugzilla/template/* filter_deny + + +proc filter_deny { why } { + ns_log Notice "filter_deny" + return "filter_return" +} + + Warning + + This probably doesn't account for all possible editor backup files so + you may wish to add some additional variations of localconfig. For + more information, see bug 186383 or Bugtraq ID 6501. + + Note + + If you are using webdot from research.att.com (the default + configuration for the webdotbase paramater), you will need to allow + access to data/webdot/*.dot for the reasearch.att.com machine. + + If you are using a local installation of GraphViz, you will need to + allow everybody to access *.png, *.gif, *.jpg, and *.map in the + data/webdot directory. + _________________________________________________________________ + +4.3. Optional Additional Configuration -4.2.1. Dependency Charts +4.3.1. Dependency Charts As well as the text-based dependency graphs, Bugzilla also supports dependency graphing, using a package called 'dot'. Exactly how this @@ -1330,7 +1344,7 @@ Chapter 4. Installation Bugzilla is only accessible using HARTS. _________________________________________________________________ -4.2.2. Bug Graphs +4.3.2. Bug Graphs As long as you installed the GD and Graph::Base Perl modules you might as well turn on the nifty Bugzilla bug reporting graphs. @@ -1345,7 +1359,7 @@ Chapter 4. Installation Bug Reports page. _________________________________________________________________ -4.2.3. The Whining Cron +4.3.3. The Whining Cron By now you have a fully functional Bugzilla, but what good are bugs if they're not annoying? To help make those bugs more annoying you can @@ -1357,27 +1371,18 @@ Chapter 4. Installation cd <your-bugzilla-directory> ; ./whineatnews.pl - Tip - - Depending on your system, crontab may have several manpages. The - following command should lead you to the most useful page for this - purpose: + Tip - man 5 crontab + Depending on your system, crontab may have several manpages. The + following command should lead you to the most useful page for this + purpose: + man 5 crontab _________________________________________________________________ -4.2.4. LDAP Authentication - - Note - - LDAP authentication has been rewritten for the 2.18 release of - Bugzilla. It no longer requires the Mozilla::LDAP module and now uses - Net::LDAP instead. This rewrite was part of a larger landing that - allowed for additional authentication schemes to be easily added (bug - 180642). +4.3.4. LDAP Authentication - This patch originally landed in 21-Mar-2003 and was included in the - 2.17.4 development release. + LDAP authentication is a module for Bugzilla's plugin authentication + architecture. The existing authentication scheme for Bugzilla uses email addresses as the primary user ID, and a password to authenticate that user. All @@ -1395,14 +1400,14 @@ Chapter 4. Installation tasks are still handled by email address, not LDAP username. You still assign bugs by email address, query on users by email address, etc. - Caution + Caution - Because the Bugzilla account is not created until the first time a - user logs in, a user who has not yet logged is unknown to Bugzilla. - This means they cannot be used as an assignee or QA contact (default - or otherwise), added to any cc list, or any other such operation. One - possible workaround is the bugzilla_ldapsync.rb script in the contrib - directory. Another possible solution is fixing bug 201069. + Because the Bugzilla account is not created until the first time a + user logs in, a user who has not yet logged is unknown to Bugzilla. + This means they cannot be used as an assignee or QA contact (default + or otherwise), added to any cc list, or any other such operation. One + possible workaround is the bugzilla_ldapsync.rb script in the contrib + directory. Another possible solution is fixing bug 201069. Parameters required to use LDAP Authentication: @@ -1452,52 +1457,33 @@ Chapter 4. Installation Ex. "mail" _________________________________________________________________ -4.2.5. Preventing untrusted Bugzilla content from executing malicious +4.3.5. Preventing untrusted Bugzilla content from executing malicious Javascript code - It is possible for a Bugzilla to execute malicious Javascript code. - Due to internationalization concerns, we are unable to incorporate the - code changes necessary to fulfill the CERT advisory requirements - mentioned in - http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3. - Making the change below will fix the problem if your installation is - for an English speaking audience. - - Telling Bugzilla to output a charset as part of the HTTP header is - much easier in version 2.18 and higher (including any cvs pull after - 4-May-2003 and development release after 2.17.5) than it was in - previous versions. Simply locate the following line in - Bugzilla/CGI.pm: - # Make sure that we don't send any charset headers - $self->charset(''); + It is possible for a Bugzilla attachment to contain malicious + Javascript code, which would be executed in the domain of your + Bugzilla, thereby making it possible for the attacker to e.g. steal + your login cookies. Due to internationalization concerns, we are + unable to incorporate by default the code changes necessary to fulfill + the CERT advisory requirements mentioned in + http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3. If + your installation is for an English speaking audience only, making the + change below will prevent this problem. - and change it to: - # Send all data using the ISO-8859-1 charset - $self->charset('ISO-8859-1'); + Simply locate the following line in Bugzilla/CGI.pm: + $self->charset(''); - 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. See bug 126266 for more information including progress toward - making bugzilla charset aware by default. - _________________________________________________________________ - -4.2.6. directoryindex for the Bugzilla default page. - - You should modify the <DirectoryIndex> parameter for the Apache - virtual host running your Bugzilla installation to allow index.cgi as - the index page for a directory, as well as the usual index.html, - index.htm, and so forth. + and change it to: + $self->charset('ISO-8859-1'); _________________________________________________________________ -4.2.7. Bugzilla and mod_perl +4.3.6. Bugzilla and mod_perl Bugzilla is unsupported under mod_perl. Effort is underway to make it work cleanly in a mod_perl environment, but it is slow going. _________________________________________________________________ -4.2.8. mod_throttle and Security +4.3.7. mod_throttle and Security It is possible for a user, by mistake or on purpose, to access the database many times in a row which can result in very slow access @@ -1511,7 +1497,7 @@ Javascript code Instructions for more information. _________________________________________________________________ -4.3. OS Specific Installation Notes +4.4. OS Specific Installation Notes Many aspects of the Bugzilla installation can be affected by the the operating system you choose to install it on. Sometimes it can be made @@ -1523,9 +1509,9 @@ Javascript code covered, please file a bug in Bugzilla Documentation. _________________________________________________________________ -4.3.1. Microsoft Windows +4.4.1. Microsoft Windows - Making Bugzilla work on windows is still a very painful processes. The + Making Bugzilla work on windows is still a painful processes. The Bugzilla Team is working to make it easier, but that goal is not considered a top priority. If you wish to run Bugzilla, we still recommend doing so on a Unix based system such as GNU/Linux. As of @@ -1540,104 +1526,99 @@ Javascript code compatibility by the 2.18 release. _________________________________________________________________ -4.3.1.1. Win32 Perl +4.4.1.1. Win32 Perl Perl for Windows can be obtained from ActiveState. You should be able to find a compiled binary at http://aspn.activestate.com/ASPN/Downloads/ActivePerl/. _________________________________________________________________ -4.3.1.2. Perl Modules on Win32 +4.4.1.2. Perl Modules on Win32 Bugzilla on Windows requires the same perl modules found in Section - 4.1.3. The main difference is that windows uses PPM instead of CPAN. - C:\perl> ppm <module name> + 4.1.5. The main difference is that windows uses PPM instead of CPAN. +C:\perl> ppm <module name> Note - The above syntax should work for all modules with the exception of - Template Toolkit. The Template Toolkit website suggests using the - instructions on OpenInteract's website. + The above syntax should work for all modules with the exception of + Template Toolkit. The Template Toolkit website suggests using the + instructions on OpenInteract's website. Tip - A complete list of modules that can be installed using ppm can be - found at http://www.activestate.com/PPMPackages/5.6plus. + A complete list of modules that can be installed using ppm can be + found at http://www.activestate.com/PPMPackages/5.6plus. _________________________________________________________________ -4.3.1.3. Code changes required to run on win32 +4.4.1.3. Code changes required to run on win32 - Unfortunately, Bugzilla still doesn't run "out of the box" on Windows. - There is work in progress to make this easier, but until that happens - code will have to be modified. This section is an attempt to list the - required changes. It is an attempt to be all inclusive, but there may - be other changes required. If you find something is missing, please - file a bug in Bugzilla Documentation. + As Bugzilla still doesn't run "out of the box" on Windows, code has to + be modified. This section is an attempt to list the required changes. _________________________________________________________________ -4.3.1.3.1. Changes to checksetup.pl +4.4.1.3.1. Changes to checksetup.pl In checksetup.pl, the line reading: - my $mysql_binaries = `which mysql`; +my $mysql_binaries = `which mysql`; to - my $mysql_binaries = "D:\\mysql\\bin\\mysql"; +my $mysql_binaries = "D:\\mysql\\bin\\mysql"; And you'll also need to change: - my $webservergid = getgrnam($my_webservergroup) +my $webservergid = getgrnam($my_webservergroup) to - my $webservergid = '8' +my $webservergid = '8' _________________________________________________________________ -4.3.1.3.2. Changes to BugMail.pm +4.4.1.3.2. Changes to BugMail.pm To make bug e-mail work on Win32 (until bug 84876 lands), the simplest - way is to have Net::SMTP installed and change this (in - Bugzilla/BugMail.pm): - open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") || - die "Can't open sendmail"; + way is to have the Net::SMTP Perl module installed and change this: +open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") || + die "Can't open sendmail"; - print SENDMAIL trim($msg) . "\n"; - close SENDMAIL; +print SENDMAIL trim($msg) . "\n"; +close SENDMAIL; to - use Net::SMTP; - my $smtp_server = 'smtp.mycompany.com'; # change this +use Net::SMTP; +my $smtp_server = 'smtp.mycompany.com'; # change this - # Use die on error, so that the mail will be in the 'unsent mails' and - # can be sent from the sanity check page. - my $smtp = Net::SMTP->new($smtp_server) || - die 'Cannot connect to server \'$smtp_server\''; +# Use die on error, so that the mail will be in the 'unsent mails' and +# can be sent from the sanity check page. +my $smtp = Net::SMTP->new($smtp_server) || + die 'Cannot connect to server \'$smtp_server\''; - $smtp->mail('bugzilla-daemon@mycompany.com'); # change this - $smtp->to($person); - $smtp->data(); - $smtp->datasend($msg); - $smtp->dataend(); - $smtp->quit; +$smtp->mail('bugzilla-daemon@mycompany.com'); # change this +$smtp->to($person); +$smtp->data(); +$smtp->datasend($msg); +$smtp->dataend(); +$smtp->quit; Don't forget to change the name of your SMTP server and the domain of the sending e-mail address (after the '@') in the above lines of code. _________________________________________________________________ -4.3.1.4. Serving the web pages +4.4.1.4. Serving the web pages As is the case on Unix based systems, any web server should be able to handle Bugzilla; however, the Bugzilla Team still recommends Apache whenever asked. No matter what web server you choose, be sure to pay - attention to the security notes in Section 5.6.4. More information on - configuring specific web servers can be found in Section 4.4. + attention to the security notes in Section 4.5.4. More information on + configuring specific web servers can be found in Section 4.2. Note - If using Apache on windows, you can set the ScriptInterpreterSource - directive in your Apache config, if you don't do this, you'll have to - modify the first line of every script to contain your path to perl - instead of /usr/bin/perl. + If using Apache on windows, you can set the ScriptInterpreterSource + directive in your Apache config, if you don't do this, you'll have to + modify the first line of every script to contain your path to perl + instead of /usr/bin/perl. _________________________________________________________________ -4.3.2. Mac OS X +4.4.2. Mac OS X 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 @@ -1657,210 +1638,186 @@ Javascript code Note - 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 be at /sw/lib and /sw/include instead of /usr/lib and - /usr/local/include. When the Perl module config script asks where your - libgd is, be sure to tell it /sw/lib. + 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 be at /sw/lib and /sw/include instead of /usr/lib and + /usr/local/include. When the Perl module config script asks where your + libgd is, be sure to tell it /sw/lib. Also available via Fink is expat. Once running using fink to install the expat package you will be able to install XML::Parser using CPAN. There is one caveat. Unlike recent versions of the GD module, XML::Parser doesn't prompt for the location of the required libraries. When using CPAN, you will need to use the following command sequence: - # perl -MCPAN -e'look XML::Parser' (1) - # perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include - # make; make test; make install (2) - # exit (3) +# perl -MCPAN -e'look XML::Parser' (1) +# perl Makefile.PL EXPATLIBPATH=/sw/lib EXPATINCPATH=/sw/include +# make; make test; make install (2) +# exit (3) - (1) (3) + (1) (3) The look command will download the module and spawn a new shell with the extracted files as the current working directory. The exit command will return you to your original shell. - (2) + (2) You should watch the output from these make commands, especially "make test" as errors may prevent XML::Parser from functioning correctly with Bugzilla. _________________________________________________________________ -4.3.3. Linux-Mandrake 8.0 +4.4.3. Linux-Mandrake 8.0 Linux-Mandrake 8.0 includes every required and optional library for Bugzilla. The easiest way to install them is by using the 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. - bash# urpmi perl-mysql - bash# urpmi perl-chart - bash# urpmi perl-gd - bash# urpmi perl-MailTools (1) - bash# urpmi apache-modules +bash# urpmi perl-mysql +bash# urpmi perl-chart +bash# urpmi perl-gd +bash# urpmi perl-MailTools (1) +bash# urpmi apache-modules - (1) + (1) for Bugzilla e-mail integration _________________________________________________________________ -4.4. HTTP Server Configuration +4.5. Bugzilla Security - The Bugzilla Team recommends Apache when using Bugzilla, however, any - web server that can be configured to run CGI scripts should be able to - handle Bugzilla. No matter what web server you choose, but especially - if you choose something other than Apache, you should be sure to read - Section 5.6.4. + Warning - The plan for this section is to eventually document the specifics of - how to lock down permissions on individual web servers. + 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. + + This is not meant to be a comprehensive list of every possible + security issue pertaining to the software mentioned in this section. + There is no subsitute for reading the information written by the + authors of any software running on your system. _________________________________________________________________ -4.4.1. Apache httpd +4.5.1. TCP/IP Ports - As mentioned above, the Bugzilla Team recommends Apache for use with - Bugzilla. You will have to make sure that Apache is properly - configured to run the Bugzilla CGI scripts. You also need to make sure - that the .htaccess files created by ./checksetup.pl (shown in Example - 4-2 for the curious) are allowed to override Apache's normal access - permissions or else important password information may be exposed to - the Internet. + TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla only + needs 1, or 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. + _________________________________________________________________ - Many Apache installations are not configured to run scripts anywhere - but in the cgi-bin directory; however, we recommend that Bugzilla not - be installed in the cgi-bin, otherwise the static files such as images - and JavaScript will not work correctly. To allow scripts to run in the - normal web space, the following changes should be made to your - httpd.conf file. +4.5.2. MySQL - To allow files with a .cgi extension to be run, make sure the - following line exists and is uncommented: - AddHandler cgi-script .cgi + 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. - To allow .htaccess files to override permissions and .cgi files to run - in the Bugzilla directory, make sure the following two lines are in a - Directory directive that applies to the Bugzilla directory on your - system (either the Bugzilla directory or one of its parents). - Options +ExecCGI - AllowOverride Limit + 1. Consult the documentation that came with your system for + information on making mysqld run as an unprivleged user. + 2. 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: - Note +bash$ mysql mysql +mysql> DELETE FROM user WHERE user = ''; +mysql> UPDATE user SET password = password('new_password') WHERE user = 'root'; +mysql> FLUSH PRIVILEGES; - For more information on Apache and its directives, see the glossary - entry on Apache. - - Example 4-2. .htaccess files for Apache - - $BUGZILLA_HOME/.htaccess - # don't allow people to retrieve non-cgi executable files or our private data - <FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$> - deny from all - </FilesMatch> - <FilesMatch ^(localconfig.js|localconfig.rdf)$> - allow from all - </FilesMatch> - - $BUGZILLA_HOME/data/.htaccess - # nothing in this directory is retrievable unless overriden by an .htaccess - # in a subdirectory; the only exception is duplicates.rdf, which is used by - # duplicates.xul and must be loadable over the web - deny from all - <Files duplicates.rdf> - allow from all - </Files> - - $BUGZILLA_HOME/data/webdot -# Restrict access to .dot files to the public webdot server at research.att.com - -# if research.att.com ever changed their IP, or if you use a different -# webdot server, you'll need to edit this -<FilesMatch ^[0-9]+\.dot$> - Allow from 192.20.225.10 - Deny from all -</FilesMatch> - -# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and -# .map files -<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> - Allow from all -</FilesMatch> - -# And no directory listings, either. -Deny from all - - $BUGZILLA_HOME/Bugzilla/.htaccess - # nothing in this directory is retrievable unless overriden by an .htaccess - # in a subdirectory - deny from all - - $BUGZILLA_HOME/template/.htaccess - # nothing in this directory is retrievable unless overriden by an .htaccess - # in a subdirectory - deny from all - _________________________________________________________________ - -4.4.2. Microsoft Internet Information Services - If you need, or for some reason even want, to use Microsoft's Internet - Information Services or Personal Web Server you should be able to. You - will need to configure them to know how to run CGI scripts, however. - This is described in Microsoft Knowledge Base article Q245225 for - Internet Information Services and Q231998 for Personal Web Server. + From this point forward you will need to use mysql -u root -p and + enter new_password when prompted when using the mysql client. + 3. 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: - Also, and this can't be stressed enough, make sure that files such as - localconfig and your data directory are secured as described in - Section 5.6.4. +[myslqd] +# Prevent network access to MySQL. +skip-networking + + + 4. 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. _________________________________________________________________ -4.4.3. AOL Server +4.5.3. Daemon Accounts - Ben FrantzDale reported success using AOL Server with Bugzilla. He - reported his experience and what appears below is based on that. + 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 compromised, + they all get compromised. For this reason it is recommended that you + create a user account for each daemon. - AOL Server will have to be configured to run CGI scripts, please - consult the documentation that came with your server for more - information on how to do this. + Note - Because AOL Server doesn't support .htaccess files, you'll have to - create a TCL script. You should create an - aolserver/modules/tcl/filter.tcl file (the filename shouldn't matter) - with the following contents (change /bugzilla/ to the web-based path - to your Bugzilla installation): - ns_register_filter preauth GET /bugzilla/localconfig filter_deny - ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny - ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny - ns_register_filter preauth GET /bugzilla/*.pl filter_deny - ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny - ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny - ns_register_filter preauth GET /bugzilla/data/* filter_deny - ns_register_filter preauth GET /bugzilla/template/* filter_deny + 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. + _________________________________________________________________ +4.5.4. Web Server Access Controls - proc filter_deny { why } { - ns_log Notice "filter_deny" - return "filter_return" - } + 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 laid out, the list of what should and should not + be accessible is rather complicated. - Warning + Users of Apache don't need to worry about this, however, because + Bugzilla ships with .htaccess files which restrict access to all the + sensitive files in this section. Users of other webservers, read on. - This probably doesn't account for all possible editor backup files so - you may wish to add some additional variations of localconfig. For - more information, see bug 186383 or Bugtraq ID 6501. + * In the main Bugzilla directory, you should: + + Block: *.pl, *localconfig*, runtests.sh + + But allow: localconfig.js, localconfig.rdf + * In data: + + Block everything + + But allow: duplicates.rdf + * In data/webdot: + + If you use a remote webdot server: + o Block everything + o But allow *.dot only for the remote webdot server + + Otherwise, if you use a local GraphViz: + o Block everything + o But allow: *.png, *.gif, *.jpg, *.map + + And if you don't use any dot: + o Block everything + * In Bugzilla: + + Block everything + * In template: + + Block everything - Note + 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. + + Caution + + Not following the instructions in this section, including testing, may + result in sensitive information being globally accessible. - If you are using webdot from research.att.com (the default - configuration for the webdotbase paramater), you will need to allow - access to data/webdot/*.dot for the reasearch.att.com machine. + Tip - If you are using a local installation of GraphViz, you will need to - allow everybody to access *.png, *.gif, *.jpg, and *.map in the - data/webdot directory. + You should check Section 4.2 to see if instructions have been included + for your web server. You should also compare those instructions with + this list to make sure everything is properly accounted for. _________________________________________________________________ -4.5. Troubleshooting +4.6. Troubleshooting This section gives solutions to common Bugzilla installation problems. _________________________________________________________________ -4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 +4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 Try executing perl -MCPAN -e 'install CPAN' and then continuing. @@ -1873,7 +1830,7 @@ Deny from all commandline above should fix things. _________________________________________________________________ -4.5.2. DBD::Sponge::db prepare failed +4.6.2. DBD::Sponge::db prepare failed The following error message may appear due to a bug in DBD::mysql (over which the Bugzilla team have no control): @@ -1885,23 +1842,23 @@ Deny from all 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}}; + 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}}; + my $numFields; + if ($attribs->{'NUM_OF_FIELDS'}) { + $numFields = $attribs->{'NUM_OF_FIELDS'}; + } elsif ($attribs->{'NAMES'}) { + $numFields = @{$attribs->{NAMES}}; (note the S added to NAME.) _________________________________________________________________ -4.5.3. cannot chdir(/var/spool/mqueue) +4.6.3. cannot chdir(/var/spool/mqueue) If you are installing Bugzilla on SuSE Linux, or some other distributions with "paranoid" security options, it is possible that @@ -1913,45 +1870,45 @@ Deny from all problem. _________________________________________________________________ -4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT +4.6.4. Your vendor has not defined Fcntl macro O_NOINHERIT This is caused by a bug in the version of File::Temp that is distributed with perl 5.6.0. Many minor variations of this error have been reported. Examples can be found in Figure 4-2. Figure 4-2. 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_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_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. +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-3. The patch is also available as a patch file. Figure 4-3. 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; - }; +--- 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; + }; _________________________________________________________________ Chapter 5. Administering Bugzilla @@ -1991,7 +1948,7 @@ Chapter 5. Administering Bugzilla not yet take advantage of features such as transactions which would justify this speed decrease. The Bugzilla team are, however, happy to hear about any experiences with row level locking and - Bugzilla + Bugzilla. 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 @@ -1999,9 +1956,9 @@ Chapter 5. Administering Bugzilla 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. + As a guide, on reasonably old hardware, 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. You will need to set the host and port settings from the params page, and set up replication in your database server so @@ -2047,12 +2004,12 @@ Chapter 5. Administering Bugzilla wise idea to require comments when users resolve, reassign, or reopen bugs at the very least. - Note + Note - 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!) + 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!) 13. 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 @@ -2075,10 +2032,10 @@ Chapter 5. Administering Bugzilla Tip - If you wish to add more administrative users, add them to the "admin" - group and, optionally, add edit the tweakparams, editusers, - creategroups, editcomponents, and editkeywords groups to add the - entire admin group to those groups. + If you wish to add more administrative users, add them to the "admin" + group and, optionally, add edit the tweakparams, editusers, + creategroups, editcomponents, and editkeywords groups to add the + entire admin group to those groups. _________________________________________________________________ 5.2.2. Managing Other Users @@ -2095,15 +2052,15 @@ Chapter 5. Administering Bugzilla 2. Fill out the form presented. This page is self-explanatory. When done, click "Submit". - Note + Note - 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. + 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. _________________________________________________________________ 5.2.2.2. Modifying Users @@ -2139,13 +2096,13 @@ Chapter 5. Administering Bugzilla Warning - Don't disable the administrator account! + Don't disable all the administrator accounts! - Note + Note - 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. + 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. @@ -2180,9 +2137,7 @@ Chapter 5. Administering Bugzilla the "editbugs" privilege to edit bugs in these products. _________________________________________________________________ -5.3. Product, Component, Milestone, and Version Administration - -5.3.1. Products +5.3. Products Products are the broadest category in Bugzilla, and tend to represent real-world shipping products. E.g. if your company makes computer @@ -2209,7 +2164,7 @@ Chapter 5. Administering Bugzilla few moments. _________________________________________________________________ -5.3.2. Components +5.4. Components Components are subsections of a Product. E.g. the computer game you are designing may have a "UI" component, an "API" component, a "Sound @@ -2238,12 +2193,12 @@ Chapter 5. Administering Bugzilla database. _________________________________________________________________ -5.3.3. Versions +5.5. Versions Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select - field; the usual practice is to select the most recent version with - the bug. + field; the usual practice is to select the earliest version known to + have the bug. To create and edit Versions: @@ -2254,7 +2209,7 @@ Chapter 5. Administering Bugzilla click the "Add" button. _________________________________________________________________ -5.3.4. Milestones +5.6. Milestones Milestones are "targets" that you plan to get a bug fixed by. For example, you have a bug that you plan to fix for your 3.0 release, it @@ -2262,8 +2217,8 @@ Chapter 5. Administering Bugzilla Note - Milestone options will only appear for a Product if you turned on the - "usetargetmilestone" Param in the "Edit Parameters" screen. + 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: @@ -2278,16 +2233,9 @@ Chapter 5. Administering Bugzilla after "Release 1.2". Select "Add". 4. From the Edit product screen, you can enter the URL of a page which gives information about your milestones and what they mean. - - Tip - - 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. _________________________________________________________________ -5.4. Voting +5.7. Voting Voting allows users to be given a pot of votes which they can allocate to bugs, to indicate that they'd like them fixed. This allows @@ -2314,7 +2262,7 @@ Chapter 5. Administering Bugzilla "Update". _________________________________________________________________ -5.5. Groups and Group Security +5.8. Groups and Group Security Groups allow the administrator to isolate bugs or products that should only be seen by certain people. The association between products and @@ -2358,12 +2306,12 @@ Chapter 5. Administering Bugzilla fulfill the Regular Expression into the new group. When you have finished, click "Add". - Warning + Warning - The User Regexp is a perl regexp and, if not anchored, will match any - part of an address. So, if you do not want to grant access into - 'mycompany.com' to 'badperson@mycompany.com.hacker.net', use - '@mycompany\.com$' as the regexp. + If specifying a domain in the regexp, make sure you end the regexp + with a $. Otherwise, when granting access to "@mycompany\.com", you + will allow access to 'badperson@mycompany.com.cracker.net'. You need + to use '@mycompany\.com$' as the regexp. 4. After you add your new group, edit the new group. On the edit page, you can specify other groups that should be included in this group and which groups should be permitted to add and delete users @@ -2377,194 +2325,197 @@ Chapter 5. Administering Bugzilla in that product. _________________________________________________________________ -5.6. Bugzilla Security +5.9. Upgrading to New Releases Warning - 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. - - Note - - 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 Documentation. + Upgrading is a one-way process. You should backup your database and + current Bugzilla directory before attempting the upgrade. If you wish + to revert to the old Bugzilla version for any reason, you will have to + restore from these backups. - Warning + 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. - 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. - _________________________________________________________________ + * If the new version is a revision or a new point release + * How many, if any, local changes have been made -5.6.1. TCP/IP Ports + There are also three different methods to upgrade your installation. - 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. - _________________________________________________________________ + 1. Using CVS (Example 5-1) + 2. Downloading a new tarball (Example 5-2) + 3. Applying the relevant patches (Example 5-3) -5.6.2. MySQL + Which options are available to you may depend on how large a jump you + are making and/or your network configuration. - 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. + 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. - 1. Consult the documentation that came with your system for - information on making mysqld run as an unprivleged user. - 2. 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: + 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. -bash$ mysql mysql -mysql> DELETE FROM user WHERE user = ''; -mysql> UPDATE user SET password = password('new_password') WHERE user = 'root'; -mysql> FLUSH PRIVILEGES; + 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. - From this point forward you will need to use mysql -u root -p and - enter new_password when prompted when using the mysql client. - 3. 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: + Example 5-1. Upgrading using CVS - [myslqd] - # Prevent network access to MySQL. - skip-networking + Every release of Bugzilla, whether it is a revision or a point + release, is tagged in CVS. Also, every tarball we have distributed + since version 2.12 has been primed for using CVS. This does, however, + require that you are able to access cvs-mirror.mozilla.org on port + 2401. + Tip - 4. 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. - _________________________________________________________________ + If you can do this, updating using CVS is probably the most painless + method, especially if you have a lot of local changes. +bash$ cd /var/www/html/bugzilla +bash$ cvs login +Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot +CVS password: anonymous +bash$ cvs -q update -r BUGZILLA-2_16_2 -dP +P checksetup.pl +P collectstats.pl +P globals.pl +P docs/rel_notes.txt +P template/en/default/list/quips.html.tmpl -5.6.3. Daemon Accounts + Caution - 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. + If a line in the output from cvs update begins with a C that + represents a file with local changes that CVS was unable to properly + merge. You need to resolve these conflicts manually before Bugzilla + (or at least the portion using that file) will be usable. Note - 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. - _________________________________________________________________ + You also need to run ./checksetup.pl before your Bugzilla upgrade will + be complete. -5.6.4. Web Server Access Controls + Example 5-2. Upgrading using the tarball - 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. + If you are unable or unwilling to use CVS, another option that's + always available is to download the latest tarball. This is the most + difficult option to use, especially if you have local changes. +bash$ cd /var/www/html +bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz +Output omitted +bash$ tar xzvf bugzilla-2.16.2.tar.gz +bugzilla-2.16.2/ +bugzilla-2.16.2/.cvsignore +bugzilla-2.16.2/1x1.gif +Output truncated +bash$ cd bugzilla-2.16.2 +bash$ cp ../bugzilla/localconfig* . +bash$ cp -r ../bugzilla/data . +bash$ cd .. +bash$ mv bugzilla bugzilla.old +bash$ mv bugzilla-2.16.2 bugzilla +bash$ cd bugzilla +bash$ ./checksetup.pl +Output omitted - * In the main Bugzilla directory, you should: - + Block: *.pl, *localconfig*, runtests.sh - + But allow: localconfig.js, localconfig.rdf - * In data: - + Block everything - + But allow: duplicates.rdf - * In data/webdot: - + If you use a remote webdot server: - o Block everything - o But allow *.dot only for the remote webdot server - + Otherwise, if you use a local GraphViz: - o Block everything - o But allow: *.png, *.gif, *.jpg, *.map - + And if you don't use any dot: - o Block everything - * In Bugzilla: - + Block everything - * In template: - + Block everything + Warning - Tip + The cp commands both end with periods which is a very important + detail, it tells the shell that the destination directory is the + current working directory. Also, the period at the beginning of the + ./checksetup.pl is important and can not be omitted. - Bugzilla ships with the ability to generate .htaccess files - instructing Apache which files should and should not be accessible. - For more information, see Section 4.4.1. + Note - 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. + You will now have to reapply any changes you have made to your local + installation manually. - Caution + Example 5-3. Upgrading using patches - Not following the instructions in this section, including testing, may - result in sensitive information being globally accessible. + The Bugzilla team will normally make a patch file available for + revisions to go from the most recent revision to the new one. You + could also read the release notes and grab the patches attached to the + mentioned bug, but it is safer to use the released patch file as + sometimes patches get changed before they get checked in. It is also + theoretically possible to scour the fixed bug list and pick and choose + which patches to apply from a point release, but this is not + recommended either as what you'll end up with is a hodge podge + Bugzilla that isn't really any version. This would also make it more + difficult to upgrade in the future. +bash$ cd /var/www/html/bugzilla +bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz +Output omitted +bash$ gunzip bugzilla-2.16.1-to-2.16.2.diff.gz +bash$ patch -p1 < bugzilla-2.16.1-to-2.16.2.diff +patching file checksetup.pl +patching file collectstats.pl +patching file globals.pl - Tip + Caution - You should check Section 4.4 to see if instructions have been included - for your web server. You should also compare those instructions with - this list to make sure everything is properly accounted for. + If you do this, beware that this doesn't change the entires in your + CVS directory so it may make updates using CVS (Example 5-1) more + difficult in the future. _________________________________________________________________ -5.7. Template Customization +Chapter 6. Customising Bugzilla + +6.1. Template Customization - One of the large changes for 2.16 was the templatization 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. + Administrators can 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. Templatization also makes localized versions of Bugzilla possible, for - the first time. As of version 2.17.4 which will soon become 2.18, it's - possible to have Bugzilla's language determined by the user's browser. - More information is available in Section 5.7.5. + the first time. It's possible to have Bugzilla's UI language + determined by the user's browser. More information is available in + Section 6.1.5. _________________________________________________________________ -5.7.1. What to Edit +6.1.1. What to Edit - There are two different ways of editing of Bugzilla's templates, and - which you use depends mainly on how you upgrade Bugzilla. The template - directory structure is that there's a top level directory, template, - which contains a directory for each installed localization. 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 template directory structure is that there's a top level + directory, template, which contains a directory for each installed + localization. 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 customizations 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. + There are two different ways of editing Bugzilla's templates, and + which you use depends mainly on the method you plan to use to upgrade + Bugzilla. The first method of making customizations 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. + The other method is to copy the templates to be modified 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 @@ -2576,32 +2527,36 @@ mysql> FLUSH PRIVILEGES; Note - Don't directly edit the compiled templates in data/template/* - your - changes will be lost when Template Toolkit recompiles them. + Don't directly edit the compiled templates in data/template/* - your + changes will be lost when Template Toolkit recompiles them. Note - It is recommended that you run ./checksetup.pl after any template - edits, especially if you've created a new file in the custom - directory. + It is recommended that you run ./checksetup.pl after any template + edits, especially if you've created a new file in the custom + directory. _________________________________________________________________ -5.7.2. How To Edit Templates +6.1.2. How To Edit Templates + + Note + + 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. 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. + Toolkit home page. + + 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 forget, 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 @@ -2616,15 +2571,9 @@ mysql> FLUSH PRIVILEGES; a free-form text entry box for "Build Identifier", then you can just edit the templates to change the field labels. It's still be called status_whiteboard internally, but your users don't need to know that. - - Note - - 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. _________________________________________________________________ -5.7.3. Template Formats +6.1.3. Template Formats Some CGIs have the ability to use more than one template. For example, buglist.cgi can output bug lists as RDF or two different forms of HTML @@ -2633,8 +2582,8 @@ mysql> FLUSH PRIVILEGES; 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. + "GetFormat". If it's not present, adding multiple format support isn't + too hard - see how it's done in other CGIs, e.g. config.cgi. 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 @@ -2655,7 +2604,7 @@ mysql> FLUSH PRIVILEGES; <cginame>.cgi?format=<formatname> . _________________________________________________________________ -5.7.4. Particular Templates +6.1.4. Particular Templates There are a few templates you may be particularly interested in customizing for your installation. @@ -2684,16 +2633,6 @@ mysql> FLUSH PRIVILEGES; the top of the bug reporting page. By modifying this, you can tell your users how they should report bugs. - bug/process/midair.html.tmpl: This is the page used if two people - submit simultaneous changes to the same bug. The second person to - submit their changes will get this page to tell them what the first - person did, and ask if they wish to overwrite those changes or go back - and revisit the bug. The default title and header on this page read - "Mid-air collision detected!" If you work in the aviation industry, or - other environment where this might be found offensive (yes, we have - true stories of this happening) you'll want to change this to - something more appropriate for your environment. - 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 @@ -2728,33 +2667,31 @@ mysql> FLUSH PRIVILEGES; would appear in the initial checkin comment. _________________________________________________________________ -5.7.5. Configuring Bugzilla to Detect the User's Language +6.1.5. Configuring Bugzilla to Detect the User's Language - Begining in version 2.18 (first introduced in version 2.17.4), it's - now possible to have the users web browser tell Bugzilla which - language templates to use for each visitor (using the HTTP_ACCEPT - header). For this to work, Bugzilla needs to have the correct language - templates installed for the version of Bugzilla you are using. Many + Bugzilla honours the user's Accept: HTTP header. You can install + templates in other languages, and Bugzilla will pick the most + appropriate according to a priority order defined by you. Many language templates can be obtained from http://www.bugzilla.org/download.html#localizations. Instructions for submitting new languages are also available from that location. After untarring the localizations (or creating your own) in the - [Bugzilla_Root]/template directory, you must update the languages + $BUGZILLA_HOME/template directory, you must update the languages parameter to contain any localizations you'd like to permit. You may also wish to set the defaultlanguage parameter to something other than "en" if you don't want Engish to be the default language. _________________________________________________________________ -5.8. Change Permission Customization +6.2. Customizing Who Can Change What - Warning + Warning - This feature should be considered experimental; the Bugzilla code you - will be changing is not stable, and could change or move between - versions. Be aware that if you make modifications to it, you may have - to re-make them or port them if Bugzilla changes internally between - versions. + This feature should be considered experimental; the Bugzilla code you + will be changing is not stable, and could change or move between + versions. Be aware that if you make modifications as outlined here, + you may have to re-make them or port them if Bugzilla changes + internally between versions, and you upgrade. Companies often have rules about which employees, or classes of employees, are allowed to change certain things in the bug system. For @@ -2775,10 +2712,10 @@ mysql> FLUSH PRIVILEGES; Certain marked sections should not be changed - these are the "plumbing" which makes the rest of the function work. In between those sections, you'll find snippets of code like: - # Allow the owner to change anything. - if ($ownerid eq $whoid) { - return 1; - } + # Allow the owner to change anything. + if ($ownerid eq $whoid) { + return 1; + } It's fairly obvious what this piece of code does. @@ -2795,27 +2732,27 @@ mysql> FLUSH PRIVILEGES; $ownerid has been obtained from the database. You can either add a positive check, which returns 1 (allow) if certain conditions are true, or a negative check, which returns 0 (deny.) E.g.: - if ($field eq "qacontact") { - if (Bugzilla->user->groups("quality_assurance")) { - return 1; - } - else { - return 0; - } - } + if ($field eq "qacontact") { + if (Bugzilla->user->groups("quality_assurance")) { + return 1; + } + else { + return 0; + } + } This says that only users in the group "quality_assurance" can change the QA Contact field of a bug. Getting more weird: - if (($field eq "priority") && - (Bugzilla->user->email =~ /.*\@example\.com$/)) - { - if ($oldvalue eq "P1") { - return 1; - } - else { - return 0; - } - } + if (($field eq "priority") && + (Bugzilla->user->email =~ /.*\@example\.com$/)) + { + if ($oldvalue eq "P1") { + return 1; + } + else { + return 0; + } + } This says that if the user is trying to change the priority field, and their email address is @example.com, they can only do so if the old @@ -2826,156 +2763,330 @@ mysql> FLUSH PRIVILEGES; your organization, ask in the newsgroup. _________________________________________________________________ -5.9. Upgrading to New Releases - - Warning - - Upgrading is a one-way process. You should backup your database and - current Bugzilla directory before attempting the upgrade. If you wish - to revert to the old Bugzilla version for any reason, you will have to - restore from these backups. +6.3. Modifying Your Running System - 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. - - 1. Using CVS (Example 5-1) - 2. Downloading a new tarball (Example 5-2) - 3. 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. + Bugzilla optimizes database lookups by storing all relatively static + information in the versioncache file, located in the data/ + subdirectory under your installation directory. - 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. + If you make a change to the structural data in your database (the + versions table for example), or to the "constants" encoded in + defparams.pl, you will need to remove the cached content from the data + directory (by doing a "rm data/versioncache" ), or your changes won't + show up. - 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. + versioncache gets automatically regenerated whenever it's more than an + hour old, so Bugzilla will eventually notice your changes by itself, + but generally you want it to notice right away, so that you can test + things. + _________________________________________________________________ - Example 5-1. Upgrading using CVS +6.4. MySQL Bugzilla Database Introduction - Every release of Bugzilla, whether it is a revision or a point - release, is tagged in CVS. Also, every tarball we have distributed - since version 2.12 has been primed for using CVS. This does, however, - require that you are able to access cvs-mirror.mozilla.org on port - 2401. + This information comes straight from my life. I was forced to learn + how Bugzilla organizes database because of nitpicky requests from + users for tiny changes in wording, rather than having people + re-educate themselves or figure out how to work our procedures around + the tool. It sucks, but it can and will happen to you, so learn how + the schema works and deal with it when it comes. - Tip + So, here you are with your brand-new installation of Bugzilla. You've + got MySQL set up, Apache working right, Perl DBI and DBD talking to + the database flawlessly. Maybe you've even entered a few test bugs to + make sure email's working; people seem to be notified of new bugs and + changes, and you can enter and edit bugs to your heart's content. + Perhaps you've gone through the trouble of setting up a gateway for + people to submit bugs to your database via email, have had a few + people test it, and received rave reviews from your beta testers. - If you can do this, updating using CVS is probably the most painless - method, especially if you have a lot of local changes. - bash$ cd /var/www/html/bugzilla - bash$ cvs login - Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot - CVS password: anonymous - bash$ cvs -q update -r BUGZILLA-2_16_2 -dP - P checksetup.pl - P collectstats.pl - P globals.pl - P docs/rel_notes.txt - P template/en/default/list/quips.html.tmpl + What's the next thing you do? Outline a training strategy for your + development team, of course, and bring them up to speed on the new + tool you've labored over for hours. - Caution + Your first training session starts off very well! You have a captive + audience which seems enraptured by the efficiency embodied in this + thing called "Bugzilla". You are caught up describing the nifty + features, how people can save favorite queries in the database, set + them up as headers and footers on their pages, customize their + layouts, generate reports, track status with greater efficiency than + ever before, leap tall buildings with a single bound and rescue Jane + from the clutches of Certain Death! - If a line in the output from cvs update begins with a C that - represents a file with local changes that CVS was unable to properly - merge. You need to resolve these conflicts manually before Bugzilla - (or at least the portion using that file) will be usable. + But Certain Death speaks up -- a tiny voice, from the dark corners of + the conference room. "I have a concern," the voice hisses from the + darkness, "about the use of the word 'verified'." - Note + The room, previously filled with happy chatter, lapses into + reverential silence as Certain Death (better known as the Vice + President of Software Engineering) continues. "You see, for two years + we've used the word 'verified' to indicate that a developer or quality + assurance engineer has confirmed that, in fact, a bug is valid. I + don't want to lose two years of training to a new software product. + You need to change the bug status of 'verified' to 'approved' as soon + as possible. To avoid confusion, of course." - You also need to run ./checksetup.pl before your Bugzilla upgrade will - be complete. + Oh no! Terror strikes your heart, as you find yourself mumbling "yes, + yes, I don't think that would be a problem," You review the changes + with Certain Death, and continue to jabber on, "no, it's not too big a + change. I mean, we have the source code, right? You know, 'Use the + Source, Luke' and all that... no problem," All the while you quiver + inside like a beached jellyfish bubbling, burbling, and boiling on a + hot Jamaican sand dune... - Example 5-2. Upgrading using the tarball + Thus begins your adventure into the heart of Bugzilla. You've been + forced to learn about non-portable enum() fields, varchar columns, and + tinyint definitions. The Adventure Awaits You! + _________________________________________________________________ - If you are unable or unwilling to use CVS, another option that's - always available is to download the latest tarball. This is the most - difficult option to use, especially if you have local changes. - bash$ cd /var/www/html - bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz - Output omitted - bash$ tar xzvf bugzilla-2.16.2.tar.gz - bugzilla-2.16.2/ - bugzilla-2.16.2/.cvsignore - bugzilla-2.16.2/1x1.gif - Output truncated - bash$ cd bugzilla-2.16.2 - bash$ cp ../bugzilla/localconfig* . - bash$ cp -r ../bugzilla/data . - bash$ cd .. - bash$ mv bugzilla bugzilla.old - bash$ mv bugzilla-2.16.2 bugzilla - bash$ cd bugzilla - bash$ ./checksetup.pl - Output omitted +6.4.1. Bugzilla Database Basics - Warning + If you were like me, at this point you're totally clueless about the + internals of MySQL, and if it weren't for this executive order from + the Vice President you couldn't care less about the difference between + a "bigint" and a "tinyint" entry in MySQL. I recommend you refer to + the MySQL documentation . Below are the basics you need to know about + the Bugzilla database. Check the chart above for more details. - The cp commands both end with periods which is a very important - detail, it tells the shell that the destination directory is the - current working directory. Also, the period at the beginning of the - ./checksetup.pl is important and can not be omitted. + 1. To connect to your database: + bash# mysql -u root + If this works without asking you for a password, shame on you ! + You should have locked your security down like the installation + instructions told you to. You can find details on locking down + your database in the Bugzilla FAQ in this directory (under + "Security"), or more robust security generalities in the MySQL + searchable documentation. + 2. You should now be at a prompt that looks like this: + mysql> + At the prompt, if "bugs" is the name you chose in the localconfig + file for your Bugzilla database, type: + mysql use bugs; + _________________________________________________________________ - Note +6.4.1.1. Bugzilla Database Tables - You will now have to reapply any changes you have made to your local - installation manually. + Imagine your MySQL database as a series of spreadsheets, and you won't + be too far off. If you use this command: - Example 5-3. Upgrading using patches + mysql> show tables from bugs; - The Bugzilla team will normally make a patch file available for - revisions to go from the most recent revision to the new one. You - could also read the release notes and grab the patches attached to the - mentioned bug, but it is safer to use the released patch file as - sometimes patches get changed before they get checked in (for minor - spelling fixes and the like). It is also theorectically possible to - scour the fixed bug list and pick and choose which patches to apply - from a point release, but this is not recommended either as what - you'll end up with is a hodge podge Bugzilla that isn't really any - version. This would also make it more difficult to upgrade in the - future. -bash$ cd /var/www/html/bugzilla -bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz -Output omitted -bash$ gunzip bugzilla-2.16.1-to-2.16.2.diff.gz -bash$ patch -p1 < bugzilla-2.16.1-to-2.16.2.diff -patching file checksetup.pl -patching file collectstats.pl -patching file globals.pl + you'll be able to see the names of all the "spreadsheets" (tables) in + your database. - Caution + From the command issued above, ou should have some output that looks + like this: ++-------------------+ +| Tables in bugs | ++-------------------+ +| attachments | +| bugs | +| bugs_activity | +| cc | +| components | +| dependencies | +| fielddefs | +| groups | +| keyworddefs | +| keywords | +| logincookies | +| longdescs | +| milestones | +| namedqueries | +| products | +| profiles | +| profiles_activity | +| tokens | +| versions | +| votes | +| watch | ++-------------------+ - If you do this, beware that this doesn't change the entires in your - CVS directory so it may make updates using CVS (Example 5-1) more - difficult in the future. + Here's an overview of what each table does. Most columns in each tab + le have + descriptive names that make it fairly trivial to figure out their jobs + . + attachments: This table stores all attachments to bugs. It tends to be + your + largest table, yet also generally has the fewest entries because file + attachments are so (relatively) large. + bugs: This is the core of your system. The bugs table stores most of + the + current information about a bug, with the exception of the info stored + in the + other tables. + bugs_activity: This stores information regarding what changes are mad + e to bugs + when -- a history file. + cc: This tiny table simply stores all the CC information for any bug + which has + any entries in the CC field of the bug. Note that, like most other tab + les in + Bugzilla, it does not refer to users by their user names, but by their + unique + userid, stored as a primary key in the profiles table. + components: This stores the programs and components (or products and + components, in newer Bugzilla parlance) for Bugzilla. Curiously, the " + program" + (product) field is the full name of the product, rather than some othe + r unique + identifier, like bug_id and user_id are elsewhere in the database. + dependencies: Stores data about those cool dependency trees. + fielddefs: A nifty table that defines other tables. For instance, whe + n you + submit a form that changes the value of "AssignedTo" this table allows + translation to the actual field name "assigned_to" for entry into MySQ + L. + groups: defines bitmasks for groups. A bitmask is a number that can u + niquely + identify group memberships. For instance, say the group that is allowe + d to + tweak parameters is assigned a value of "1", the group that is allowed + to edit + users is assigned a "2", and the group that is allowed to create new g + roups is + assigned the bitmask of "4". By uniquely combining the group bitmasks + (much + like the chmod command in UNIX,) you can identify a user is allowed to + tweak + parameters and create groups, but not edit users, by giving him a bitm + ask of + "5", or a user allowed to edit users and create groups, but not tweak + parameters, by giving him a bitmask of "6" Simple, huh? + If this makes no sense to you, try this at the mysql prompt: + mysql> select * from groups; + You'll see the list, it makes much more sense that way. + keyworddefs: Definitions of keywords to be used + keywords: Unlike what you'd think, this table holds which keywords are + associated with which bug id's. + logincookies: This stores every login cookie ever assigned to you for + every + machine you've ever logged into Bugzilla from. Curiously, it never doe + s any + housecleaning -- I see cookies in this file I've not used for months. + However, + since Bugzilla never expires your cookie (for convenience' sake), it m + akes + sense. + longdescs: The meat of bugzilla -- here is where all user comments ar + e stored! + You've only got 2^24 bytes per comment (it's a mediumtext field), so s + peak + sparingly -- that's only the amount of space the Old Testament from th + e Bible + would take (uncompressed, 16 megabytes). Each comment is keyed to the + bug_id to which it's attached, so the order is necessarily chronologic + al, for + comments are played back in the order in which they are received. + milestones: Interesting that milestones are associated with a specifi + c product + in this table, but Bugzilla does not yet support differing milestones + by + product through the standard configuration interfaces. + namedqueries: This is where everybody stores their "custom queries". + Very + cool feature; it beats the tar out of having to bookmark each cool que + ry you + construct. + products: What products you have, whether new bug entries are allowed + for the + product, what milestone you're working toward on that product, votes, + etc. It + will be nice when the components table supports these same features, s + o you + could close a particular component for bug entry without having to clo + se an + entire product... + profiles: Ahh, so you were wondering where your precious user informa + tion was + stored? Here it is! With the passwords in plain text for all to see! + (but + sshh... don't tell your users!) + profiles_activity: Need to know who did what when to who's profile? + This'll + tell you, it's a pretty complete history. + versions: Version information for every product + votes: Who voted for what when + watch: Who (according to userid) is watching who's bugs (according to + their + userid). + === + THE DETAILS + === + Ahh, so you're wondering just what to do with the information above? + At the + mysql prompt, you can view any information about the columns in a tabl + e with + this command (where "table" is the name of the table you wish to view) + : + mysql> show columns from table; + You can also view all the data in a table with this command: + mysql> select * from table; + -- note: this is a very bad idea to do on, for instance, the "bugs" + table if + you have 50,000 bugs. You'll be sitting there a while until you ctrl-c + or + 50,000 bugs play across your screen. + You can limit the display from above a little with the command, wher + e + "column" is the name of the column for which you wish to restrict info + rmation: + mysql> select * from table where (column = "some info"); + -- or the reverse of this + mysql> select * from table where (column != "some info"); + Let's take our example from the introduction, and assume you need to + change + the word "verified" to "approved" in the resolution field. We know fro + m the + above information that the resolution is likely to be stored in the "b + ugs" + table. Note we'll need to change a little perl code as well as this da + tabase + change, but I won't plunge into that in this document. Let's verify th + e + information is stored in the "bugs" table: + mysql> show columns from bugs + (exceedingly long output truncated here) + | bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED + ','VERIFIED','CLOSED')||MUL | UNCONFIRMED|| + Sorry about that long line. We see from this that the "bug status" c + olumn is + an "enum field", which is a MySQL peculiarity where a string type fiel + d can + only have certain types of entries. While I think this is very cool, i + t's not + standard SQL. Anyway, we need to add the possible enum field entry + 'APPROVED' by altering the "bugs" table. + mysql> ALTER table bugs CHANGE bug_status bug_status + -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED", + -> "VERIFIED", "APPROVED", "CLOSED") not null; + (note we can take three lines or more -- whatever you put in befor + e the + semicolon is evaluated as a single expression) + Now if you do this: + mysql> show columns from bugs; + you'll see that the bug_status field has an extra "APPROVED" enum th + at's + available! Cool thing, too, is that this is reflected on your query p + age as + well -- you can query by the new status. But how's it fit into the exi + sting + scheme of things? + Looks like you need to go back and look for instances of the word "v + erified" + in the perl code for Bugzilla -- wherever you find "verified", change + it to + "approved" and you're in business (make sure that's a case-insensitive + search). + Although you can query by the enum field, you can't give something a s + tatus + of "APPROVED" until you make the perl changes. Note that this change I + mentioned can also be done by editing checksetup.pl, which automates a + lot of + this. But you need to know this stuff anyway, right? _________________________________________________________________ -5.10. Integrating Bugzilla with Third-Party Tools +6.5. Integrating Bugzilla with Third-Party Tools -5.10.1. Bonsai +6.5.1. Bonsai Bonsai is a web-based tool for managing CVS, the Concurrent Versioning System . Using Bonsai, administrators can control open/closed status @@ -2985,7 +3096,7 @@ patching file globals.pl Mozilla automated build management system. _________________________________________________________________ -5.10.2. CVS +6.5.2. CVS CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway. @@ -3002,7 +3113,7 @@ patching file globals.pl Check it out at: http://homepages.kcbbs.gen.nz/~tonyg/. _________________________________________________________________ -5.10.3. Perforce SCM +6.5.3. Perforce SCM You can find the project page for Bugzilla and Teamtrack Perforce integration (p4dti) at: http://www.ravenbrook.com/project/p4dti/ . @@ -3018,9 +3129,12 @@ patching file globals.pl for it. Please consult the pages linked above for further information. _________________________________________________________________ -5.10.4. Tinderbox/Tinderbox2 +6.5.4. Tinderbox/Tinderbox2 - We need Tinderbox integration information. + Tinderbox is a continuous-build system which can integrate with + Bugzilla - see http://www.mozilla.org/projects/tinderbox for details + of Tinderbox, and http://tinderbox.mozilla.org/showbuilds.cgi to see + it in action. _________________________________________________________________ Appendix A. The Bugzilla FAQ @@ -3029,232 +3143,199 @@ Appendix A. The Bugzilla FAQ 1. General Questions - A.1.1. Where can I find information about Bugzilla? - A.1.2. What license is Bugzilla distributed under? - A.1.3. How do I get commercial support for Bugzilla? - A.1.4. What major companies or projects are currently using - Bugzilla for bug-tracking? + A.1.1. What license is Bugzilla distributed under? + A.1.2. How do I get commercial support for Bugzilla? + A.1.3. What major companies or projects are currently using + Bugzilla for bug-tracking? - A.1.5. Who maintains Bugzilla? - A.1.6. How does Bugzilla stack up against other bug-tracking - databases? + A.1.4. Who maintains Bugzilla? + A.1.5. How does Bugzilla stack up against other bug-tracking + databases? - A.1.7. Why doesn't Bugzilla offer this or that feature or - compatibility with this other tracking software? + A.1.6. Why doesn't Bugzilla offer this or that feature or + compatibility with this other tracking software? - A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on - Oracle/Sybase/Msql/PostgreSQL/MSSQL. + A.1.7. Why MySQL? I'm interested in seeing Bugzilla run on + Oracle/Sybase/Msql/PostgreSQL/MSSQL. - A.1.9. What is /usr/bonsaitools/bin/perl? - A.1.10. My perl is not located at /usr/bin/perl, is there an easy - way to change it everywhere it needs to be changed? + A.1.8. What is /usr/bonsaitools/bin/perl? + A.1.9. My perl is not located at /usr/bin/perl, is there an easy + way to change it everywhere it needs to be changed? - A.1.11. Is there an easy way to change the Bugzilla cookie name? + A.1.10. Is there an easy way to change the Bugzilla cookie name? 2. Managerial Questions A.2.1. Is Bugzilla web-based, or do you have to have specific - software or a specific operating system on your machine? - - A.2.2. Can Bugzilla integrate with Perforce (SCM software)? - A.2.3. Does Bugzilla allow the user to track multiple projects? - A.2.4. If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to - sort by project, severity etc? - - A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs - etc)? If yes, are there any that are NOT allowed? + software or a specific operating system on your machine? - A.2.6. Does Bugzilla allow us to define our own priorities and + A.2.2. Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and the choice of - acceptable values? + acceptable values? - A.2.7. Does Bugzilla provide any reporting features, metrics, + A.2.3. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management - likes to see. :) + likes to see. :) - A.2.8. Is there email notification and if so, what do you see - when you get an email? + A.2.4. Is there email notification and if so, what do you see + when you get an email? - A.2.9. Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? + A.2.5. Do users have to have any particular type of email + application? - A.2.10. Do users have to have any particular type of email - application? - - A.2.11. Does Bugzilla allow data to be imported and exported? If - I had outsiders write up a bug report using a MS Word bug + A.2.6. Does Bugzilla allow data to be imported and exported? If I + had outsiders write up a bug report using a MS Word bug template, could that template be imported into "matching" fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? - - A.2.12. Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? + export that data to MS Excel, could I do that? - A.2.13. Can a user create and save reports? Can they do this in - Word format? Excel format? + A.2.7. Has anyone converted Bugzilla to another language to be + used in other countries? Is it localizable? - A.2.14. Does Bugzilla have the ability to search by word, phrase, - compound search? + A.2.8. Can a user create and save reports? Can they do this in + Word format? Excel format? - A.2.15. Does Bugzilla provide record locking when there is + A.2.9. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are - they notified? + they notified? - A.2.16. Are there any backup features provided? - A.2.17. Can users be on the system while a backup is in progress? - - A.2.18. What type of human resources are needed to be on staff to + A.2.10. Are there any backup features provided? + A.2.11. Can users be on the system while a backup is in progress? + + A.2.12. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. + buying an "out-of-the-box" solution? - A.2.19. What time frame are we looking at if we decide to hire + A.2.13. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? + for 1 person, 2 people, etc? - A.2.20. Is there any licensing fee or other fees for using + A.2.14. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? + needed as identified above? 3. Bugzilla Security A.3.1. How do I completely disable MySQL security if it's giving me problems (I've followed the instructions in the - installation section of this guide)? + installation section of this guide)? - A.3.2. Are there any security problems with Bugzilla? - A.3.3. I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. + A.3.2. Are there any security problems with Bugzilla? 4. Bugzilla Email A.4.1. I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? + from Bugzilla. How do I stop it entirely for this user? A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? - - A.4.3. I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? + email to anyone but me. How do I do it? - A.4.4. I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? + A.4.3. I want whineatnews.pl to whine at something different to + only new bugs. How do I do it? - A.4.5. How do I set up the email interface to submit/change bugs - via email? + A.4.4. How do I set up the email interface to submit/change bugs + via email? - A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's - extremely slow. What gives? + A.4.5. Email takes FOREVER to reach me from Bugzilla -- it's + extremely slow. What gives? - A.4.7. How come email from Bugzilla changes never reaches me? + A.4.6. How come email from Bugzilla changes never reaches me? 5. Bugzilla Database - A.5.1. I've heard Bugzilla can be used with Oracle? + A.5.1. I've heard Bugzilla can be used with Oracle? A.5.2. I think my database might be corrupted, or contain invalid - entries. What do I do? + entries. What do I do? - A.5.3. I want to manually edit some entries in my database. How? + A.5.3. I want to manually edit some entries in my database. How? A.5.4. I think I've set up MySQL permissions correctly, but - Bugzilla still can't connect. + Bugzilla still can't connect. A.5.5. How do I synchronize bug information among multiple - different Bugzilla databases? + different Bugzilla databases? 6. Bugzilla and Win32 A.6.1. What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? + (Win98+/NT/2K)? - A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32? + A.6.2. Is there a "Bundle::Bugzilla" equivalent for Win32? A.6.3. CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? + Windows NT application" error. Why? A.6.4. I'm having trouble with the perl modules for NT not being - able to talk to to the database. + able to talk to to the database. 7. Bugzilla Usage - A.7.1. How do I change my user name (email address) in Bugzilla? + A.7.1. How do I change my user name (email address) in Bugzilla? A.7.2. The query page is very confusing. Isn't there a simpler - way to query? + way to query? A.7.3. I'm confused by the behavior of the "accept" button in the Show Bug form. Why doesn't it assign the bug to me when I - accept it? + accept it? A.7.4. I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? + Attachment" link. What am I doing wrong? A.7.5. How do I change a keyword in Bugzilla, once some bugs are - using it? + using it? A.7.6. Why can't I close bugs from the "Change Several Bugs at - Once" page? + Once" page? 8. Bugzilla Hacking - A.8.1. What kind of style should I use for templatization? - A.8.2. What bugs are in Bugzilla right now? + A.8.1. What kind of style should I use for templatization? + A.8.2. What bugs are in Bugzilla right now? A.8.3. How can I change the default priority to a null value? For instance, have the default priority be "---" instead of - "P2"? + "P2"? A.8.4. What's the best way to submit patches? What guidelines - should I follow? + should I follow? 1. General Questions - A.1.1. Where can I find information about Bugzilla? - - You can stay up-to-date with the latest Bugzilla information at - http://www.bugzilla.org/. - - A.1.2. What license is Bugzilla distributed under? + A.1.1. What license is Bugzilla distributed under? Bugzilla is covered by the Mozilla Public License. See details at http://www.mozilla.org/MPL/. - A.1.3. How do I get commercial support for Bugzilla? + A.1.2. How do I get commercial support for Bugzilla? http://bugzilla.org/consulting.html is a list of people and companies who have asked us to list them as consultants for Bugzilla. - http://www.collab.net/ offers Bugzilla as part of their standard - offering to large projects. They do have some minimum fees that are - pretty hefty, and generally aren't interested in small projects. - There are several experienced Bugzilla hackers on the mailing list/newsgroup who are willing to make themselves available for generous compensation. Try sending a message to the mailing list asking for a volunteer. - A.1.4. What major companies or projects are currently using Bugzilla + A.1.3. What major companies or projects are currently using Bugzilla for bug-tracking? There are dozens of major companies with public Bugzilla sites to track bugs in their products. We have a fairly complete list available - on our website at http://bugzilla.org/installation_list.html. If you - have an installation of Bugzilla and would like to be added to the - list, whether it's a public install or not, simply e-mail Gerv - <gerv@mozilla.org>. Keep in mind that it's kinda difficult to get onto - the "high-profile" list ;). + on our website at http://bugzilla.org/installation-list/. If you have + an installation of Bugzilla and would like to be added to the list, + whether it's a public install or not, simply e-mail Gerv + <gerv@mozilla.org>. - A.1.5. Who maintains Bugzilla? + A.1.4. Who maintains Bugzilla? A core team, led by Dave Miller (justdave@bugzilla.org). - A.1.6. How does Bugzilla stack up against other bug-tracking + A.1.5. How does Bugzilla stack up against other bug-tracking databases? We can't find any head-to-head comparisons of Bugzilla against other @@ -3270,7 +3351,7 @@ Appendix A. The Bugzilla FAQ forward with a list of advantages your product has over Bugzilla. We'd be happy to include it in the "Competitors" section. - A.1.7. Why doesn't Bugzilla offer this or that feature or + A.1.6. Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software? It may be that the support has not been built yet, or that you have @@ -3285,7 +3366,7 @@ Appendix A. The Bugzilla FAQ Enhancement" (RFE) using the bug submission interface at bugzilla.mozilla.org. - A.1.8. Why MySQL? I'm interested in seeing Bugzilla run on + A.1.7. Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL. MySQL was originally chosen because it is free, easy to install, and @@ -3299,7 +3380,7 @@ Appendix A. The Bugzilla FAQ Once both of these are done, adding support for additional database servers should be trivial. - A.1.9. What is /usr/bonsaitools/bin/perl? + A.1.8. What is /usr/bonsaitools/bin/perl? Bugzilla used to have the path to perl on the shebang line set to /usr/bonsaitools/bin/perl because when Terry first started writing the @@ -3311,56 +3392,26 @@ Appendix A. The Bugzilla FAQ anything else, such as Bonsai, using it and you don't intend to reinstall an older version of Bugzilla). - A.1.10. My perl is not located at /usr/bin/perl, is there an easy way + A.1.9. My perl is not located at /usr/bin/perl, is there an easy way to change it everywhere it needs to be changed? Yes, the following bit of perl magic will change all the shebang lines. Be sure to change /usr/local/bin/perl to your path to the perl binary. - perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl +perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl - A.1.11. Is there an easy way to change the Bugzilla cookie name? + A.1.10. Is there an easy way to change the Bugzilla cookie name? At present, no. 2. Managerial Questions - Note - - Questions likely to be asked by managers. :-) - A.2.1. Is Bugzilla web-based, or do you have to have specific software or a specific operating system on your machine? - It is web and e-mail based. You can edit bugs by sending specially - formatted email to a properly configured Bugzilla, or control via the - web. - - A.2.2. Can Bugzilla integrate with Perforce (SCM software)? + It is web and e-mail based. - Yes! You can find more information elsewhere in "The Bugzilla Guide" - in the "Integration with Third-Party Products" section. - - A.2.3. Does Bugzilla allow the user to track multiple projects? - - Absolutely! You can track any number of Products that can each be - composed of any number of Components. - - A.2.4. If I am on many projects, and search for all bugs assigned to - me, will Bugzilla list them for me and allow me to sort by project, - severity etc? - - Yes. - - A.2.5. Does Bugzilla allow attachments (text, screenshots, URLs etc)? - If yes, are there any that are NOT allowed? - - Yes - any sort of attachment is allowed, although administrators can - configure a maximum size. Bugzilla gives the user the option of either - using the MIME-type supplied by the browser, choosing from a - pre-defined list or manually typing any arbitrary MIME-type. - - A.2.6. Does Bugzilla allow us to define our own priorities and levels? + A.2.2. Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and the choice of acceptable values? @@ -3371,7 +3422,7 @@ Appendix A. The Bugzilla FAQ There is no GUI for adding fields to Bugzilla at this time. You can follow development of this feature in bug 91037 - A.2.7. Does Bugzilla provide any reporting features, metrics, graphs, + A.2.3. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) Yes. Look at http://bugzilla.mozilla.org/report.cgi for samples of @@ -3384,34 +3435,28 @@ Appendix A. The Bugzilla FAQ implications. Even if you give read-only access to the bugs database it will bypass the secure bugs features of Bugzilla. - A.2.8. Is there email notification and if so, what do you see when you + A.2.4. Is there email notification and if so, what do you see when you get an email? Email notification is user-configurable. By default, the bug id and - Summary of the bug report accompany each email notification, along + summary of the bug report accompany each email notification, along with a list of the changes made. - A.2.9. Can email notification be set up to send to multiple people, - some on the To List, CC List, BCC List etc? - - Yes. - - A.2.10. Do users have to have any particular type of email - application? + A.2.5. Do users have to have any particular type of email application? Bugzilla email is sent in plain text, the most compatible mail format on the planet. Note - If you decide to use the bugzilla_email integration features to allow - Bugzilla to record responses to mail with the associated bug, you may - need to caution your users to set their mailer to "respond to messages - in the format in which they were sent". For security reasons Bugzilla - ignores HTML tags in comments, and if a user sends HTML-based email - into Bugzilla the resulting comment looks downright awful. + If you decide to use the bugzilla_email integration features to allow + Bugzilla to record responses to mail with the associated bug, you may + need to caution your users to set their mailer to "respond to messages + in the format in which they were sent". For security reasons Bugzilla + ignores HTML tags in comments, and if a user sends HTML-based email + into Bugzilla the resulting comment looks downright awful. - A.2.11. Does Bugzilla allow data to be imported and exported? If I had + A.2.6. Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be imported into "matching" fields? If I wanted to take the results of a query and export that data to MS Excel, could I do @@ -3420,11 +3465,11 @@ Appendix A. The Bugzilla FAQ Bugzilla can output buglists as HTML (the default), CSV or RDF. The link for CSV can be found at the bottom of the buglist in HTML format. This CSV format can easily be imported into MS Excel or other - spread-sheet applications. + spreadsheet applications. To use the RDF format of the buglist it is necessary to append a &ctype=rdf to the URL. RDF is meant to be machine readable and thus it - is assumed that the URL would be generated progmatically so there is + is assumed that the URL would be generated programatically so there is no user visible link to this format. Currently the only script included with Bugzilla that can import data @@ -3436,8 +3481,8 @@ Appendix A. The Bugzilla FAQ e-mail to import information into Bugzilla, but these scripts are not currently supported and included for educational purposes. - A.2.12. Has anyone converted Bugzilla to another language to be used - in other countries? Is it localizable? + A.2.7. Has anyone converted Bugzilla to another language to be used in + other countries? Is it localizable? Yes. For more information including available translated templates, see http://www.bugzilla.org/download.html#localizations. The admin @@ -3445,42 +3490,36 @@ Appendix A. The Bugzilla FAQ therefore still English only. Also, there may be issues with the charset not being declared. See bug 126226 for more information. - A.2.13. Can a user create and save reports? Can they do this in Word + A.2.8. Can a user create and save reports? Can they do this in Word format? Excel format? Yes. No. Yes (using the CSV format). - A.2.14. Does Bugzilla have the ability to search by word, phrase, - compound search? - - You have no idea. Bugzilla's query interface, particularly with the - advanced Boolean operators, is incredibly versatile. - - A.2.15. Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second person get a - notice that the bug is in use or how are they notified? + A.2.9. Does Bugzilla provide record locking when there is simultaneous + access to the same bug? Does the second person get a notice that the + bug is in use or how are they notified? Bugzilla does not lock records. It provides mid-air collision detection, and offers the offending user a choice of options to deal with the conflict. - A.2.16. Are there any backup features provided? + A.2.10. Are there any backup features provided? MySQL, the database back-end for Bugzilla, allows hot-backup of data. You can find strategies for dealing with backup considerations at http://www.mysql.com/doc/B/a/Backup.html. - A.2.17. Can users be on the system while a backup is in progress? + A.2.11. Can users be on the system while a backup is in progress? Yes. However, commits to the database must wait until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. - A.2.18. What type of human resources are needed to be on staff to + A.2.12. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much - would that cost vs buying an "Out-of-the-Box" solution. + would that cost vs buying an "out-of-the-box" solution? If Bugzilla is set up correctly from the start, continuing maintenance needs are minimal and can be done easily using the web interface. @@ -3490,7 +3529,7 @@ Appendix A. The Bugzilla FAQ available from skilled members of the newsgroup. Simple questions are answered there and then. - A.2.19. What time frame are we looking at if we decide to hire people + A.2.13. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this a multi-week install process, plus a full @@ -3503,7 +3542,7 @@ Appendix A. The Bugzilla FAQ UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. - A.2.20. Is there any licensing fee or other fees for using Bugzilla? + A.2.14. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -3528,13 +3567,6 @@ Appendix A. The Bugzilla FAQ installation, and follow the recommended security guidelines found in The Bugzilla Guide. - A.3.3. I've implemented the security fixes mentioned in Chris Yeh's - security advisory of 5/10/2000 advising not to run MySQL as root, and - am running into problems with MySQL no longer working correctly. - - This is a common problem, related to running out of file descriptors. - Simply add "ulimit -n unlimited" to the script which starts mysqld. - 4. Bugzilla Email A.4.1. I have a user who doesn't want to receive any more email from @@ -3549,49 +3581,37 @@ Appendix A. The Bugzilla FAQ Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>". - A.4.3. I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? + A.4.3. I want whineatnews.pl to whine at something different to only + new bugs. How do I do it? Try Klaas Freitag's excellent patch for "whineatassigned" functionality. You can find it in bug 6679. This patch is against an older version of Bugzilla, so you must apply the diffs manually. - A.4.4. I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? - - You can call bug_email.pl directly from your aliases file, with an - entry like this: - - bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" - - However, this is fairly nasty and subject to problems; you also need - to set up your smrsh (sendmail restricted shell) to allow it. In a - pinch, though, it can work. - - A.4.5. How do I set up the email interface to submit/change bugs via + A.4.4. How do I set up the email interface to submit/change bugs via email? You can find an updated README.mailif file in the contrib/ directory of your Bugzilla distribution that walks you through the setup. - A.4.6. Email takes FOREVER to reach me from Bugzilla -- it's extremely + A.4.5. Email takes FOREVER to reach me from Bugzilla -- it's extremely slow. What gives? + If you are using sendmail, try enabling sendmailnow in editparams.cgi. + If you are using an alternate MTA, make sure the options given in Bugzilla/BugMail.pm and any other place where sendmail is called from are correct for your MTA. You should also ensure that the sendmailnow param is set to on. - If you are using sendmail, try enabling sendmailnow in editparams.cgi. - - A.4.7. How come email from Bugzilla changes never reaches me? + A.4.6. How come email from Bugzilla changes never reaches me? Double-check that you have not turned off email in your user preferences. Confirm that Bugzilla is able to send email by visiting the "Log In" link of your Bugzilla installation and clicking the "Email me a password" button after entering your email address. - If you never receive mail from Bugzilla, chances you do not have + If you never receive mail from Bugzilla, chances are you do not have sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked to, "/usr/lib/sendmail". @@ -3599,26 +3619,26 @@ Appendix A. The Bugzilla FAQ A.5.1. I've heard Bugzilla can be used with Oracle? - Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. Red + Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle, but + it is now so old as to be obsolete, and is totally unsupported. Red Hat's newer version (based on 2.17.1 and soon to be merged into the main distribution) runs on PostgreSQL. At this time we know of no - recent ports of Bugzilla to Oracle but do intend to support it in the - future (possibly the 2.20 time-frame). + recent ports of Bugzilla to Oracle; to be honest, Bugzilla doesn't + need what Oracle offers. A.5.2. I think my database might be corrupted, or contain invalid entries. What do I do? - Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home - directory) from your web browser to see! If it finishes without - errors, you're probably OK. If it doesn't come back OK (i.e. any red - letters), there are certain things Bugzilla can recover from and - certain things it can't. If it can't auto-recover, I hope you're - familiar with mysqladmin commands or have installed another way to - manage your database. Sanity Check, although it is a good basic check - on your database integrity, by no means is a substitute for competent - database administration and avoiding deletion of data. It is not - exhaustive, and was created to do a basic check for the most common - problems in Bugzilla databases. + Run the "sanity check" utility (sanitycheck.cgi) from your web browser + to see! If it finishes without errors, you're probably OK. If it + doesn't come back OK (i.e. any red letters), there are certain things + Bugzilla can recover from and certain things it can't. If it can't + auto-recover, I hope you're familiar with mysqladmin commands or have + installed another way to manage your database. Sanity Check, although + it is a good basic check on your database integrity, by no means is a + substitute for competent database administration and avoiding deletion + of data. It is not exhaustive, and was created to do a basic check for + the most common problems in Bugzilla databases. A.5.3. I want to manually edit some entries in my database. How? @@ -3641,9 +3661,9 @@ Appendix A. The Bugzilla FAQ Warning - Running MySQL with this command line option is very insecure and - should only be done when not connected to the external network as a - troubleshooting step. + Running MySQL with this command line option is very insecure and + should only be done when not connected to the external network as a + troubleshooting step. A.5.5. How do I synchronize bug information among multiple different Bugzilla databases? @@ -3772,18 +3792,18 @@ Appendix A. The Bugzilla FAQ Gerv and Myk suggest a 2-space indent, with embedded code sections on their own line, in line with outer tags. Like this: - <fred> - [% IF foo %] - <bar> - [% FOREACH x = barney %] - <tr> - <td> - [% x %] - </td> - <tr> - [% END %] - [% END %] - </fred> +<fred> +[% IF foo %] + <bar> + [% FOREACH x = barney %] + <tr> + <td> + [% x %] + </td> + <tr> + [% END %] +[% END %] +</fred> Myk also recommends you turn on PRE_CHOMP in the template initialization to prevent bloating of HTML with unnecessary @@ -3836,364 +3856,15 @@ Appendix A. The Bugzilla FAQ successful open-source bug-tracking software on the planet :) _________________________________________________________________ -Appendix B. The Bugzilla Database +Appendix B. Contrib - Note - - This document really needs to be updated with more fleshed out - information about primary keys, interrelationships, and maybe some - nifty tables to document dependencies. Any takers? + There are a number of unofficial Bugzilla add-ons in the + $BUGZILLA_ROOT/contrib/ directory. This section documents them. _________________________________________________________________ -B.1. Modifying Your Running System - - Bugzilla optimizes database lookups by storing all relatively static - information in the versioncache file, located in the data/ - subdirectory under your installation directory. - - If you make a change to the structural data in your database (the - versions table for example), or to the "constants" encoded in - defparams.pl, you will need to remove the cached content from the data - directory (by doing a "rm data/versioncache" ), or your changes won't - show up. - - versioncache gets automatically regenerated whenever it's more than an - hour old, so Bugzilla will eventually notice your changes by itself, - but generally you want it to notice right away, so that you can test - things. - _________________________________________________________________ - -B.2. MySQL Bugzilla Database Introduction - - This information comes straight from my life. I was forced to learn - how Bugzilla organizes database because of nitpicky requests from - users for tiny changes in wording, rather than having people - re-educate themselves or figure out how to work our procedures around - the tool. It sucks, but it can and will happen to you, so learn how - the schema works and deal with it when it comes. - - So, here you are with your brand-new installation of Bugzilla. You've - got MySQL set up, Apache working right, Perl DBI and DBD talking to - the database flawlessly. Maybe you've even entered a few test bugs to - make sure email's working; people seem to be notified of new bugs and - changes, and you can enter and edit bugs to your heart's content. - Perhaps you've gone through the trouble of setting up a gateway for - people to submit bugs to your database via email, have had a few - people test it, and received rave reviews from your beta testers. +B.1. Command-line Search Interface - What's the next thing you do? Outline a training strategy for your - development team, of course, and bring them up to speed on the new - tool you've labored over for hours. - - Your first training session starts off very well! You have a captive - audience which seems enraptured by the efficiency embodied in this - thing called "Bugzilla". You are caught up describing the nifty - features, how people can save favorite queries in the database, set - them up as headers and footers on their pages, customize their - layouts, generate reports, track status with greater efficiency than - ever before, leap tall buildings with a single bound and rescue Jane - from the clutches of Certain Death! - - But Certain Death speaks up -- a tiny voice, from the dark corners of - the conference room. "I have a concern," the voice hisses from the - darkness, "about the use of the word 'verified'." - - The room, previously filled with happy chatter, lapses into - reverential silence as Certain Death (better known as the Vice - President of Software Engineering) continues. "You see, for two years - we've used the word 'verified' to indicate that a developer or quality - assurance engineer has confirmed that, in fact, a bug is valid. I - don't want to lose two years of training to a new software product. - You need to change the bug status of 'verified' to 'approved' as soon - as possible. To avoid confusion, of course." - - Oh no! Terror strikes your heart, as you find yourself mumbling "yes, - yes, I don't think that would be a problem," You review the changes - with Certain Death, and continue to jabber on, "no, it's not too big a - change. I mean, we have the source code, right? You know, 'Use the - Source, Luke' and all that... no problem," All the while you quiver - inside like a beached jellyfish bubbling, burbling, and boiling on a - hot Jamaican sand dune... - - Thus begins your adventure into the heart of Bugzilla. You've been - forced to learn about non-portable enum() fields, varchar columns, and - tinyint definitions. The Adventure Awaits You! - _________________________________________________________________ - -B.2.1. Bugzilla Database Basics - - If you were like me, at this point you're totally clueless about the - internals of MySQL, and if it weren't for this executive order from - the Vice President you couldn't care less about the difference between - a "bigint" and a "tinyint" entry in MySQL. I recommend you refer to - the MySQL documentation . Below are the basics you need to know about - the Bugzilla database. Check the chart above for more details. - - 1. To connect to your database: - bash# mysql -u root - If this works without asking you for a password, shame on you ! - You should have locked your security down like the installation - instructions told you to. You can find details on locking down - your database in the Bugzilla FAQ in this directory (under - "Security"), or more robust security generalities in the MySQL - searchable documentation. - 2. You should now be at a prompt that looks like this: - mysql> - At the prompt, if "bugs" is the name you chose in the localconfig - file for your Bugzilla database, type: - mysql use bugs; - _________________________________________________________________ - -B.2.1.1. Bugzilla Database Tables - - Imagine your MySQL database as a series of spreadsheets, and you won't - be too far off. If you use this command: - - mysql> show tables from bugs; - - you'll be able to see the names of all the "spreadsheets" (tables) in - your database. - - From the command issued above, ou should have some output that looks - like this: - +-------------------+ - | Tables in bugs | - +-------------------+ - | attachments | - | bugs | - | bugs_activity | - | cc | - | components | - | dependencies | - | fielddefs | - | groups | - | keyworddefs | - | keywords | - | logincookies | - | longdescs | - | milestones | - | namedqueries | - | products | - | profiles | - | profiles_activity | - | tokens | - | versions | - | votes | - | watch | - +-------------------+ - - Here's an overview of what each table does. Most columns in each tab - le have - descriptive names that make it fairly trivial to figure out their jobs - . - attachments: This table stores all attachments to bugs. It tends to be - your - largest table, yet also generally has the fewest entries because file - attachments are so (relatively) large. - bugs: This is the core of your system. The bugs table stores most of - the - current information about a bug, with the exception of the info stored - in the - other tables. - bugs_activity: This stores information regarding what changes are mad - e to bugs - when -- a history file. - cc: This tiny table simply stores all the CC information for any bug - which has - any entries in the CC field of the bug. Note that, like most other tab - les in - Bugzilla, it does not refer to users by their user names, but by their - unique - userid, stored as a primary key in the profiles table. - components: This stores the programs and components (or products and - components, in newer Bugzilla parlance) for Bugzilla. Curiously, the " - program" - (product) field is the full name of the product, rather than some othe - r unique - identifier, like bug_id and user_id are elsewhere in the database. - dependencies: Stores data about those cool dependency trees. - fielddefs: A nifty table that defines other tables. For instance, whe - n you - submit a form that changes the value of "AssignedTo" this table allows - translation to the actual field name "assigned_to" for entry into MySQ - L. - groups: defines bitmasks for groups. A bitmask is a number that can u - niquely - identify group memberships. For instance, say the group that is allowe - d to - tweak parameters is assigned a value of "1", the group that is allowed - to edit - users is assigned a "2", and the group that is allowed to create new g - roups is - assigned the bitmask of "4". By uniquely combining the group bitmasks - (much - like the chmod command in UNIX,) you can identify a user is allowed to - tweak - parameters and create groups, but not edit users, by giving him a bitm - ask of - "5", or a user allowed to edit users and create groups, but not tweak - parameters, by giving him a bitmask of "6" Simple, huh? - If this makes no sense to you, try this at the mysql prompt: - mysql> select * from groups; - You'll see the list, it makes much more sense that way. - keyworddefs: Definitions of keywords to be used - keywords: Unlike what you'd think, this table holds which keywords are - associated with which bug id's. - logincookies: This stores every login cookie ever assigned to you for - every - machine you've ever logged into Bugzilla from. Curiously, it never doe - s any - housecleaning -- I see cookies in this file I've not used for months. - However, - since Bugzilla never expires your cookie (for convenience' sake), it m - akes - sense. - longdescs: The meat of bugzilla -- here is where all user comments ar - e stored! - You've only got 2^24 bytes per comment (it's a mediumtext field), so s - peak - sparingly -- that's only the amount of space the Old Testament from th - e Bible - would take (uncompressed, 16 megabytes). Each comment is keyed to the - bug_id to which it's attached, so the order is necessarily chronologic - al, for - comments are played back in the order in which they are received. - milestones: Interesting that milestones are associated with a specifi - c product - in this table, but Bugzilla does not yet support differing milestones - by - product through the standard configuration interfaces. - namedqueries: This is where everybody stores their "custom queries". - Very - cool feature; it beats the tar out of having to bookmark each cool que - ry you - construct. - products: What products you have, whether new bug entries are allowed - for the - product, what milestone you're working toward on that product, votes, - etc. It - will be nice when the components table supports these same features, s - o you - could close a particular component for bug entry without having to clo - se an - entire product... - profiles: Ahh, so you were wondering where your precious user informa - tion was - stored? Here it is! With the passwords in plain text for all to see! - (but - sshh... don't tell your users!) - profiles_activity: Need to know who did what when to who's profile? - This'll - tell you, it's a pretty complete history. - versions: Version information for every product - votes: Who voted for what when - watch: Who (according to userid) is watching who's bugs (according to - their - userid). - === - THE DETAILS - === - Ahh, so you're wondering just what to do with the information above? - At the - mysql prompt, you can view any information about the columns in a tabl - e with - this command (where "table" is the name of the table you wish to view) - : - mysql> show columns from table; - You can also view all the data in a table with this command: - mysql> select * from table; - -- note: this is a very bad idea to do on, for instance, the "bugs" - table if - you have 50,000 bugs. You'll be sitting there a while until you ctrl-c - or - 50,000 bugs play across your screen. - You can limit the display from above a little with the command, wher - e - "column" is the name of the column for which you wish to restrict info - rmation: - mysql> select * from table where (column = "some info"); - -- or the reverse of this - mysql> select * from table where (column != "some info"); - Let's take our example from the introduction, and assume you need to - change - the word "verified" to "approved" in the resolution field. We know fro - m the - above information that the resolution is likely to be stored in the "b - ugs" - table. Note we'll need to change a little perl code as well as this da - tabase - change, but I won't plunge into that in this document. Let's verify th - e - information is stored in the "bugs" table: - mysql> show columns from bugs - (exceedingly long output truncated here) - | bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED - ','VERIFIED','CLOSED')||MUL | UNCONFIRMED|| - Sorry about that long line. We see from this that the "bug status" c - olumn is - an "enum field", which is a MySQL peculiarity where a string type fiel - d can - only have certain types of entries. While I think this is very cool, i - t's not - standard SQL. Anyway, we need to add the possible enum field entry - 'APPROVED' by altering the "bugs" table. - mysql> ALTER table bugs CHANGE bug_status bug_status - -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED", - -> "VERIFIED", "APPROVED", "CLOSED") not null; - (note we can take three lines or more -- whatever you put in befor - e the - semicolon is evaluated as a single expression) - Now if you do this: - mysql> show columns from bugs; - you'll see that the bug_status field has an extra "APPROVED" enum th - at's - available! Cool thing, too, is that this is reflected on your query p - age as - well -- you can query by the new status. But how's it fit into the exi - sting - scheme of things? - Looks like you need to go back and look for instances of the word "v - erified" - in the perl code for Bugzilla -- wherever you find "verified", change - it to - "approved" and you're in business (make sure that's a case-insensitive - search). - Although you can query by the enum field, you can't give something a s - tatus - of "APPROVED" until you make the perl changes. Note that this change I - mentioned can also be done by editing checksetup.pl, which automates a - lot of - this. But you need to know this stuff anyway, right? - _________________________________________________________________ - -Appendix C. Useful Patches and Utilities for Bugzilla - - Are you looking for a way to put your Bugzilla into overdrive? Catch - some of the niftiest tricks here in this section. - _________________________________________________________________ - -C.1. Apache mod_rewrite magic - - Apache's mod_rewrite module lets you do some truly amazing things with - URL rewriting. Here are a couple of examples of what you can do. - - 1. Make it so if someone types http://www.foo.com/12345 , Bugzilla - spits back http://www.foo.com/show_bug.cgi?id=12345. Try setting - up your VirtualHost section for Bugzilla with a rule like this: - - <VirtualHost 12.34.56.78> - RewriteEngine On - RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] - </VirtualHost> - - 2. There are many, many more things you can do with mod_rewrite. - Please refer to the mod_rewrite documentation at - http://www.apache.org. - _________________________________________________________________ - -C.2. Command-line Bugzilla Queries - - There are a suite of Unix utilities for querying Bugzilla from the + There are a suite of Unix utilities for searching Bugzilla from the command line. They live in the contrib/cmdline directory. However, they have not yet been updated to work with 2.16 (post-templatisation.). There are three files - query.conf, buglist @@ -4226,82 +3897,7 @@ C.2. Command-line Bugzilla Queries w3m -T text/html -dump _________________________________________________________________ -Appendix D. Bugzilla Variants and Competitors - - I created this section to answer questions about Bugzilla competitors - and variants, then found a wonderful site which covers an awful lot of - what I wanted to discuss. Rather than quote it in its entirety, I'll - simply refer you here: http://linas.org/linux/pm.html. - _________________________________________________________________ - -D.1. Red Hat Bugzilla - - Red Hat's old fork of Bugzilla which was based on version 2.8 is now - obsolete. The newest version in use is based on version 2.17.1 and is - in the process of being integrated into the main Bugzilla source tree. - The back-end is modified to work with PostgreSQL instead of MySQL and - they have custom templates to get their desired look and feel, but - other than that it is Bugzilla 2.17.1. Dave Lawrence of Red Hat put - forth a great deal of effort to make sure that the changes he made - could be integrated back into the main tree. Bug 98304 exists to track - this integration. - - URL: http://bugzilla.redhat.com/bugzilla/ - - This section last updated 24 Dec 2002 - _________________________________________________________________ - -D.2. Loki Bugzilla (Fenris) - - Fenris was a fork from Bugzilla made by Loki Games; when Loki went - into receivership, it died. While Loki's other code lives on, its - custodians recommend Bugzilla for future bug-tracker deployments. - - This section last updated 27 Jul 2002 - _________________________________________________________________ - -D.3. Issuezilla - - Issuezilla was another fork from Bugzilla, made by collab.net and - hosted at tigris.org. It is also dead; the primary focus of - bug-tracking at tigris.org is their Java-based bug-tracker, Section - D.4. - - This section last updated 27 Jul 2002 - _________________________________________________________________ - -D.4. Scarab - - Scarab is a new open source bug-tracking system built using Java - Servlet technology. It is currently at version 1.0 beta 13. - - URL: http://scarab.tigris.org/ - - This section last updated 18 Jan 2003 - _________________________________________________________________ - -D.5. Perforce SCM - - Although Perforce isn't really a bug tracker, it can be used as such - through the "jobs" functionality. - - URL: http://www.perforce.com/perforce/technotes/note052.html - - This section last updated 27 Jul 2002 - _________________________________________________________________ - -D.6. SourceForge - - SourceForge is a way of coordinating geographically distributed free - software and open source projects over the Internet. It has a built-in - bug tracker, but it's not highly thought of. - - URL: http://www.sourceforge.net - - This section last updated 27 Jul 2002 - _________________________________________________________________ - -Appendix E. GNU Free Documentation License +Appendix C. GNU Free Documentation License Version 1.1, March 2000 @@ -4707,7 +4303,7 @@ A doesn't have to be changed in every Bugzilla script. For more information about how to configure Apache for - Bugzilla, see Section 4.4.1. + Bugzilla, see Section 4.2.1. B @@ -4754,10 +4350,10 @@ C perl, there may be additional modules or other requirements than those of the offical distribution. - Note + Note - Scripts in the contrib directory are not offically supported by the - Bugzilla team and may break in between versions. + Scripts in the contrib directory are not offically supported by the + Bugzilla team and may break in between versions. D @@ -4804,7 +4400,7 @@ M Privilege System Much more detailed information about the suggestions in - Section 5.6.2. + Section 4.5.2. P @@ -4848,7 +4444,7 @@ R S - SGML + SGML SGML stands for "Standard Generalized Markup Language". Created in the 1980's to provide an extensible means to maintain documentation based upon content instead of presentation, SGML @@ -4884,16 +4480,16 @@ Z - I've been asked to explain this ... way back when, when Netscape - released version 4.0 of its browser, we had a release party. - Naturally, there had been a big push to try and fix every known bug - before the release. Naturally, that hadn't actually happened. (This is - not unique to Netscape or to 4.0; the same thing has happened with - every software project I've ever seen.) Anyway, at the release party, - T-shirts were handed out that said something like "Netscape 4.0: Zarro - Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh. - So, when you query for a list of bugs, and it gets no results, you can - think of this as a friendly reminder. Of *course* there are bugs - matching your query, they just aren't in the bugsystem yet... + I've been asked to explain this ... way back when, when Netscape + released version 4.0 of its browser, we had a release party. + Naturally, there had been a big push to try and fix every known bug + before the release. Naturally, that hadn't actually happened. (This is + not unique to Netscape or to 4.0; the same thing has happened with + every software project I've ever seen.) Anyway, at the release party, + T-shirts were handed out that said something like "Netscape 4.0: Zarro + Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh. + So, when you query for a list of bugs, and it gets no results, you can + think of this as a friendly reminder. Of *course* there are bugs + matching your query, they just aren't in the bugsystem yet... - --Terry Weissman + --Terry Weissman diff --git a/docs/xml/Bugzilla-Guide.xml b/docs/xml/Bugzilla-Guide.xml index 5ff9555a4..8fb74a31a 100644 --- a/docs/xml/Bugzilla-Guide.xml +++ b/docs/xml/Bugzilla-Guide.xml @@ -13,7 +13,7 @@ <!ENTITY integration SYSTEM "integration.xml"> <!ENTITY future SYSTEM "future.xml"> <!ENTITY index SYSTEM "index.xml"> -<!ENTITY database SYSTEM "database.xml"> +<!ENTITY customization SYSTEM "customization.xml"> <!ENTITY patches SYSTEM "patches.xml"> <!ENTITY variants SYSTEM "variants.xml"> <!ENTITY introduction SYSTEM "introduction.xml"> @@ -34,11 +34,10 @@ <!ENTITY bz-ver "2.17.5"> <!ENTITY bz-nextver "2.18"> -<!ENTITY bz-date "2003-11-01"> +<!ENTITY bz-date "2004-01-15"> <!ENTITY % bz-devel "INCLUDE"> <!ENTITY bz "http://www.bugzilla.org/"> -<!ENTITY bzg-auth "The Bugzilla Team"> <!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation'>Bugzilla Documentation</ulink>"> <!ENTITY mysql "http://www.mysql.com/"> <!ENTITY newest-perl-ver "5.8"> @@ -70,21 +69,23 @@ <!-- Coding standards for this document -* Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc. +* Other than the GFDL, please use the "section" tag instead of "sect1", + "sect2", etc. * Use Entities to include files for new chapters in Bugzilla-Guide.xml. * Try to use Entities for frequently-used passages of text as well. * Ensure all documents compile cleanly to HTML after modification. -The warning, "DTDDECL catalog types not supported" is normal. + The warning, "DTDDECL catalog types not supported" is normal. * Try to index important terms wherever possible. * Use "glossterm" whenever you introduce a new term. * Follow coding standards at http://www.tldp.org, and -check out the KDE guidelines (they are nice, too) -http://i18n.kde.org/doc/markup.html + check out the KDE guidelines (they are nice, too) + http://i18n.kde.org/doc/markup.html * All tags should be lowercase. * Please use sensible spacing. The comments at the very end of each -file define reasonable defaults for PSGML mode in EMACS. -Double-indent tags, use double spacing whenever possible, and -try to avoid clutter and feel free to waste space in the code to make it more readable. + file define reasonable defaults for PSGML mode in EMACS. +* Double-indent tags, use double spacing whenever possible, and + try to avoid clutter and feel free to waste space in the code to make it + more readable. --> @@ -93,18 +94,10 @@ try to avoid clutter and feel free to waste space in the code to make it more re <!-- Header --> <bookinfo> - <title>The Bugzilla Guide - &bz-ver; <![%bz-devel;[Development ]]>Release</title> + <title>The Bugzilla Guide - &bz-ver; + <![%bz-devel;[Development ]]>Release</title> <authorgroup> - <author> - <firstname>Matthew</firstname> - <othername>P.</othername> - <surname>Barnson</surname> - </author> - <author> - <firstname>Jacob</firstname> - <surname>Steenhagen</surname> - </author> <corpauthor>The Bugzilla Team</corpauthor> </authorgroup> @@ -112,28 +105,17 @@ try to avoid clutter and feel free to waste space in the code to make it more re <abstract> <para> - This is the documentation for Bugzilla, the mozilla.org - bug-tracking system. + This is the documentation for Bugzilla, a + bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software - that powers issue-tracking for hundreds of - organizations around the world, tracking millions of bugs. + that tracks millions of bugs and issues for hundreds of + organizations around the world. </para> - <para> - 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 the &bzg-bugs; component. - </para> - <![%bz-devel;[ - <para>This is a development version of this guide. Information in it - is subject to change before the &bz-nextver; release of this guide - (which will correspond with the &bz-nextver; release of Bugzilla). - </para> - ]]> - <para> The most current version of this document can always be found on the - <ulink url="http://www.bugzilla.org/documentation.html">Bugzilla Documentation Page</ulink>. + <ulink url="http://www.bugzilla.org/documentation.html">Bugzilla + Documentation Page</ulink>. </para> </abstract> @@ -166,18 +148,15 @@ try to avoid clutter and feel free to waste space in the code to make it more re <!-- Administering Bugzilla --> &administration; +<!-- Customizing Bugzilla --> +&customization; + <!-- Appendix: The Frequently Asked Questions --> &faq; -<!-- Appendix: The Database Schema --> -&database; - <!-- Appendix: Custom Patches --> &patches; -<!-- Appendix: Major Bugzilla Variants --> -&variants; - <!-- Appendix: GNU Free Documentation License --> &gfdl; diff --git a/docs/xml/about.xml b/docs/xml/about.xml index 3b0f18e0f..28cc9d8c7 100644 --- a/docs/xml/about.xml +++ b/docs/xml/about.xml @@ -7,7 +7,7 @@ <section id="copyright"> <title>Copyright Information</title> <blockquote> - <attribution>Copyright (c) 2000-2003 Matthew P. Barnson and &bzg-auth;</attribution> + <attribution>Copyright (c) 2000-2004 The Bugzilla Team</attribution> <para> Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation @@ -20,7 +20,7 @@ <para> If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, - please contact &bzg-auth;. + please contact the Bugzilla Team. </para> </section> @@ -28,7 +28,7 @@ <title>Disclaimer</title> <para> No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content at your own risk. + Follow the instructions herein 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 @@ -36,35 +36,20 @@ war. Proceed with caution. </para> <para> - 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. - </para> - <para> 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, + wholeheartedly endorse the use of GNU/Linux; it is an extremely + versatile, stable, and robust operating system that offers an ideal operating environment for Bugzilla. </para> <para> - 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! - </para> - <para> 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 + ensure that all exploitable bugs or options have been + fixed, security holes surely exist. Great care should be taken both in + the installation and usage of this software. The Bugzilla development + team members assume no liability for your use of this software. You have + the source code, and are responsible for auditing it yourself to ensure your security needs are met. </para> </section> @@ -77,24 +62,14 @@ This is the &bz-ver; version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. <![%bz-devel;[ - This version of the guide, like its associated Bugzilla version is a - development version. Information is subject to change between now and - when &bz-nextver; is released. + This version of the guide, like its associated Bugzilla version, is a + development version. ]]> - 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. </para> <para> The newest version of this guide can always be found at <ulink - url="http://www.bugzilla.org"/>; including - documentation for past releases and the current development version. - </para> - <para> - The documentation for the most recent stable release of Bugzilla can also - be found at - <ulink url="http://www.tldp.org">The Linux Documentation Project</ulink>. + url="http://www.bugzilla.org"/>; however, you should read the version + which came with the Bugzilla release you are using. </para> <para> The latest version of this document can always be checked out via CVS. @@ -118,87 +93,33 @@ contribution to the Bugzilla community: </para> - <!-- TODO: This is evil... there has to be a valid way to get this look --> - <variablelist> - <varlistentry> - <term>Matthew P. Barnson <email>mbarnson@sisna.com</email></term> - <listitem> - <para>for the Herculaean task of pulling together the Bugzilla Guide - and shepherding it to 2.14. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Terry Weissman <email>terry@mozilla.org</email></term> - <listitem> - <para>for initially writing Bugzilla and creating the README upon - which the UNIX installation documentation is largely based. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Tara Hernandez <email>tara@tequilarists.org</email></term> - <listitem> - <para>for keeping Bugzilla development going strong after Terry left - mozilla.org and for running landfill. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Dave Lawrence <email>dkl@redhat.com</email></term> - <listitem> - <para>for providing insight into the key differences between Red - Hat's customized Bugzilla, and being largely responsible for - <xref linkend="variant-redhat"/>. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Dawn Endico <email>endico@mozilla.org</email></term> - <listitem> - <para>for being a hacker extraordinaire and putting up with Matthew's - incessant questions and arguments on irc.mozilla.org in #mozwebtools - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Jacob Steenhagen <email>jake@bugzilla.org</email></term> - <listitem> - <para>for taking over documentation during the 2.17 development - period. - </para> - </listitem> - </varlistentry> - - </variablelist> - <para> - Last but not least, all the members of the - <ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"/> - newsgroup. Without your discussions, insight, suggestions, and patches, - this could never have happened. - </para> - <para> - Thanks also go to the following people for significant contributions - to this documentation (in alphabetical order): <simplelist type="inline"> - <member>Andrew Pearson</member> + <member>Matthew P. Barnson</member> + <member>Kevin Brannen</member> + <member>Dawn Endico</member> <member>Ben FrantzDale</member> <member>Eric Hanson</member> + <member>Tara Hernandez</member> + <member>Dave Lawrence</member> + <member>Zach Lipton</member> <member>Gervase Markham</member> + <member>Andrew Pearson</member> <member>Joe Robins</member> - <member>Kevin Brannen</member> - <member>Martin Wulffeld</member> - <member>Ron Teitelbaum</member> <member>Spencer Smith</member> - <member>Zach Liption</member> - </simplelist> - . + <member>Jacob Steenhagen</member> + <member>Ron Teitelbaum</member> + <member>Terry Weissman</member> + <member>Martin Wulffeld</member> + </simplelist>. + </para> + + <para> + Last but not least, all the members of the + <ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"> + netscape.public.mozilla.webtools</ulink> + newsgroup. Without your discussions, insight, suggestions, and patches, + this could never have happened. </para> </section> diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml index 8eb7769a4..b261f4ee2 100644 --- a/docs/xml/administration.xml +++ b/docs/xml/administration.xml @@ -71,7 +71,7 @@ standard type, and Bugzilla does not yet take advantage of features such as transactions which would justify this speed decrease. The Bugzilla team are, however, happy to hear about any experiences with - row level locking and Bugzilla</para> + row level locking and Bugzilla.</para> <para>The <quote>shadowdb</quote> parameter was designed to get around this limitation. While only a @@ -82,7 +82,7 @@ high-traffic Bugzilla databases.</para> <para> - As a guide, mozilla.org began needing + As a guide, on reasonably old hardware, mozilla.org began needing <quote>shadowdb</quote> when they reached around 40,000 Bugzilla users with several hundred Bugzilla bug changes and comments per day.</para> @@ -321,7 +321,7 @@ they attempt to perform these actions, and should explain why the account was disabled. <warning> - <para>Don't disable the administrator account!</para> + <para>Don't disable all the administrator accounts!</para> </warning> <note> @@ -418,178 +418,167 @@ </section> </section> - <section id="programadmin"> - <title>Product, Component, Milestone, and Version Administration</title> + <section id="products"> + <title>Products</title> - <section id="products"> - <title>Products</title> + <para> + <glossterm linkend="gloss-product" baseform="product"> + Products</glossterm> - <para> - <glossterm linkend="gloss-product" baseform="product"> - Products</glossterm> - - 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...)</para> - - <para>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.</para> - - <para>To create a new product:</para> - - <orderedlist> - <listitem> - <para>Select "products" from the footer</para> - - </listitem> - - <listitem> - <para>Select the "Add" link in the bottom right</para> - </listitem> - - <listitem> - <para>Enter the name of the product and a description. The - Description field may contain HTML.</para> - </listitem> - </orderedlist> - - <para>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. - </para> - </section> + 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...)</para> - <section id="components"> - <title>Components</title> - - <para>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.</para> - - <para> - 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 - <emphasis>default assignments</emphasis>; - these can be changed on bug submission, or at any later point in - a bug's life.</para> - - <para>To create a new Component:</para> - - <orderedlist> - <listitem> - <para>Select the "Edit components" link from the "Edit product" - page</para> - </listitem> - - <listitem> - <para>Select the "Add" link in the bottom right.</para> - </listitem> - - <listitem> - <para>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. - </para> - </listitem> - </orderedlist> - </section> + <para>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.</para> - <section id="versions"> - <title>Versions</title> + <para>To create a new product:</para> - <para>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. - </para> + <orderedlist> + <listitem> + <para>Select "products" from the footer</para> + + </listitem> + + <listitem> + <para>Select the "Add" link in the bottom right</para> + </listitem> - <para>To create and edit Versions:</para> + <listitem> + <para>Enter the name of the product and a description. The + Description field may contain HTML.</para> + </listitem> + </orderedlist> - <orderedlist> - <listitem> - <para>From the "Edit product" screen, select "Edit Versions"</para> - </listitem> + <para>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. + </para> + </section> - <listitem> - <para>You will notice that the product already has the default - version "undefined". Click the "Add" link in the bottom right.</para> - </listitem> + <section id="components"> + <title>Components</title> - <listitem> - <para>Enter the name of the Version. This field takes text only. - Then click the "Add" button.</para> - </listitem> + <para>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.</para> - </orderedlist> - </section> + <para> + 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 + <emphasis>default assignments</emphasis>; + these can be changed on bug submission, or at any later point in + a bug's life.</para> + + <para>To create a new Component:</para> - <section id="milestones"> - <title>Milestones</title> + <orderedlist> + <listitem> + <para>Select the "Edit components" link from the "Edit product" + page</para> + </listitem> - <para>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.</para> + <listitem> + <para>Select the "Add" link in the bottom right.</para> + </listitem> - <note> - <para>Milestone options will only appear for a Product if you turned - on the "usetargetmilestone" Param in the "Edit Parameters" screen. + <listitem> + <para>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. </para> - </note> - - <para>To create new Milestones, set Default Milestones, and set - Milestone URL:</para> - - <orderedlist> - <listitem> - <para>Select "Edit milestones" from the "Edit product" page.</para> - </listitem> - - <listitem> - <para>Select "Add" in the bottom right corner. - text</para> - </listitem> - - <listitem> - <para>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".</para> - </listitem> - - <listitem> - <para>From the Edit product screen, you can enter the URL of a - page which gives information about your milestones and what - they mean. </para> + </listitem> + </orderedlist> + </section> - <tip> - <para>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.</para> - </tip> - </listitem> - </orderedlist> - </section> + <section id="versions"> + <title>Versions</title> + + <para>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 earliest version known to have + the bug. + </para> + + <para>To create and edit Versions:</para> + + <orderedlist> + <listitem> + <para>From the "Edit product" screen, select "Edit Versions"</para> + </listitem> + + <listitem> + <para>You will notice that the product already has the default + version "undefined". Click the "Add" link in the bottom right.</para> + </listitem> + + <listitem> + <para>Enter the name of the Version. This field takes text only. + Then click the "Add" button.</para> + </listitem> + + </orderedlist> + </section> + + <section id="milestones"> + <title>Milestones</title> + + <para>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.</para> + + <note> + <para>Milestone options will only appear for a Product if you turned + on the "usetargetmilestone" Param in the "Edit Parameters" screen. + </para> + </note> + + <para>To create new Milestones, set Default Milestones, and set + Milestone URL:</para> + + <orderedlist> + <listitem> + <para>Select "Edit milestones" from the "Edit product" page.</para> + </listitem> + + <listitem> + <para>Select "Add" in the bottom right corner. + text</para> + </listitem> + + <listitem> + <para>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".</para> + </listitem> + + <listitem> + <para>From the Edit product screen, you can enter the URL of a + page which gives information about your milestones and what + they mean. </para> + </listitem> + </orderedlist> </section> <section id="voting"> @@ -723,9 +712,10 @@ place all users who fulfill the Regular Expression into the new group. When you have finished, click <quote>Add</quote>.</para> <warning> - <para>The User Regexp is a perl regexp and, if not anchored, will match - any part of an address. So, if you do not want to grant access - into 'mycompany.com' to 'badperson@mycompany.com.hacker.net', use + <para>If specifying a domain in the regexp, make sure you end + the regexp with a $. Otherwise, when granting access to + "@mycompany\.com", you will allow access to + 'badperson@mycompany.com.cracker.net'. You need to use '@mycompany\.com$' as the regexp.</para> </warning> </listitem> @@ -749,705 +739,6 @@ </para> </section> - - <section id="security"> - <title>Bugzilla Security</title> - - <warning> - <para>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.</para> - </warning> - - <note> - <para>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 &bzg-bugs;. - </para> - </note> - - <warning> - <para>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. - </para> - </warning> - - <section id="security-networking"> - <title>TCP/IP Ports</title> - - <!-- TODO: Make this make sense (TCP/IP) --> - <para>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. - </para> - </section> - - <section id="security-mysql"> - <title>MySQL</title> - - <para>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 <emphasis>not</emphasis> the same as - the system root). Also, many installations default to running - <application>mysqld</application> as the system root. - </para> - - <orderedlist> - <listitem> - <para>Consult the documentation that came with your system for - information on making <application>mysqld</application> run as an - unprivleged user. - </para> - </listitem> - - <listitem> - <para>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: - </para> - <programlisting> -<prompt>bash$</prompt> mysql mysql -<prompt>mysql></prompt> DELETE FROM user WHERE user = ''; -<prompt>mysql></prompt> UPDATE user SET password = password('<replaceable>new_password</replaceable>') WHERE user = 'root'; -<prompt>mysql></prompt> FLUSH PRIVILEGES; - </programlisting> - <para>From this point forward you will need to use - <command>mysql -u root -p</command> and enter - <replaceable>new_password</replaceable> when prompted when using the - mysql client. - </para> - </listitem> - - <listitem> - <para>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 <filename>/etc/my.conf</filename>: - </para> - <programlisting> -[myslqd] -# Prevent network access to MySQL. -skip-networking - </programlisting> - </listitem> - - <listitem> - <para>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. - </para> - </listitem> - - </orderedlist> - - </section> - - <section id="security-daemon"> - <title>Daemon Accounts</title> - - <para>Many daemons, such as Apache's httpd and MySQL's mysqld default to - running as either <quote>root</quote> or <quote>nobody</quote>. Running - as <quote>root</quote> introduces obvious security problems, but the - problems introduced by running everything as <quote>nobody</quote> may - not be so obvious. Basically, if you're running every daemon as - <quote>nobody</quote> 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. - </para> - - <note> - <para>You will need to set the <varname>webservergroup</varname> to - the group you created for your webserver to run as in - <filename>localconfig</filename>. This will allow - <command>./checksetup.pl</command> to better adjust the file - permissions on your Bugzilla install so as to not require making - anything world-writable. - </para> - </note> - - </section> - - <section id="security-access"> - <title>Web Server Access Controls</title> - - <para>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 - <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"> - bug 44659</ulink> for more information. - </para> - - <itemizedlist spacing="compact"> - <listitem> - <para>In the main Bugzilla directory, you should:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block: - <simplelist type="inline"> - <member><filename>*.pl</filename></member> - <member><filename>*localconfig*</filename></member> - <member><filename>runtests.sh</filename></member> - </simplelist> - </para> - </listitem> - <listitem> - <para>But allow: - <simplelist type="inline"> - <member><filename>localconfig.js</filename></member> - <member><filename>localconfig.rdf</filename></member> - </simplelist> - </para> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>In <filename class="directory">data</filename>:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - <listitem> - <para>But allow: - <simplelist type="inline"> - <member><filename>duplicates.rdf</filename></member> - </simplelist> - </para> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>In <filename class="directory">data/webdot</filename>:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>If you use a remote webdot server:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - <listitem> - <para>But allow - <simplelist type="inline"> - <member><filename>*.dot</filename></member> - </simplelist> - only for the remote webdot server</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>Otherwise, if you use a local GraphViz:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - <listitem> - <para>But allow: - <simplelist type="inline"> - <member><filename>*.png</filename></member> - <member><filename>*.gif</filename></member> - <member><filename>*.jpg</filename></member> - <member><filename>*.map</filename></member> - </simplelist> - </para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>And if you don't use any dot:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - </itemizedlist> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>In <filename class="directory">Bugzilla</filename>:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>In <filename class="directory">template</filename>:</para> - <itemizedlist spacing="compact"> - <listitem> - <para>Block everything</para> - </listitem> - </itemizedlist> - </listitem> - </itemizedlist> - - <tip> - <para>Bugzilla ships with the ability to generate - <filename>.htaccess</filename> files instructing - <glossterm linkend="gloss-apache">Apache</glossterm> which files - should and should not be accessible. For more information, see - <xref linkend="http-apache"/>. - </para> - </tip> - - <para>You should test to make sure that the files mentioned above are - not accessible from the Internet, especially your - <filename>localconfig</filename> 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 - <ulink url="http://bugzilla.mozilla.org/localconfig"/>. You should - get a <errorcode>403</errorcode> <errorname>Forbidden</errorname> - error. - </para> - - <caution> - <para>Not following the instructions in this section, including - testing, may result in sensitive information being globally - accessible. - </para> - </caution> - - <tip> - <para>You should check <xref linkend="http"/> to see if instructions - have been included for your web server. You should also compare those - instructions with this list to make sure everything is properly - accounted for. - </para> - </tip> - - </section> - - </section> - - <section id="cust-templates"> - <title>Template Customization</title> - - <para> - One of the large changes for 2.16 was the templatization of the - entire user-facing UI, using the - <ulink url="http://www.template-toolkit.org">Template Toolkit</ulink>. - 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. - </para> - - <para> - Templatization also makes localized versions of Bugzilla possible, - for the first time. As of version <![%bz-devel;[2.17.4 which will soon - become ]]>2.18, it's possible to have Bugzilla's language determined by - the user's browser. More information is available in - <xref linkend="template-http-accept"/>. - </para> - - <section> - <title>What to Edit</title> - <para> - 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, - <filename>template</filename>, which contains a directory for - each installed localization. The default English templates are - therefore in <filename>en</filename>. Underneath that, there - is the <filename>default</filename> directory and optionally the - <filename>custom</filename> directory. The <filename>default</filename> - directory contains all the templates shipped with Bugzilla, whereas - the <filename>custom</filename> directory does not exist at first and - must be created if you want to use it. - </para> - - <para> - The first method of making customizations is to directly edit the - templates in <filename>template/en/default</filename>. 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 - <command>cvs update</command>, any template fixes will get - automagically merged into your modified versions. - </para> - - <para> - If you use this method, your installation will break if CVS conflicts - occur. - </para> - - <para> - The other method is to copy the templates into a mirrored directory - structure under <filename>template/en/custom</filename>. 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. - </para> - - <para> - 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. - </para> - - <note> - <para> - Don't directly edit the compiled templates in - <filename class="directory">data/template/*</filename> - your - changes will be lost when Template Toolkit recompiles them. - </para> - </note> - - <note> - <para>It is recommended that you run <command>./checksetup.pl</command> - after any template edits, especially if you've created a new file in - the <filename class="directory">custom</filename> directory. - </para> - </note> - </section> - - <section> - <title>How To Edit Templates</title> - - <para> - 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 - <ulink url="http://www.template-toolkit.org">Template Toolkit home - page</ulink>. 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. - </para> - - <para> - 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 &lt;. 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <note> - <para> - 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 - <ulink url="http://www.bugzilla.org/developerguide.html">Developers' - Guide</ulink>. - </para> - </note> - </section> - - - <section> - <title>Template Formats</title> - - <para> - 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 <filename>&format=simple</filename> to a buglist.cgi - URL on your Bugzilla installation.) This - mechanism, called template 'formats', is extensible. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - Write your template in whatever markup or text style is appropriate. - </para> - - <para> - You now need to decide what content type you want your template - served as. Open up the <filename>localconfig</filename> file and find the - <filename>$contenttypes</filename> - 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. - </para> - - <para> - Save the template as <filename><stubname>-<formatname>.<contenttypetag>.tmpl</filename>. - Try out the template by calling the CGI as - <filename><cginame>.cgi?format=<formatname></filename> . - </para> - </section> - - - <section> - <title>Particular Templates</title> - - <para> - There are a few templates you may be particularly interested in - customizing for your installation. - </para> - - <para> - <command>index.html.tmpl</command>: - This is the Bugzilla front page. - </para> - - <para> - <command>global/header.html.tmpl</command>: - 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. - </para> - - <para> - <command>global/banner.html.tmpl</command>: - 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 customize 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. - </para> - - <para> - <command>global/footer.html.tmpl</command>: - 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. - </para> - - <para> - <command>bug/create/user-message.html.tmpl</command>: - 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. - </para> - - <para> - <command>bug/process/midair.html.tmpl</command>: - This is the page used if two people submit simultaneous changes to the - same bug. The second person to submit their changes will get this page - to tell them what the first person did, and ask if they wish to - overwrite those changes or go back and revisit the bug. The default - title and header on this page read "Mid-air collision detected!" If - you work in the aviation industry, or other environment where this - might be found offensive (yes, we have true stories of this happening) - you'll want to change this to something more appropriate for your - environment. - </para> - - <para> - <command>bug/create/create.html.tmpl</command> and - <command>bug/create/comment.txt.tmpl</command>: - 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 - <ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided">guided - bug submission form</ulink>. - </para> - - <para> - To make this work, create a custom template for - <filename>enter_bug.cgi</filename> (the default template, on which you - could base it, is <filename>create.html.tmpl</filename>), - and either call it <filename>create.html.tmpl</filename> or use a format and - call it <filename>create-<formatname>.html.tmpl</filename>. - Put it in the <filename class="directory">custom/bug/create</filename> - 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. - </para> - - <para> - Then, create a template like - <filename>custom/bug/create/comment.txt.tmpl</filename>, 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. - </para> - - <para> - For example, if your enter_bug template had a field - <programlisting><input type="text" name="buildid" size="30"></programlisting> - and then your comment.txt.tmpl had - <programlisting>BuildID: [% form.buildid %]</programlisting> - then - <programlisting>BuildID: 20020303</programlisting> - would appear in the initial checkin comment. - </para> - </section> - - - <section id="template-http-accept"> - <title>Configuring Bugzilla to Detect the User's Language</title> - - <para>Begining in version 2.18<![%bz-devel;[ (first introduced in version - 2.17.4)]]>, it's now possible to have the users web browser tell Bugzilla - which language templates to use for each visitor (using the HTTP_ACCEPT - header). For this to work, Bugzilla needs to have the correct language - templates installed for the version of Bugzilla you are using. Many - language templates can be obtained from <ulink - url="http://www.bugzilla.org/download.html#localizations"/>. Instructions - for submitting new languages are also available from that location. - </para> - - <para>After untarring the localizations (or creating your own) in the - <filename class="directory">[Bugzilla_Root]/template</filename> directory, - you must update the <option>languages</option> parameter to contain any - localizations you'd like to permit. You may also wish to set the - <option>defaultlanguage</option> parameter to something other than - <quote>en</quote> if you don't want Engish to be the default language. - </para> - </section> - - </section> - - <section id="cust-change-permissions"> - <title>Change Permission Customization</title> - - <warning> - <para> - This feature should be considered experimental; the Bugzilla code you - will be changing is not stable, and could change or move between - versions. Be aware that if you make modifications to it, you may have - to re-make them or port them if Bugzilla changes internally between - versions. - </para> - </warning> - - <para> - Companies often have rules about which employees, or classes of employees, - are allowed to change certain things in the bug system. For example, - only the bug's designated QA Contact may be allowed to VERIFY the bug. - Bugzilla has been - designed to make it easy for you to write your own custom rules to define - who is allowed to make what sorts of value transition. - </para> - - <para> - For maximum flexibility, customizing this means editing Bugzilla's Perl - code. This gives the administrator complete control over exactly who is - allowed to do what. The relevant function is called - <filename>CheckCanChangeField()</filename>, - and is found in <filename>process_bug.cgi</filename> in your - Bugzilla directory. If you open that file and grep for - "sub CheckCanChangeField", you'll find it. - </para> - - <para> - This function has been carefully commented to allow you to see exactly - how it works, and give you an idea of how to make changes to it. Certain - marked sections should not be changed - these are the "plumbing" which - makes the rest of the function work. In between those sections, you'll - find snippets of code like: - <programlisting> # Allow the owner to change anything. - if ($ownerid eq $whoid) { - return 1; - }</programlisting> - It's fairly obvious what this piece of code does. - </para> - - <para> - So, how does one go about changing this function? Well, simple changes - can be made just be removing pieces - for example, if you wanted to - prevent any user adding a comment to a bug, just remove the lines marked - "Allow anyone to change comments." And if you want the reporter to have - no special rights on bugs they have filed, just remove the entire section - which refers to him. - </para> - - <para> - More complex customizations are not much harder. Basically, you add - a check in the right place in the function, i.e. after all the variables - you are using have been set up. So, don't look at $ownerid before - $ownerid has been obtained from the database. You can either add a - positive check, which returns 1 (allow) if certain conditions are true, - or a negative check, which returns 0 (deny.) E.g.: - <programlisting> if ($field eq "qacontact") { - if (Bugzilla->user->groups("quality_assurance")) { - return 1; - } - else { - return 0; - } - }</programlisting> - This says that only users in the group "quality_assurance" can change - the QA Contact field of a bug. Getting more weird: - <programlisting> if (($field eq "priority") && - (Bugzilla->user->email =~ /.*\@example\.com$/)) - { - if ($oldvalue eq "P1") { - return 1; - } - else { - return 0; - } - }</programlisting> - This says that if the user is trying to change the priority field, - and their email address is @example.com, they can only do so if the - old value of the field was "P1". Not very useful, but illustrative. - </para> - - <para> - For a list of possible field names, look in - <filename>data/versioncache</filename> for the list called - <filename>@::log_columns</filename>. If you need help writing custom - rules for your organization, ask in the newsgroup. - </para> - </section> - <section id="upgrading"> <title>Upgrading to New Releases</title> @@ -1619,8 +910,8 @@ bash$ <command>./checksetup.pl</command> revisions to go from the most recent revision to the new one. You could also read the release notes and grab the patches attached to the mentioned bug, but it is safer to use the released patch file as - sometimes patches get changed before they get checked in (for minor - spelling fixes and the like). It is also theorectically possible to + sometimes patches get changed before they get checked in. + It is also theoretically possible to scour the fixed bug list and pick and choose which patches to apply from a point release, but this is not recommended either as what you'll end up with is a hodge podge Bugzilla that isn't really any version. @@ -1650,10 +941,6 @@ patching file globals.pl </example> </section> - - <!-- Integrating Bugzilla with Third-Party Tools --> - &integration; - </chapter> <!-- Keep this comment at the end of the file diff --git a/docs/xml/conventions.xml b/docs/xml/conventions.xml index 7e9eb5b04..5f3bcb35d 100644 --- a/docs/xml/conventions.xml +++ b/docs/xml/conventions.xml @@ -60,7 +60,7 @@ </row> <row> - <entry>File Names</entry> + <entry>File and directory names</entry> <entry> <filename>filename</filename> @@ -68,14 +68,6 @@ </row> <row> - <entry>Directory Names</entry> - - <entry> - <filename class="directory">directory</filename> - </entry> - </row> - - <row> <entry>Commands to be typed</entry> <entry> @@ -84,7 +76,7 @@ </row> <row> - <entry>Applications Names</entry> + <entry>Applications names</entry> <entry> <application>application</application> @@ -119,7 +111,7 @@ </row> <row> - <entry>Environment Variables</entry> + <entry>Environment variables</entry> <entry> <envar>VARIABLE</envar> @@ -127,14 +119,6 @@ </row> <row> - <entry>Emphasized word</entry> - - <entry> - <emphasis>word</emphasis> - </entry> - </row> - - <row> <entry>Term found in the glossary</entry> <entry> @@ -143,7 +127,7 @@ </row> <row> - <entry>Code Example</entry> + <entry>Code example</entry> <entry> <programlisting><sgmltag class="starttag">para</sgmltag> @@ -154,6 +138,13 @@ Beginning and end of paragraph </tbody> </tgroup> </informaltable> + + <para> + 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 the &bzg-bugs; component. + </para> + </section> <!-- Keep this comment at the end of the file diff --git a/docs/xml/customization.xml b/docs/xml/customization.xml new file mode 100644 index 000000000..2e3306f88 --- /dev/null +++ b/docs/xml/customization.xml @@ -0,0 +1,787 @@ +<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> +<chapter id="customization"> + <title>Customising Bugzilla</title> + + <section id="cust-templates"> + <title>Template Customization</title> + + <para> + Administrators can 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. + </para> + + <para> + Templatization also makes localized versions of Bugzilla possible, + for the first time. It's possible to have Bugzilla's UI language + determined by the user's browser. More information is available in + <xref linkend="template-http-accept"/>. + </para> + + <section> + <title>What to Edit</title> + <para> + The template directory structure is that there's a top level directory, + <filename>template</filename>, which contains a directory for + each installed localization. The default English templates are + therefore in <filename>en</filename>. Underneath that, there + is the <filename>default</filename> directory and optionally the + <filename>custom</filename> directory. The <filename>default</filename> + directory contains all the templates shipped with Bugzilla, whereas + the <filename>custom</filename> directory does not exist at first and + must be created if you want to use it. + </para> + + <para> + There are two different ways of editing Bugzilla's templates, + and which you use depends mainly on the method you plan to use to + upgrade Bugzilla. + The first method of making customizations is to directly edit the + templates in <filename>template/en/default</filename>. 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 + <command>cvs update</command>, any template fixes will get + automagically merged into your modified versions. + </para> + + <para> + If you use this method, your installation will break if CVS conflicts + occur. + </para> + + <para> + The other method is to copy the templates to be modified into a + mirrored directory + structure under <filename>template/en/custom</filename>. 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. + </para> + + <para> + 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. + </para> + + <note> + <para> + Don't directly edit the compiled templates in + <filename class="directory">data/template/*</filename> - your + changes will be lost when Template Toolkit recompiles them. + </para> + </note> + + <note> + <para>It is recommended that you run <command>./checksetup.pl</command> + after any template edits, especially if you've created a new file in + the <filename class="directory">custom</filename> directory. + </para> + </note> + </section> + + <section> + <title>How To Edit Templates</title> + + <note> + <para> + 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 + <ulink url="http://www.bugzilla.org/developerguide.html">Developers' + Guide</ulink>. + </para> + </note> + + <para> + 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 + <ulink url="http://www.template-toolkit.org">Template Toolkit home + page</ulink>. + </para> + + <para> + 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 &lt;. You use the 'html' filter in the + Template Toolkit to do this. If you forget, you may open up + your installation to cross-site scripting attacks. + </para> + + <para> + 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. + </para> + + <para> + 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. + </para> + + </section> + + + <section> + <title>Template Formats</title> + + <para> + 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 <filename>&format=simple</filename> to a buglist.cgi + URL on your Bugzilla installation.) This + mechanism, called template 'formats', is extensible. + </para> + + <para> + To see if a CGI supports multiple output formats, grep the + CGI for "GetFormat". If it's not present, adding + multiple format support isn't too hard - see how it's done in + other CGIs, e.g. config.cgi. + </para> + + <para> + 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. + </para> + + <para> + Write your template in whatever markup or text style is appropriate. + </para> + + <para> + You now need to decide what content type you want your template + served as. Open up the <filename>localconfig</filename> file and find the + <filename>$contenttypes</filename> + 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. + </para> + + <para> + Save the template as <filename><stubname>-<formatname>.<contenttypetag>.tmpl</filename>. + Try out the template by calling the CGI as + <filename><cginame>.cgi?format=<formatname></filename> . + </para> + </section> + + + <section> + <title>Particular Templates</title> + + <para> + There are a few templates you may be particularly interested in + customizing for your installation. + </para> + + <para> + <command>index.html.tmpl</command>: + This is the Bugzilla front page. + </para> + + <para> + <command>global/header.html.tmpl</command>: + 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. + </para> + + <para> + <command>global/banner.html.tmpl</command>: + 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 customize 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. + </para> + + <para> + <command>global/footer.html.tmpl</command>: + 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. + </para> + + <para> + <command>bug/create/user-message.html.tmpl</command>: + 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. + </para> + + <para> + <command>bug/create/create.html.tmpl</command> and + <command>bug/create/comment.txt.tmpl</command>: + 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 + <ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided">guided + bug submission form</ulink>. + </para> + + <para> + To make this work, create a custom template for + <filename>enter_bug.cgi</filename> (the default template, on which you + could base it, is <filename>create.html.tmpl</filename>), + and either call it <filename>create.html.tmpl</filename> or use a format and + call it <filename>create-<formatname>.html.tmpl</filename>. + Put it in the <filename class="directory">custom/bug/create</filename> + 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. + </para> + + <para> + Then, create a template like + <filename>custom/bug/create/comment.txt.tmpl</filename>, 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. + </para> + + <para> + For example, if your enter_bug template had a field + <programlisting><input type="text" name="buildid" size="30"></programlisting> + and then your comment.txt.tmpl had + <programlisting>BuildID: [% form.buildid %]</programlisting> + then + <programlisting>BuildID: 20020303</programlisting> + would appear in the initial checkin comment. + </para> + </section> + + + <section id="template-http-accept"> + <title>Configuring Bugzilla to Detect the User's Language</title> + + <para>Bugzilla honours the user's Accept: HTTP header. You can install + templates in other languages, and Bugzilla will pick the most appropriate + according to a priority order defined by you. Many + language templates can be obtained from <ulink + url="http://www.bugzilla.org/download.html#localizations"/>. Instructions + for submitting new languages are also available from that location. + </para> + + <para>After untarring the localizations (or creating your own) in the + <filename class="directory">$BUGZILLA_HOME/template</filename> directory, + you must update the <option>languages</option> parameter to contain any + localizations you'd like to permit. You may also wish to set the + <option>defaultlanguage</option> parameter to something other than + <quote>en</quote> if you don't want Engish to be the default language. + </para> + </section> + + </section> + + <section id="cust-change-permissions"> + <title>Customizing Who Can Change What</title> + + <warning> + <para> + This feature should be considered experimental; the Bugzilla code you + will be changing is not stable, and could change or move between + versions. Be aware that if you make modifications as outlined here, + you may have + to re-make them or port them if Bugzilla changes internally between + versions, and you upgrade. + </para> + </warning> + + <para> + Companies often have rules about which employees, or classes of employees, + are allowed to change certain things in the bug system. For example, + only the bug's designated QA Contact may be allowed to VERIFY the bug. + Bugzilla has been + designed to make it easy for you to write your own custom rules to define + who is allowed to make what sorts of value transition. + </para> + + <para> + For maximum flexibility, customizing this means editing Bugzilla's Perl + code. This gives the administrator complete control over exactly who is + allowed to do what. The relevant function is called + <filename>CheckCanChangeField()</filename>, + and is found in <filename>process_bug.cgi</filename> in your + Bugzilla directory. If you open that file and grep for + "sub CheckCanChangeField", you'll find it. + </para> + + <para> + This function has been carefully commented to allow you to see exactly + how it works, and give you an idea of how to make changes to it. Certain + marked sections should not be changed - these are the "plumbing" which + makes the rest of the function work. In between those sections, you'll + find snippets of code like: + <programlisting> # Allow the owner to change anything. + if ($ownerid eq $whoid) { + return 1; + }</programlisting> + It's fairly obvious what this piece of code does. + </para> + + <para> + So, how does one go about changing this function? Well, simple changes + can be made just be removing pieces - for example, if you wanted to + prevent any user adding a comment to a bug, just remove the lines marked + "Allow anyone to change comments." And if you want the reporter to have + no special rights on bugs they have filed, just remove the entire section + which refers to him. + </para> + + <para> + More complex customizations are not much harder. Basically, you add + a check in the right place in the function, i.e. after all the variables + you are using have been set up. So, don't look at $ownerid before + $ownerid has been obtained from the database. You can either add a + positive check, which returns 1 (allow) if certain conditions are true, + or a negative check, which returns 0 (deny.) E.g.: + <programlisting> if ($field eq "qacontact") { + if (Bugzilla->user->groups("quality_assurance")) { + return 1; + } + else { + return 0; + } + }</programlisting> + This says that only users in the group "quality_assurance" can change + the QA Contact field of a bug. Getting more weird: + <programlisting> if (($field eq "priority") && + (Bugzilla->user->email =~ /.*\@example\.com$/)) + { + if ($oldvalue eq "P1") { + return 1; + } + else { + return 0; + } + }</programlisting> + This says that if the user is trying to change the priority field, + and their email address is @example.com, they can only do so if the + old value of the field was "P1". Not very useful, but illustrative. + </para> + + <para> + For a list of possible field names, look in + <filename>data/versioncache</filename> for the list called + <filename>@::log_columns</filename>. If you need help writing custom + rules for your organization, ask in the newsgroup. + </para> + </section> + + <section id="dbmodify"> + <title>Modifying Your Running System</title> + + <para>Bugzilla optimizes database lookups by storing all relatively + static information in the + <filename>versioncache</filename> file, located in the + <filename class="directory">data/</filename> + subdirectory under your installation directory.</para> + + <para>If you make a change to the structural data in your database (the + versions table for example), or to the + <quote>constants</quote> + + encoded in <filename>defparams.pl</filename>, you will need to remove + the cached content from the data directory (by doing a + <quote>rm data/versioncache</quote> + + ), or your changes won't show up.</para> + + <para> <filename>versioncache</filename> + gets automatically regenerated whenever it's more than + an hour old, so Bugzilla will eventually notice your changes by itself, + but generally you want it to notice right away, so that you can test + things.</para> + </section> + + <section id="dbdoc"> + <title>MySQL Bugzilla Database Introduction</title> + + <para>This information comes straight from my life. I was forced to learn + how Bugzilla organizes database because of nitpicky requests from users + for tiny changes in wording, rather than having people re-educate + themselves or figure out how to work our procedures around the tool. It + sucks, but it can and will happen to you, so learn how the schema works + and deal with it when it comes.</para> + + <para>So, here you are with your brand-new installation of Bugzilla. + You've got MySQL set up, Apache working right, Perl DBI and DBD talking + to the database flawlessly. Maybe you've even entered a few test bugs to + make sure email's working; people seem to be notified of new bugs and + changes, and you can enter and edit bugs to your heart's content. Perhaps + you've gone through the trouble of setting up a gateway for people to + submit bugs to your database via email, have had a few people test it, + and received rave reviews from your beta testers.</para> + + <para>What's the next thing you do? Outline a training strategy for your + development team, of course, and bring them up to speed on the new tool + you've labored over for hours.</para> + + <para>Your first training session starts off very well! You have a + captive audience which seems enraptured by the efficiency embodied in + this thing called "Bugzilla". You are caught up describing the nifty + features, how people can save favorite queries in the database, set them + up as headers and footers on their pages, customize their layouts, + generate reports, track status with greater efficiency than ever before, + leap tall buildings with a single bound and rescue Jane from the clutches + of Certain Death!</para> + + <para>But Certain Death speaks up -- a tiny voice, from the dark corners + of the conference room. "I have a concern," the voice hisses from the + darkness, "about the use of the word 'verified'."</para> + + <para>The room, previously filled with happy chatter, lapses into + reverential silence as Certain Death (better known as the Vice President + of Software Engineering) continues. "You see, for two years we've used + the word 'verified' to indicate that a developer or quality assurance + engineer has confirmed that, in fact, a bug is valid. I don't want to + lose two years of training to a new software product. You need to change + the bug status of 'verified' to 'approved' as soon as possible. To avoid + confusion, of course."</para> + + <para>Oh no! Terror strikes your heart, as you find yourself mumbling + "yes, yes, I don't think that would be a problem," You review the changes + with Certain Death, and continue to jabber on, "no, it's not too big a + change. I mean, we have the source code, right? You know, 'Use the + Source, Luke' and all that... no problem," All the while you quiver + inside like a beached jellyfish bubbling, burbling, and boiling on a hot + Jamaican sand dune...</para> + + <para>Thus begins your adventure into the heart of Bugzilla. You've been + forced to learn about non-portable enum() fields, varchar columns, and + tinyint definitions. The Adventure Awaits You!</para> + + <section> + <title>Bugzilla Database Basics</title> + + <para>If you were like me, at this point you're totally clueless about + the internals of MySQL, and if it weren't for this executive order from + the Vice President you couldn't care less about the difference between + a + <quote>bigint</quote> + + and a + <quote>tinyint</quote> + + entry in MySQL. I recommend you refer to the + <ulink url="http://www.mysql.com/documentation/">MySQL documentation</ulink> + . Below are the basics you need to know about the Bugzilla database. + Check the chart above for more details.</para> + + <para> + <orderedlist> + <listitem> + <para>To connect to your database:</para> + + <para> + <prompt>bash#</prompt> + + <command>mysql</command> + + <parameter>-u root</parameter> + </para> + + <para>If this works without asking you for a password, + <emphasis>shame on you</emphasis> + + ! You should have locked your security down like the installation + instructions told you to. You can find details on locking down + your database in the Bugzilla FAQ in this directory (under + "Security"), or more robust security generalities in the + <ulink url="http://www.mysql.com/php/manual.php3?section=Privilege_system">MySQL + searchable documentation</ulink>. + </para> + </listitem> + + <listitem> + <para>You should now be at a prompt that looks like this:</para> + + <para> + <prompt>mysql></prompt> + </para> + + <para>At the prompt, if + <quote>bugs</quote> + + is the name you chose in the + <filename>localconfig</filename> + + file for your Bugzilla database, type:</para> + + <para> + <prompt>mysql</prompt> + + <command>use bugs;</command> + </para> + + </listitem> + </orderedlist> + </para> + + <section> + <title>Bugzilla Database Tables</title> + + <para>Imagine your MySQL database as a series of spreadsheets, and + you won't be too far off. If you use this command:</para> + + <para> + <prompt>mysql></prompt> + <command>show tables from bugs;</command> + </para> + + <para>you'll be able to see the names of all the + <quote>spreadsheets</quote> + (tables) in your database.</para> + + <para>From the command issued above, ou should have some + output that looks like this: +<programlisting> ++-------------------+ +| Tables in bugs | ++-------------------+ +| attachments | +| bugs | +| bugs_activity | +| cc | +| components | +| dependencies | +| fielddefs | +| groups | +| keyworddefs | +| keywords | +| logincookies | +| longdescs | +| milestones | +| namedqueries | +| products | +| profiles | +| profiles_activity | +| tokens | +| versions | +| votes | +| watch | ++-------------------+ +</programlisting> +</para> + +<literallayout> + Here's an overview of what each table does. Most columns in each table have +descriptive names that make it fairly trivial to figure out their jobs. + +attachments: This table stores all attachments to bugs. It tends to be your +largest table, yet also generally has the fewest entries because file +attachments are so (relatively) large. + +bugs: This is the core of your system. The bugs table stores most of the +current information about a bug, with the exception of the info stored in the +other tables. + +bugs_activity: This stores information regarding what changes are made to bugs +when -- a history file. + +cc: This tiny table simply stores all the CC information for any bug which has +any entries in the CC field of the bug. Note that, like most other tables in +Bugzilla, it does not refer to users by their user names, but by their unique +userid, stored as a primary key in the profiles table. + +components: This stores the programs and components (or products and +components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program" +(product) field is the full name of the product, rather than some other unique +identifier, like bug_id and user_id are elsewhere in the database. + +dependencies: Stores data about those cool dependency trees. + +fielddefs: A nifty table that defines other tables. For instance, when you +submit a form that changes the value of "AssignedTo" this table allows +translation to the actual field name "assigned_to" for entry into MySQL. + +groups: defines bitmasks for groups. A bitmask is a number that can uniquely +identify group memberships. For instance, say the group that is allowed to +tweak parameters is assigned a value of "1", the group that is allowed to edit +users is assigned a "2", and the group that is allowed to create new groups is +assigned the bitmask of "4". By uniquely combining the group bitmasks (much +like the chmod command in UNIX,) you can identify a user is allowed to tweak +parameters and create groups, but not edit users, by giving him a bitmask of +"5", or a user allowed to edit users and create groups, but not tweak +parameters, by giving him a bitmask of "6" Simple, huh? + If this makes no sense to you, try this at the mysql prompt: +mysql> select * from groups; + You'll see the list, it makes much more sense that way. + +keyworddefs: Definitions of keywords to be used + +keywords: Unlike what you'd think, this table holds which keywords are +associated with which bug id's. + +logincookies: This stores every login cookie ever assigned to you for every +machine you've ever logged into Bugzilla from. Curiously, it never does any +housecleaning -- I see cookies in this file I've not used for months. However, +since Bugzilla never expires your cookie (for convenience' sake), it makes +sense. + +longdescs: The meat of bugzilla -- here is where all user comments are stored! +You've only got 2^24 bytes per comment (it's a mediumtext field), so speak +sparingly -- that's only the amount of space the Old Testament from the Bible +would take (uncompressed, 16 megabytes). Each comment is keyed to the +bug_id to which it's attached, so the order is necessarily chronological, for +comments are played back in the order in which they are received. + +milestones: Interesting that milestones are associated with a specific product +in this table, but Bugzilla does not yet support differing milestones by +product through the standard configuration interfaces. + +namedqueries: This is where everybody stores their "custom queries". Very +cool feature; it beats the tar out of having to bookmark each cool query you +construct. + +products: What products you have, whether new bug entries are allowed for the +product, what milestone you're working toward on that product, votes, etc. It +will be nice when the components table supports these same features, so you +could close a particular component for bug entry without having to close an +entire product... + +profiles: Ahh, so you were wondering where your precious user information was +stored? Here it is! With the passwords in plain text for all to see! (but +sshh... don't tell your users!) + +profiles_activity: Need to know who did what when to who's profile? This'll +tell you, it's a pretty complete history. + +versions: Version information for every product + +votes: Who voted for what when + +watch: Who (according to userid) is watching who's bugs (according to their +userid). + + +=== +THE DETAILS +=== + + Ahh, so you're wondering just what to do with the information above? At the +mysql prompt, you can view any information about the columns in a table with +this command (where "table" is the name of the table you wish to view): + +mysql> show columns from table; + + You can also view all the data in a table with this command: + +mysql> select * from table; + + -- note: this is a very bad idea to do on, for instance, the "bugs" table if +you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or +50,000 bugs play across your screen. + + You can limit the display from above a little with the command, where +"column" is the name of the column for which you wish to restrict information: + +mysql> select * from table where (column = "some info"); + + -- or the reverse of this + +mysql> select * from table where (column != "some info"); + + Let's take our example from the introduction, and assume you need to change +the word "verified" to "approved" in the resolution field. We know from the +above information that the resolution is likely to be stored in the "bugs" +table. Note we'll need to change a little perl code as well as this database +change, but I won't plunge into that in this document. Let's verify the +information is stored in the "bugs" table: + +mysql> show columns from bugs + + (exceedingly long output truncated here) +| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED|| + + Sorry about that long line. We see from this that the "bug status" column is +an "enum field", which is a MySQL peculiarity where a string type field can +only have certain types of entries. While I think this is very cool, it's not +standard SQL. Anyway, we need to add the possible enum field entry +'APPROVED' by altering the "bugs" table. + +mysql> ALTER table bugs CHANGE bug_status bug_status + -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED", + -> "VERIFIED", "APPROVED", "CLOSED") not null; + + (note we can take three lines or more -- whatever you put in before the +semicolon is evaluated as a single expression) + +Now if you do this: + +mysql> show columns from bugs; + + you'll see that the bug_status field has an extra "APPROVED" enum that's +available! Cool thing, too, is that this is reflected on your query page as +well -- you can query by the new status. But how's it fit into the existing +scheme of things? + Looks like you need to go back and look for instances of the word "verified" +in the perl code for Bugzilla -- wherever you find "verified", change it to +"approved" and you're in business (make sure that's a case-insensitive search). +Although you can query by the enum field, you can't give something a status +of "APPROVED" until you make the perl changes. Note that this change I +mentioned can also be done by editing checksetup.pl, which automates a lot of +this. But you need to know this stuff anyway, right? + </literallayout> + </section> + </section> + </section> + + <!-- Integrating Bugzilla with Third-Party Tools --> + &integration; + +</chapter> + +<!-- Keep this comment at the end of the file +Local variables: +mode: sgml +sgml-always-quote-attributes:t +sgml-auto-insert-required-elements:t +sgml-balanced-tag-edit:t +sgml-exposed-tags:nil +sgml-general-insert-case:lower +sgml-indent-data:t +sgml-indent-step:2 +sgml-local-catalogs:nil +sgml-local-ecat-files:nil +sgml-minimize-attributes:nil +sgml-namecase-general:t +sgml-omittag:t +sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") +sgml-shorttag:t +sgml-tag-region-if-active:t +End: +--> + diff --git a/docs/xml/database.xml b/docs/xml/database.xml deleted file mode 100644 index aea80640b..000000000 --- a/docs/xml/database.xml +++ /dev/null @@ -1,392 +0,0 @@ -<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> -<appendix id="database"> - <title>The Bugzilla Database</title> - - <note> - <para>This document really needs to be updated with more fleshed out - information about primary keys, interrelationships, and maybe some nifty - tables to document dependencies. Any takers?</para> - </note> - - <section id="dbmodify"> - <title>Modifying Your Running System</title> - - <para>Bugzilla optimizes database lookups by storing all relatively - static information in the - <filename>versioncache</filename> file, located in the - <filename class="directory">data/</filename> - subdirectory under your installation directory.</para> - - <para>If you make a change to the structural data in your database (the - versions table for example), or to the - <quote>constants</quote> - - encoded in <filename>defparams.pl</filename>, you will need to remove - the cached content from the data directory (by doing a - <quote>rm data/versioncache</quote> - - ), or your changes won't show up.</para> - - <para> <filename>versioncache</filename> - gets automatically regenerated whenever it's more than - an hour old, so Bugzilla will eventually notice your changes by itself, - but generally you want it to notice right away, so that you can test - things.</para> - </section> - - <section id="dbdoc"> - <title>MySQL Bugzilla Database Introduction</title> - - <para>This information comes straight from my life. I was forced to learn - how Bugzilla organizes database because of nitpicky requests from users - for tiny changes in wording, rather than having people re-educate - themselves or figure out how to work our procedures around the tool. It - sucks, but it can and will happen to you, so learn how the schema works - and deal with it when it comes.</para> - - <para>So, here you are with your brand-new installation of Bugzilla. - You've got MySQL set up, Apache working right, Perl DBI and DBD talking - to the database flawlessly. Maybe you've even entered a few test bugs to - make sure email's working; people seem to be notified of new bugs and - changes, and you can enter and edit bugs to your heart's content. Perhaps - you've gone through the trouble of setting up a gateway for people to - submit bugs to your database via email, have had a few people test it, - and received rave reviews from your beta testers.</para> - - <para>What's the next thing you do? Outline a training strategy for your - development team, of course, and bring them up to speed on the new tool - you've labored over for hours.</para> - - <para>Your first training session starts off very well! You have a - captive audience which seems enraptured by the efficiency embodied in - this thing called "Bugzilla". You are caught up describing the nifty - features, how people can save favorite queries in the database, set them - up as headers and footers on their pages, customize their layouts, - generate reports, track status with greater efficiency than ever before, - leap tall buildings with a single bound and rescue Jane from the clutches - of Certain Death!</para> - - <para>But Certain Death speaks up -- a tiny voice, from the dark corners - of the conference room. "I have a concern," the voice hisses from the - darkness, "about the use of the word 'verified'."</para> - - <para>The room, previously filled with happy chatter, lapses into - reverential silence as Certain Death (better known as the Vice President - of Software Engineering) continues. "You see, for two years we've used - the word 'verified' to indicate that a developer or quality assurance - engineer has confirmed that, in fact, a bug is valid. I don't want to - lose two years of training to a new software product. You need to change - the bug status of 'verified' to 'approved' as soon as possible. To avoid - confusion, of course."</para> - - <para>Oh no! Terror strikes your heart, as you find yourself mumbling - "yes, yes, I don't think that would be a problem," You review the changes - with Certain Death, and continue to jabber on, "no, it's not too big a - change. I mean, we have the source code, right? You know, 'Use the - Source, Luke' and all that... no problem," All the while you quiver - inside like a beached jellyfish bubbling, burbling, and boiling on a hot - Jamaican sand dune...</para> - - <para>Thus begins your adventure into the heart of Bugzilla. You've been - forced to learn about non-portable enum() fields, varchar columns, and - tinyint definitions. The Adventure Awaits You!</para> - - <section> - <title>Bugzilla Database Basics</title> - - <para>If you were like me, at this point you're totally clueless about - the internals of MySQL, and if it weren't for this executive order from - the Vice President you couldn't care less about the difference between - a - <quote>bigint</quote> - - and a - <quote>tinyint</quote> - - entry in MySQL. I recommend you refer to the - <ulink url="http://www.mysql.com/documentation/">MySQL documentation</ulink> - . Below are the basics you need to know about the Bugzilla database. - Check the chart above for more details.</para> - - <para> - <orderedlist> - <listitem> - <para>To connect to your database:</para> - - <para> - <prompt>bash#</prompt> - - <command>mysql</command> - - <parameter>-u root</parameter> - </para> - - <para>If this works without asking you for a password, - <emphasis>shame on you</emphasis> - - ! You should have locked your security down like the installation - instructions told you to. You can find details on locking down - your database in the Bugzilla FAQ in this directory (under - "Security"), or more robust security generalities in the - <ulink url="http://www.mysql.com/php/manual.php3?section=Privilege_system">MySQL - searchable documentation</ulink>. - </para> - </listitem> - - <listitem> - <para>You should now be at a prompt that looks like this:</para> - - <para> - <prompt>mysql></prompt> - </para> - - <para>At the prompt, if - <quote>bugs</quote> - - is the name you chose in the - <filename>localconfig</filename> - - file for your Bugzilla database, type:</para> - - <para> - <prompt>mysql</prompt> - - <command>use bugs;</command> - </para> - - </listitem> - </orderedlist> - </para> - - <section> - <title>Bugzilla Database Tables</title> - - <para>Imagine your MySQL database as a series of spreadsheets, and - you won't be too far off. If you use this command:</para> - - <para> - <prompt>mysql></prompt> - <command>show tables from bugs;</command> - </para> - - <para>you'll be able to see the names of all the - <quote>spreadsheets</quote> - (tables) in your database.</para> - - <para>From the command issued above, ou should have some - output that looks like this: -<programlisting> -+-------------------+ -| Tables in bugs | -+-------------------+ -| attachments | -| bugs | -| bugs_activity | -| cc | -| components | -| dependencies | -| fielddefs | -| groups | -| keyworddefs | -| keywords | -| logincookies | -| longdescs | -| milestones | -| namedqueries | -| products | -| profiles | -| profiles_activity | -| tokens | -| versions | -| votes | -| watch | -+-------------------+ -</programlisting> -</para> - -<literallayout> - Here's an overview of what each table does. Most columns in each table have -descriptive names that make it fairly trivial to figure out their jobs. - -attachments: This table stores all attachments to bugs. It tends to be your -largest table, yet also generally has the fewest entries because file -attachments are so (relatively) large. - -bugs: This is the core of your system. The bugs table stores most of the -current information about a bug, with the exception of the info stored in the -other tables. - -bugs_activity: This stores information regarding what changes are made to bugs -when -- a history file. - -cc: This tiny table simply stores all the CC information for any bug which has -any entries in the CC field of the bug. Note that, like most other tables in -Bugzilla, it does not refer to users by their user names, but by their unique -userid, stored as a primary key in the profiles table. - -components: This stores the programs and components (or products and -components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program" -(product) field is the full name of the product, rather than some other unique -identifier, like bug_id and user_id are elsewhere in the database. - -dependencies: Stores data about those cool dependency trees. - -fielddefs: A nifty table that defines other tables. For instance, when you -submit a form that changes the value of "AssignedTo" this table allows -translation to the actual field name "assigned_to" for entry into MySQL. - -groups: defines bitmasks for groups. A bitmask is a number that can uniquely -identify group memberships. For instance, say the group that is allowed to -tweak parameters is assigned a value of "1", the group that is allowed to edit -users is assigned a "2", and the group that is allowed to create new groups is -assigned the bitmask of "4". By uniquely combining the group bitmasks (much -like the chmod command in UNIX,) you can identify a user is allowed to tweak -parameters and create groups, but not edit users, by giving him a bitmask of -"5", or a user allowed to edit users and create groups, but not tweak -parameters, by giving him a bitmask of "6" Simple, huh? - If this makes no sense to you, try this at the mysql prompt: -mysql> select * from groups; - You'll see the list, it makes much more sense that way. - -keyworddefs: Definitions of keywords to be used - -keywords: Unlike what you'd think, this table holds which keywords are -associated with which bug id's. - -logincookies: This stores every login cookie ever assigned to you for every -machine you've ever logged into Bugzilla from. Curiously, it never does any -housecleaning -- I see cookies in this file I've not used for months. However, -since Bugzilla never expires your cookie (for convenience' sake), it makes -sense. - -longdescs: The meat of bugzilla -- here is where all user comments are stored! -You've only got 2^24 bytes per comment (it's a mediumtext field), so speak -sparingly -- that's only the amount of space the Old Testament from the Bible -would take (uncompressed, 16 megabytes). Each comment is keyed to the -bug_id to which it's attached, so the order is necessarily chronological, for -comments are played back in the order in which they are received. - -milestones: Interesting that milestones are associated with a specific product -in this table, but Bugzilla does not yet support differing milestones by -product through the standard configuration interfaces. - -namedqueries: This is where everybody stores their "custom queries". Very -cool feature; it beats the tar out of having to bookmark each cool query you -construct. - -products: What products you have, whether new bug entries are allowed for the -product, what milestone you're working toward on that product, votes, etc. It -will be nice when the components table supports these same features, so you -could close a particular component for bug entry without having to close an -entire product... - -profiles: Ahh, so you were wondering where your precious user information was -stored? Here it is! With the passwords in plain text for all to see! (but -sshh... don't tell your users!) - -profiles_activity: Need to know who did what when to who's profile? This'll -tell you, it's a pretty complete history. - -versions: Version information for every product - -votes: Who voted for what when - -watch: Who (according to userid) is watching who's bugs (according to their -userid). - - -=== -THE DETAILS -=== - - Ahh, so you're wondering just what to do with the information above? At the -mysql prompt, you can view any information about the columns in a table with -this command (where "table" is the name of the table you wish to view): - -mysql> show columns from table; - - You can also view all the data in a table with this command: - -mysql> select * from table; - - -- note: this is a very bad idea to do on, for instance, the "bugs" table if -you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or -50,000 bugs play across your screen. - - You can limit the display from above a little with the command, where -"column" is the name of the column for which you wish to restrict information: - -mysql> select * from table where (column = "some info"); - - -- or the reverse of this - -mysql> select * from table where (column != "some info"); - - Let's take our example from the introduction, and assume you need to change -the word "verified" to "approved" in the resolution field. We know from the -above information that the resolution is likely to be stored in the "bugs" -table. Note we'll need to change a little perl code as well as this database -change, but I won't plunge into that in this document. Let's verify the -information is stored in the "bugs" table: - -mysql> show columns from bugs - - (exceedingly long output truncated here) -| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED|| - - Sorry about that long line. We see from this that the "bug status" column is -an "enum field", which is a MySQL peculiarity where a string type field can -only have certain types of entries. While I think this is very cool, it's not -standard SQL. Anyway, we need to add the possible enum field entry -'APPROVED' by altering the "bugs" table. - -mysql> ALTER table bugs CHANGE bug_status bug_status - -> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED", - -> "VERIFIED", "APPROVED", "CLOSED") not null; - - (note we can take three lines or more -- whatever you put in before the -semicolon is evaluated as a single expression) - -Now if you do this: - -mysql> show columns from bugs; - - you'll see that the bug_status field has an extra "APPROVED" enum that's -available! Cool thing, too, is that this is reflected on your query page as -well -- you can query by the new status. But how's it fit into the existing -scheme of things? - Looks like you need to go back and look for instances of the word "verified" -in the perl code for Bugzilla -- wherever you find "verified", change it to -"approved" and you're in business (make sure that's a case-insensitive search). -Although you can query by the enum field, you can't give something a status -of "APPROVED" until you make the perl changes. Note that this change I -mentioned can also be done by editing checksetup.pl, which automates a lot of -this. But you need to know this stuff anyway, right? - </literallayout> - </section> - </section> - </section> - -</appendix> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-always-quote-attributes:t -sgml-auto-insert-required-elements:t -sgml-balanced-tag-edit:t -sgml-exposed-tags:nil -sgml-general-insert-case:lower -sgml-indent-data:t -sgml-indent-step:2 -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -sgml-minimize-attributes:nil -sgml-namecase-general:t -sgml-omittag:t -sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") -sgml-shorttag:t -sgml-tag-region-if-active:t -End: ---> - diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml index e2cebd647..d00a8e8f3 100644 --- a/docs/xml/faq.xml +++ b/docs/xml/faq.xml @@ -14,19 +14,6 @@ <title>General Questions</title> <qandaentry> - <question id="faq-general-information"> - <para> - Where can I find information about Bugzilla?</para> - </question> - <answer> - <para> - You can stay up-to-date with the latest Bugzilla - information at <ulink url="http://www.bugzilla.org/"/>. - </para> - </answer> - </qandaentry> - - <qandaentry> <question id="faq-general-license"> <para> What license is Bugzilla distributed under? @@ -53,12 +40,6 @@ as consultants for Bugzilla. </para> <para> - <ulink url="http://www.collab.net/"/> offers - Bugzilla as part of their standard offering to large projects. - They do have some minimum fees that are pretty hefty, and generally - aren't interested in small projects. - </para> - <para> There are several experienced Bugzilla hackers on the mailing list/newsgroup who are willing to make themselves available for generous compensation. @@ -79,11 +60,10 @@ There are <emphasis>dozens</emphasis> of major companies with public Bugzilla sites to track bugs in their products. We have a fairly complete list available on our website at - <ulink url="http://bugzilla.org/installation_list.html"/>. If you + <ulink url="http://bugzilla.org/installation-list/"/>. If you have an installation of Bugzilla and would like to be added to the list, whether it's a public install or not, simply e-mail - Gerv <email>gerv@mozilla.org</email>. Keep in mind that it's kinda - difficult to get onto the <quote>high-profile</quote> list ;). + Gerv <email>gerv@mozilla.org</email>. </para> </answer> </qandaentry> @@ -241,13 +221,6 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl <qandadiv id="faq-phb"> <title>Managerial Questions</title> - <para> - <note> - <para> - Questions likely to be asked by managers. :-) - </para> - </note> - </para> <qandaentry> <question id="faq-phb-client"> @@ -258,69 +231,7 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </question> <answer> <para> - It is web and e-mail based. You can edit bugs by sending specially - formatted email to a properly configured Bugzilla, or control via the web. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question id="faq-phb-integration"> - <para> - Can Bugzilla integrate with - Perforce (SCM software)? - </para> - </question> - <answer> - <para> - Yes! You can find more information elsewhere in "The Bugzilla - Guide" in the "Integration with Third-Party Products" section. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question id="faq-phb-projects"> - <para> - Does Bugzilla allow the user to track multiple projects? - </para> - </question> - <answer> - <para> - Absolutely! You can track any number of Products that can each be - composed of any number of Components. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question id="faq-phb-sorting"> - <para> - If I am on many projects, and search for all bugs assigned to me, will - Bugzilla list them for me and allow me to sort by project, severity etc? - </para> - </question> - <answer> - <para> - Yes. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question id="faq-phb-attachments"> - <para> - Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes, - are there any that are NOT allowed? - </para> - </question> - <answer> - <para> - Yes - any sort of attachment is allowed, although administrators can - configure a maximum size. - Bugzilla gives the user the option of either using the MIME-type - supplied by the browser, choosing from a pre-defined list or - manually typing any arbitrary MIME-type. + It is web and e-mail based. </para> </answer> </qandaentry> @@ -380,27 +291,13 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl <answer> <para> Email notification is user-configurable. By default, the bug id and - Summary of the bug report accompany each email notification, along with + summary of the bug report accompany each email notification, along with a list of the changes made. </para> </answer> </qandaentry> <qandaentry> - <question id="faq-phb-cclist"> - <para> - Can email notification be set up to send to multiple - people, some on the To List, CC List, BCC List etc? - </para> - </question> - <answer> - <para> - Yes. - </para> - </answer> - </qandaentry> - - <qandaentry> <question id="faq-phb-emailapp"> <para> Do users have to have any particular @@ -439,13 +336,13 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl Bugzilla can output buglists as HTML (the default), CSV or RDF. The link for CSV can be found at the bottom of the buglist in HTML format. This CSV format can easily be imported into MS Excel or - other spread-sheet applications. + other spreadsheet applications. </para> <para> To use the RDF format of the buglist it is necessary to append a <computeroutput>&ctype=rdf</computeroutput> to the URL. RDF is meant to be machine readable and thus it is assumed that the - URL would be generated progmatically so there is no user visible + URL would be generated programatically so there is no user visible link to this format. </para> <para> @@ -500,21 +397,6 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </qandaentry> <qandaentry> - <question id="faq-phb-searching"> - <para> - Does Bugzilla have the ability to search by word, phrase, compound - search? - </para> - </question> - <answer> - <para> - You have no idea. Bugzilla's query interface, particularly with the - advanced Boolean operators, is incredibly versatile. - </para> - </answer> - </qandaentry> - - <qandaentry> <question id="faq-phb-midair"> <para> Does Bugzilla provide record locking when there is simultaneous access @@ -567,7 +449,7 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an - "Out-of-the-Box" solution. + "out-of-the-box" solution? </para> </question> <answer> @@ -657,24 +539,6 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </para> </answer> </qandaentry> - - - <qandaentry> - <question id="faq-security-mysqluser"> - <para> - I've implemented the security fixes mentioned in Chris Yeh's security - advisory of 5/10/2000 advising not to run MySQL as root, and am running into - problems with MySQL no longer working correctly. - </para> - </question> - <answer> - <para> - This is a common problem, related to running out of file descriptors. - Simply add "ulimit -n unlimited" to the script which starts - mysqld. - </para> - </answer> - </qandaentry> </qandadiv> <qandadiv id="faq-email"> @@ -714,7 +578,7 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl <qandaentry> <question id="faq-email-whine"> <para> - I want whineatnews.pl to whine at something more, or other than, only new + I want whineatnews.pl to whine at something different to only new bugs. How do I do it? </para> </question> @@ -731,29 +595,6 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </qandaentry> <qandaentry> - <question id="faq-email-procmail"> - <para> - I don't like/want to use Procmail to hand mail off to bug_email.pl. - What alternatives do I have? - </para> - </question> - <answer> - <para> - You can call bug_email.pl directly from your aliases file, with - an entry like this: - <blockquote> - <para> - bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" - </para> - </blockquote> - However, this is fairly nasty and subject to problems; you also - need to set up your smrsh (sendmail restricted shell) to allow - it. In a pinch, though, it can work. - </para> - </answer> - </qandaentry> - - <qandaentry> <question id="faq-email-mailif"> <para> How do I set up the email interface to submit/change bugs via email? @@ -776,17 +617,17 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </question> <answer> <para> + If you are using <application>sendmail</application>, try enabling + <option>sendmailnow</option> in <filename>editparams.cgi</filename>. + <!-- TODO provide more info about this, possibly a link to admin --> + </para> + <para> If you are using an alternate <glossterm linkend="gloss-mta">MTA</glossterm>, make sure the options given in <filename>Bugzilla/BugMail.pm</filename> and any other place where <application>sendmail</application> is called from are correct for your MTA. You should also ensure that the <option>sendmailnow</option> param is set to <literal>on</literal>. </para> - <para> - If you are using <application>sendmail</application>, try enabling - <option>sendmailnow</option> in <filename>editparams.cgi</filename>. - <!-- TODO provide more info about this, possibly a link to admin --> - </para> </answer> </qandaentry> @@ -804,7 +645,7 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl button after entering your email address. </para> <para> - If you never receive mail from Bugzilla, chances you do not have + If you never receive mail from Bugzilla, chances are you do not have sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked to, "/usr/lib/sendmail". </para> @@ -823,11 +664,12 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl </question> <answer> <para> - Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle. + Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle, + but it is now so old as to be obsolete, and is totally unsupported. Red Hat's newer version (based on 2.17.1 and soon to be merged into the main distribution) runs on PostgreSQL. At this time we know of - no recent ports of Bugzilla to Oracle but do intend to support it - in the future (possibly the 2.20 time-frame). + no recent ports of Bugzilla to Oracle; to be honest, Bugzilla + doesn't need what Oracle offers. </para> </answer> </qandaentry> @@ -842,9 +684,8 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl <answer> <para> Run the <quote>sanity check</quote> utility - (<filename>./sanitycheck.cgi</filename> in the - Bugzilla_home directory) from your web browser to see! If - it finishes without errors, you're + (<filename>sanitycheck.cgi</filename>) from your web browser to see! + If it finishes without errors, you're <emphasis>probably</emphasis> OK. If it doesn't come back OK (i.e. any red letters), there are certain things Bugzilla can recover from and certain things it can't. If diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index 336cc0ccc..447975523 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -1,5 +1,5 @@ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> --> -<!-- $Id: installation.xml,v 1.55 2003/10/30 18:42:21 jocuri%softhome.net Exp $ --> +<!-- $Id: installation.xml,v 1.56 2004/01/15 22:34:35 gerv%gerv.net Exp $ --> <chapter id="installation"> <title>Installation</title> @@ -40,6 +40,11 @@ with administrative access to install it for you. </para> + <para> + You are strongly recommended to make a backup of your system + before installing Bugzilla and at regular intervals thereafter. + </para> + <para>The listing below is a basic step-by-step list. More information can be found in the sections below. Minimum versions will be included in parenthesis where appropriate. @@ -47,17 +52,13 @@ <procedure> <step> - <para><link linkend="install-mysql">Install MySQL</link> - (&min-mysql-ver;) - </para> - </step> - <step> <para><link linkend="install-perl">Install Perl</link> (&min-perl-ver;) </para> </step> <step> - <para><link linkend="install-perlmodules">Install Perl Modules</link> + <para><link linkend="install-mysql">Install MySQL</link> + (&min-mysql-ver;) </para> </step> <step> @@ -69,11 +70,28 @@ </para> </step> <step> + <para><link linkend="install-perlmodules">Install Perl Modules</link> + </para> + </step> + <step> <para><link linkend="install-setupdatabase">Setup the MySQL Database</link> </para> </step> </procedure> + <section id="install-perl"> + <title>Perl</title> + + <para>Any machine that doesn't have Perl on it is a sad machine indeed. + Perl can be got in source form from <ulink url="http://www.perl.com"/>. + There are also binary versions available for many platforms, most of which + are linked to from perl.com. + Although Bugzilla runs with perl &min-perl-ver;, + 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 &newest-perl-ver;.</para> + </section> + <section id="install-mysql"> <title>MySQL</title> @@ -121,19 +139,106 @@ set-variable = max_allowed_packet=1M also wish to utilize the <option>skip-networking</option> option as mentioned in <xref linkend="security-mysql"/> for the added security. </para> + + <section id="install-setupdatabase"> + <title>Configuring MySQL</title> + + <para>This first thing you'll want to do is make sure you've given the + <quote>root</quote> user a password as suggested in + <xref linkend="security-mysql"/>. For clarity, these instructions will + assume that your MySQL user for Bugzilla will be <quote>bugs_user</quote>, + the database will be called <quote>bugs_db</quote> and the password for + the <quote>bugs_user</quote> user is <quote>bugs_password</quote>. You + should, of course, substitute the values you intend to use for your site. + </para> + + <note> + <para>Most people use <quote>bugs</quote> for both the user and + database name. + </para> + </note> + + <para>Next, we use an SQL <command>GRANT</command> command to create a + <quote>bugs_user</quote> + user, and grant sufficient permissions for checksetup.pl, which we'll + use later, to work its magic. This also restricts the + <quote>bugs_user</quote> + user to operations within a database called + <quote>bugs_db</quote>, and only allows the account to connect from + <quote>localhost</quote>. + Modify it to reflect your setup if you will be connecting from + another machine or as a different user.</para> + + <screen> + <prompt>mysql></prompt> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, + DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost + IDENTIFIED BY 'bugs_password'; + <prompt>mysql></prompt> FLUSH PRIVILEGES; + </screen> + + <note> + <para>If you are using MySQL 4, the bugs user also needs to be granted + the <computeroutput>LOCK TABLES</computeroutput> and + <computeroutput>CREATE TEMPORARY TABLES</computeroutput> permissions. + </para> + </note> + </section> </section> - <section id="install-perl"> - <title>Perl</title> + <section id="install-webserver"> + <title>HTTP Server</title> - <para>Any machine that doesn't have Perl on it is a sad machine indeed. - Perl can be got in source form from <ulink url="http://www.perl.com"/>. - There are also binary versions available for many platforms, most of which - are linked to from perl.com. - Although Bugzilla runs with perl &min-perl-ver;, - 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 &newest-perl-ver;.</para> + <para>You have freedom of choice here, pretty much any web server that + is capable of running <glossterm linkend="gloss-cgi">CGI</glossterm> + scripts will work. <xref linkend="http"/> has more information about + configuring web servers to work with Bugzilla. + </para> + + <note> + <para>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 by filing a bug in &bzg-bugs;. + </para> + </note> + + </section> + + <section id="install-bzfiles"> + <title>Bugzilla</title> + + <para>You should untar the Bugzilla files into a directory that you're + willing to make writable by the default web server user (probably + <quote>nobody</quote>). + You may decide to put the files in the main web space for your + web server or perhaps in + <filename>/usr/local</filename> + with a symbolic link in the web space that points to the Bugzilla + directory.</para> + + <tip> + <para>If you symlink the bugzilla directory into your Apache's HTML + hierarchy, you may receive + <errorname>Forbidden</errorname> + errors unless you add the + <quote>FollowSymLinks</quote> + directive to the <Directory> entry for the HTML root + in httpd.conf.</para> + </tip> + + <para>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 + <filename>checksetup.pl</filename> + script, which locks down your installation.</para> + + <caution> + <para>The default Bugzilla distribution is not designed to be placed + in a <filename class="directory">cgi-bin</filename> directory (this + includes any directory which is configured using the + <option>ScriptAlias</option> directive of Apache). + </para> + </caution> </section> <section id="install-perlmodules"> @@ -177,7 +282,7 @@ set-variable = max_allowed_packet=1M </para> </callout> <callout arearefs="cpan-moduledir"> - <para>The process of untaring the module as defined in + <para>The process of untarring the module as defined in <xref linkend="cpan-moduletar"/> will create the <filename class="directory"><module></filename> directory. </para> @@ -660,122 +765,14 @@ ReadLine support enabled </section> </section> - <section id="install-webserver"> - <title>HTTP Server</title> - - <para>You have freedom of choice here, pretty much any web server that - is capable of running <glossterm linkend="gloss-cgi">CGI</glossterm> - scripts will work. <xref linkend="http"/> has more information about - configuring web servers to work with Bugzilla. - </para> - - <note> - <para>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 by filing a bug in &bzg-bugs;. - </para> - </note> - - </section> - - <section id="install-bzfiles"> - <title>Bugzilla</title> - - <para>You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <quote>nobody</quote>). - You may decide to put the files in the main web space for your - web server or perhaps in - <filename>/usr/local</filename> - with a symbolic link in the web space that points to the Bugzilla - directory.</para> - - <tip> - <para>If you symlink the bugzilla directory into your Apache's HTML - hierarchy, you may receive - <errorname>Forbidden</errorname> - errors unless you add the - <quote>FollowSymLinks</quote> - directive to the <Directory> entry for the HTML root - in httpd.conf.</para> - </tip> - - <para>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 - <filename>checksetup.pl</filename> - script, which locks down your installation.</para> - - <caution> - <para>The default Bugzilla distribution is not designed to be placed - in a <filename class="directory">cgi-bin</filename> directory (this - includes any directory which is configured using the - <option>ScriptAlias</option> directive of Apache). This will probably - change as part of - <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=44659">bug - 44659</ulink>. - </para> - </caution> - </section> - - <section id="install-setupdatabase"> - <title>Setting Up the MySQL Database</title> - - <para>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.</para> - - <para>This first thing you'll want to do is make sure you've given the - <quote>root</quote> user a password as suggested in - <xref linkend="security-mysql"/>. For clarity, these instructions will - assume that your MySQL user for Bugzilla will be <quote>bugs_user</quote>, - the database will be called <quote>bugs_db</quote> and the password for - the <quote>bugs_user</quote> user is <quote>bugs_password</quote>. You - should, of course, substitute the values you intend to use for your site. - </para> - - <note> - <para>Most people use <quote>bugs</quote> for both the user and - database name. - </para> - </note> - - <para>Next, we use an SQL <command>GRANT</command> command to create a - <quote>bugs_user</quote> - user, and grant sufficient permissions for checksetup.pl, which we'll - use later, to work its magic. This also restricts the - <quote>bugs_user</quote> - user to operations within a database called - <quote>bugs_db</quote>, and only allows the account to connect from - <quote>localhost</quote>. - Modify it to reflect your setup if you will be connecting from - another machine or as a different user.</para> - - <screen> -<prompt>mysql></prompt> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE, - DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost - IDENTIFIED BY 'bugs_password'; -<prompt>mysql></prompt> FLUSH PRIVILEGES; - </screen> - - <note> - <para>If you are using MySQL 4, the bugs user also needs to be granted - the <computeroutput>LOCK TABLES</computeroutput> and - <computeroutput>CREATE TEMPORARY TABLES</computeroutput> permissions. - </para> - </note> - </section> <section> <title> <filename>checksetup.pl</filename> </title> - <para>Next, run the magic checksetup.pl script. (Many thanks to - <ulink url="mailto:holgerschurig@nikocity.de">Holger Schurig</ulink> - for writing this script!) - This script is designed to make sure your perl modules are the correct + <para>Next, run the magic checksetup.pl script. + This is designed to make sure your perl modules are the correct version and your MySQL database and other configuration options are consistent with the Bugzilla CGI files. It will make sure Bugzilla files and directories have reasonable @@ -849,6 +846,149 @@ ReadLine support enabled </section> </section> + <section id="http"> + <title>HTTP Server Configuration</title> + + <para>The Bugzilla Team recommends Apache when using Bugzilla, however, any web server + that can be configured to run <glossterm linkend="gloss-cgi">CGI</glossterm> scripts + should be able to handle Bugzilla. No matter what web server you choose, but + especially if you choose something other than Apache, you should be sure to read + <xref linkend="security-access"/>. + </para> + + <para>The plan for this section is to eventually document the specifics of how to lock + down permissions on individual web servers. + </para> + + <section id="http-apache"> + <title>Apache <productname>httpd</productname></title> + + <para>You will have to make sure that Apache is properly + configured to run the Bugzilla CGI scripts. You also need to make sure + that the <filename>.htaccess</filename> files created by + <command>./checksetup.pl</command> are allowed to override Apache's normal access + permissions or else important password information may be exposed to the + Internet. + </para> + + <para>You need to configure Apache to run .cgi files outside the + <filename class="directory">cgi-bin</filename> directory. + Open your + <filename>httpd.conf</filename> file and make sure the + following line exists and is uncommented:</para> + <programlisting> +AddHandler cgi-script .cgi + </programlisting> + + <para>To allow <filename>.htaccess</filename> files to override + permissions and .cgi files to run in the Bugzilla directory, make sure + the following two lines are in a <computeroutput>Directory</computeroutput> + directive that applies to the Bugzilla directory on your system + (either the Bugzilla directory or one of its parents). + </para> + <programlisting> +Options +ExecCGI +AllowOverride Limit + </programlisting> + + <para>You should modify the <DirectoryIndex> parameter for + the Apache virtual host running your Bugzilla installation to + allow <filename>index.cgi</filename> as the index page for a + directory, as well as the usual <filename>index.html</filename>, + <filename>index.htm</filename>, and so forth. </para> + + <note> + <para>For more information on Apache and its directives, see the + glossary entry on <xref linkend="gloss-apache"/>. + </para> + </note> + </section> + + <section id="http-iis"> + <title>Microsoft <productname>Internet Information Services</productname></title> + + <para>If you need, or for some reason even want, to use Microsoft's + <productname>Internet Information Services</productname> or + <productname>Personal Web Server</productname> you should be able + to. You will need to configure them to know how to run CGI scripts, + however. This is described in Microsoft Knowledge Base article + <ulink url="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp">Q245225</ulink> + for <productname>Internet Information Services</productname> and + <ulink url="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp">Q231998</ulink> + for <productname>Personal Web Server</productname>. + </para> + + <para>Also, and this can't be stressed enough, make sure that files such as + <filename>localconfig</filename> and your <filename class="directory">data</filename> + directory are secured as described in <xref linkend="security-access"/>. + </para> + + </section> + + <section id="http-aol"> + <title>AOL Server</title> + + <para>Ben FrantzDale reported success using AOL Server with Bugzilla. He + reported his experience and what appears below is based on that. + </para> + + <para>AOL Server will have to be configured to run + <glossterm linkend="gloss-cgi">CGI</glossterm> scripts, please consult + the documentation that came with your server for more information on + how to do this. + </para> + + <para>Because AOL Server doesn't support <filename>.htaccess</filename> + files, you'll have to create a <glossterm linkend="gloss-tcl">TCL</glossterm> + script. You should create an <filename>aolserver/modules/tcl/filter.tcl</filename> + file (the filename shouldn't matter) with the following contents (change + <computeroutput>/bugzilla/</computeroutput> to the web-based path to + your Bugzilla installation): + </para> + + <programlisting> +ns_register_filter preauth GET /bugzilla/localconfig filter_deny +ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny +ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny +ns_register_filter preauth GET /bugzilla/*.pl filter_deny +ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny +ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny +ns_register_filter preauth GET /bugzilla/data/* filter_deny +ns_register_filter preauth GET /bugzilla/template/* filter_deny + +proc filter_deny { why } { + ns_log Notice "filter_deny" + return "filter_return" +} + </programlisting> + + <warning> + <para>This probably doesn't account for all possible editor backup + files so you may wish to add some additional variations of + <filename>localconfig</filename>. For more information, see + <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"> + bug 186383</ulink> or <ulink + url="http://online.securityfocus.com/bid/6501">Bugtraq ID 6501</ulink>. + </para> + </warning> + + <note> + <para>If you are using webdot from research.att.com (the default + configuration for the <option>webdotbase</option> paramater), you + will need to allow access to <filename>data/webdot/*.dot</filename> + for the reasearch.att.com machine. + </para> + <para>If you are using a local installation of <ulink + url="http://www.graphviz.org">GraphViz</ulink>, you will need to allow + everybody to access <filename>*.png</filename>, + <filename>*.gif</filename>, <filename>*.jpg</filename>, and + <filename>*.map</filename> in the + <filename class="directory">data/webdot</filename> directory. + </para> + </note> + </section> + </section> + <section id="extraconfig"> <title>Optional Additional Configuration</title> @@ -961,20 +1101,9 @@ man 5 crontab <section id="bzldap"> <title>LDAP Authentication</title> - <note> - <para>LDAP authentication has been rewritten for the 2.18 release of - Bugzilla. It no longer requires the Mozilla::LDAP module and now uses - Net::LDAP instead. This rewrite was part of a larger landing that - allowed for additional authentication schemes to be easily added - (<ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=180642">bug - 180642</ulink>). - </para> - <![%bz-devel;[ - <para>This patch originally landed in 21-Mar-2003 and was included - in the 2.17.4 development release. - </para> - ]]> - </note> + <para>LDAP authentication is a module for Bugzilla's plugin + authentication architecture. + </para> <para> The existing authentication @@ -1093,56 +1222,31 @@ man 5 crontab <title>Preventing untrusted Bugzilla content from executing malicious Javascript code</title> - <para>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 + <para>It is possible for a Bugzilla attachment to contain malicious + Javascript + code, which would be executed in the domain of your Bugzilla, thereby + making it possible for the attacker to e.g. steal your login cookies. + Due to internationalization concerns, we are unable to + incorporate by default the code changes necessary to fulfill the CERT + advisory requirements mentioned in <ulink url="http://www.cert.org/tech_tips/malicious_code_mitigation.html/#3"/>. - Making the change below will fix the problem if your installation is for - an English speaking audience. + If your installation is for an English speaking audience only, making the + change below will prevent this problem. </para> - <para>Telling Bugzilla to output a charset as part of the HTTP header is - much easier in version 2.18 and higher<![%bz-devel;[ (including any cvs - pull after 4-May-2003 and development release after 2.17.5)]]> than it was - in previous versions. Simply locate the following line in + <para>Simply locate the following line in <filename>Bugzilla/CGI.pm</filename>: <programlisting> - # Make sure that we don't send any charset headers $self->charset(''); </programlisting> and change it to: <programlisting> - # Send all data using the ISO-8859-1 charset $self->charset('ISO-8859-1'); </programlisting> </para> - - <note> - <para>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. See - <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=126266">bug 126266</ulink> - for more information including progress toward making - bugzilla charset aware by default. - </para> - </note> </section> - <section id="directoryindex" xreflabel="Modifying the Apache - DirectoryIndex parameter to use index.cgi"> - <title> - <filename>directoryindex</filename> for the Bugzilla default page. - </title> - - <para>You should modify the <DirectoryIndex> parameter for - the Apache virtual host running your Bugzilla installation to - allow <filename>index.cgi</filename> as the index page for a - directory, as well as the usual <filename>index.html</filename>, - <filename>index.htm</filename>, and so forth. </para> - </section> - <section id="mod_perl" xreflabel="Bugzilla and mod_perl"> <title> Bugzilla and <filename>mod_perl</filename> @@ -1199,7 +1303,7 @@ man 5 crontab <section id="os-win32"> <title>Microsoft Windows</title> - <para>Making Bugzilla work on windows is still a very painful processes. + <para>Making Bugzilla work on windows is still a painful processes. The Bugzilla Team is working to make it easier, but that goal is not considered a top priority. If you wish to run Bugzilla, we still recommend doing so on a Unix based system such as GNU/Linux. As of this @@ -1259,12 +1363,9 @@ C:\perl> <command>ppm <module name></command> <section id="win32-code-changes"> <title>Code changes required to run on win32</title> - <para>Unfortunately, Bugzilla still doesn't run "out of the box" on - Windows. There is work in progress to make this easier, but until that - happens code will have to be modified. This section is an attempt to - list the required changes. It is an attempt to be all inclusive, but - there may be other changes required. If you find something is missing, - please file a bug in &bzg-bugs;. + <para>As Bugzilla still doesn't run "out of the box" on + Windows, code has to be modified. This section is an attempt to + list the required changes. </para> <section id="win32-code-checksetup"> @@ -1297,8 +1398,8 @@ my $webservergid = '8' <para>To make bug e-mail work on Win32 (until <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=84876">bug 84876</ulink> lands), the - simplest way is to have Net::SMTP installed and change this (in - <filename>Bugzilla/BugMail.pm</filename>):</para> + simplest way is to have the Net::SMTP Perl module installed and + change this:</para> <programlisting> open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") || @@ -1452,217 +1553,270 @@ $smtp->quit; </section> - <section id="http"> - <title>HTTP Server Configuration</title> - - <para>The Bugzilla Team recommends Apache when using Bugzilla, however, any web server - that can be configured to run <glossterm linkend="gloss-cgi">CGI</glossterm> scripts - should be able to handle Bugzilla. No matter what web server you choose, but - especially if you choose something other than Apache, you should be sure to read - <xref linkend="security-access"/>. - </para> - - <para>The plan for this section is to eventually document the specifics of how to lock - down permissions on individual web servers. - </para> - - <section id="http-apache"> - <title>Apache <productname>httpd</productname></title> + <section id="security"> + <title>Bugzilla Security</title> - <para>As mentioned above, the Bugzilla Team recommends Apache for use - with Bugzilla. You will have to make sure that Apache is properly - configured to run the Bugzilla CGI scripts. You also need to make sure - that the <filename>.htaccess</filename> files created by - <command>./checksetup.pl</command> (shown in <xref linkend="http-apache-htaccess"/> - for the curious) are allowed to override Apache's normal access - permissions or else important password information may be exposed to the - Internet. + <warning> + <para>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.</para> + + <para>This is not meant to be a comprehensive list of every possible + security issue pertaining to the software mentioned in this section. + There is + no subsitute for reading the information written by the authors of any + software running on your system. </para> + </warning> + + <section id="security-networking"> + <title>TCP/IP Ports</title> + + <!-- TODO: Make this make sense (TCP/IP) --> + <para>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla + only needs 1, or 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. + </para> + </section> - <para>Many Apache installations are not configured to run scripts - anywhere but in the <filename class="directory">cgi-bin</filename> - directory; however, we recommend that Bugzilla not be installed in the - <filename class="directory">cgi-bin</filename>, otherwise the static - files such as images and <xref linkend="gloss-javascript"/> - will not work correctly. To allow scripts to run in the normal - web space, the following changes should be made to your - <filename>httpd.conf</filename> file. - </para> - - <para>To allow files with a .cgi extension to be run, make sure the - following line exists and is uncommented:</para> - <programlisting> -AddHandler cgi-script .cgi - </programlisting> - - <para>To allow <filename>.htaccess</filename> files to override - permissions and .cgi files to run in the Bugzilla directory, make sure - the following two lines are in a <computeroutput>Directory</computeroutput> - directive that applies to the Bugzilla directory on your system - (either the Bugzilla directory or one of its parents). - </para> - <programlisting> -Options +ExecCGI -AllowOverride Limit - </programlisting> - - <note> - <para>For more information on Apache and its directives, see the - glossary entry on <xref linkend="gloss-apache"/>. - </para> - </note> + <section id="security-mysql"> + <title>MySQL</title> - <example id="http-apache-htaccess"> - <title><filename>.htaccess</filename> files for Apache</title> - - <para><filename>$BUGZILLA_HOME/.htaccess</filename> - <programlisting><![CDATA[ -# don't allow people to retrieve non-cgi executable files or our private data -<FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$> - deny from all -</FilesMatch> -<FilesMatch ^(localconfig.js|localconfig.rdf)$> - allow from all -</FilesMatch> - ]]></programlisting> - </para> + <para>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 <emphasis>not</emphasis> the same as + the system root). Also, many installations default to running + <application>mysqld</application> as the system root. + </para> - <para><filename>$BUGZILLA_HOME/data/.htaccess</filename> - <programlisting><![CDATA[ -# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory; the only exception is duplicates.rdf, which is used by -# duplicates.xul and must be loadable over the web -deny from all -<Files duplicates.rdf> - allow from all -</Files> - ]]></programlisting> + <orderedlist> + <listitem> + <para>Consult the documentation that came with your system for + information on making <application>mysqld</application> run as an + unprivleged user. </para> + </listitem> - <para><filename>$BUGZILLA_HOME/data/webdot</filename> - <programlisting><![CDATA[ -# Restrict access to .dot files to the public webdot server at research.att.com -# if research.att.com ever changed their IP, or if you use a different -# webdot server, you'll need to edit this -<FilesMatch ^[0-9]+\.dot$> - Allow from 192.20.225.10 - Deny from all -</FilesMatch> - -# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and -# .map files -<FilesMatch ^[0-9]+\.(png|gif|jpg|map)$> - Allow from all -</FilesMatch> - -# And no directory listings, either. -Deny from all - ]]></programlisting> + <listitem> + <para>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: </para> - - <para><filename>$BUGZILLA_HOME/Bugzilla/.htaccess</filename> <programlisting> -# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all +<prompt>bash$</prompt> mysql mysql +<prompt>mysql></prompt> DELETE FROM user WHERE user = ''; +<prompt>mysql></prompt> UPDATE user SET password = password('<replaceable>new_password</replaceable>') WHERE user = 'root'; +<prompt>mysql></prompt> FLUSH PRIVILEGES; </programlisting> + <para>From this point forward you will need to use + <command>mysql -u root -p</command> and enter + <replaceable>new_password</replaceable> when prompted when using the + mysql client. </para> + </listitem> - <para><filename>$BUGZILLA_HOME/template/.htaccess</filename> + <listitem> + <para>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 <filename>/etc/my.conf</filename>: + </para> <programlisting> -# nothing in this directory is retrievable unless overriden by an .htaccess -# in a subdirectory -deny from all +[myslqd] +# Prevent network access to MySQL. +skip-networking </programlisting> + </listitem> + + <listitem> + <para>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. </para> + </listitem> - </example> + </orderedlist> </section> - <section id="http-iis"> - <title>Microsoft <productname>Internet Information Services</productname></title> - - <para>If you need, or for some reason even want, to use Microsoft's - <productname>Internet Information Services</productname> or - <productname>Personal Web Server</productname> you should be able - to. You will need to configure them to know how to run CGI scripts, - however. This is described in Microsoft Knowledge Base article - <ulink url="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp">Q245225</ulink> - for <productname>Internet Information Services</productname> and - <ulink url="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp">Q231998</ulink> - for <productname>Personal Web Server</productname>. + <section id="security-daemon"> + <title>Daemon Accounts</title> + + <para>Many daemons, such as Apache's httpd and MySQL's mysqld default to + running as either <quote>root</quote> or <quote>nobody</quote>. Running + as <quote>root</quote> introduces obvious security problems, but the + problems introduced by running everything as <quote>nobody</quote> may + not be so obvious. Basically, if you're running every daemon as + <quote>nobody</quote> and one of them gets compromised, they all get + compromised. For this reason it is recommended that you create a user + account for each daemon. </para> - <para>Also, and this can't be stressed enough, make sure that files such as - <filename>localconfig</filename> and your <filename class="directory">data</filename> - directory are secured as described in <xref linkend="security-access"/>. - </para> + <note> + <para>You will need to set the <varname>webservergroup</varname> to + the group you created for your webserver to run as in + <filename>localconfig</filename>. This will allow + <command>./checksetup.pl</command> to better adjust the file + permissions on your Bugzilla install so as to not require making + anything world-writable. + </para> + </note> </section> - <section id="http-aol"> - <title>AOL Server</title> + <section id="security-access"> + <title>Web Server Access Controls</title> - <para>Ben FrantzDale reported success using AOL Server with Bugzilla. He - reported his experience and what appears below is based on that. + <para>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 laid out, the list of what should and should + not be accessible is rather complicated. </para> - - <para>AOL Server will have to be configured to run - <glossterm linkend="gloss-cgi">CGI</glossterm> scripts, please consult - the documentation that came with your server for more information on - how to do this. + + <para>Users of Apache don't need to worry about this, however, because + Bugzilla ships with .htaccess files which restrict access to all the + sensitive files in this section. Users of other webservers, read on. </para> - <para>Because AOL Server doesn't support <filename>.htaccess</filename> - files, you'll have to create a <glossterm linkend="gloss-tcl">TCL</glossterm> - script. You should create an <filename>aolserver/modules/tcl/filter.tcl</filename> - file (the filename shouldn't matter) with the following contents (change - <computeroutput>/bugzilla/</computeroutput> to the web-based path to - your Bugzilla installation): - </para> + <itemizedlist spacing="compact"> + <listitem> + <para>In the main Bugzilla directory, you should:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block: + <simplelist type="inline"> + <member><filename>*.pl</filename></member> + <member><filename>*localconfig*</filename></member> + <member><filename>runtests.sh</filename></member> + </simplelist> + </para> + </listitem> + <listitem> + <para>But allow: + <simplelist type="inline"> + <member><filename>localconfig.js</filename></member> + <member><filename>localconfig.rdf</filename></member> + </simplelist> + </para> + </listitem> + </itemizedlist> + </listitem> - <programlisting> -ns_register_filter preauth GET /bugzilla/localconfig filter_deny -ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny -ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny -ns_register_filter preauth GET /bugzilla/*.pl filter_deny -ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny -ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny -ns_register_filter preauth GET /bugzilla/data/* filter_deny -ns_register_filter preauth GET /bugzilla/template/* filter_deny - -proc filter_deny { why } { - ns_log Notice "filter_deny" - return "filter_return" -} - </programlisting> + <listitem> + <para>In <filename class="directory">data</filename>:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + <listitem> + <para>But allow: + <simplelist type="inline"> + <member><filename>duplicates.rdf</filename></member> + </simplelist> + </para> + </listitem> + </itemizedlist> + </listitem> - <warning> - <para>This probably doesn't account for all possible editor backup - files so you may wish to add some additional variations of - <filename>localconfig</filename>. For more information, see - <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"> - bug 186383</ulink> or <ulink - url="http://online.securityfocus.com/bid/6501">Bugtraq ID 6501</ulink>. - </para> - </warning> + <listitem> + <para>In <filename class="directory">data/webdot</filename>:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>If you use a remote webdot server:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + <listitem> + <para>But allow + <simplelist type="inline"> + <member><filename>*.dot</filename></member> + </simplelist> + only for the remote webdot server</para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Otherwise, if you use a local GraphViz:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + <listitem> + <para>But allow: + <simplelist type="inline"> + <member><filename>*.png</filename></member> + <member><filename>*.gif</filename></member> + <member><filename>*.jpg</filename></member> + <member><filename>*.map</filename></member> + </simplelist> + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>And if you don't use any dot:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + </listitem> - <note> - <para>If you are using webdot from research.att.com (the default - configuration for the <option>webdotbase</option> paramater), you - will need to allow access to <filename>data/webdot/*.dot</filename> - for the reasearch.att.com machine. + <listitem> + <para>In <filename class="directory">Bugzilla</filename>:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + </itemizedlist> + </listitem> + + <listitem> + <para>In <filename class="directory">template</filename>:</para> + <itemizedlist spacing="compact"> + <listitem> + <para>Block everything</para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + + <para>You should test to make sure that the files mentioned above are + not accessible from the Internet, especially your + <filename>localconfig</filename> 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 + <ulink url="http://bugzilla.mozilla.org/localconfig"/>. You should + get a <errorcode>403</errorcode> <errorname>Forbidden</errorname> + error. + </para> + + <caution> + <para>Not following the instructions in this section, including + testing, may result in sensitive information being globally + accessible. </para> - <para>If you are using a local installation of <ulink - url="http://www.graphviz.org">GraphViz</ulink>, you will need to allow - everybody to access <filename>*.png</filename>, - <filename>*.gif</filename>, <filename>*.jpg</filename>, and - <filename>*.map</filename> in the - <filename class="directory">data/webdot</filename> directory. + </caution> + + <tip> + <para>You should check <xref linkend="http"/> to see if instructions + have been included for your web server. You should also compare those + instructions with this list to make sure everything is properly + accounted for. </para> - </note> + </tip> + </section> + </section> <section id="troubleshooting"> diff --git a/docs/xml/integration.xml b/docs/xml/integration.xml index 65451dc75..598baffca 100644 --- a/docs/xml/integration.xml +++ b/docs/xml/integration.xml @@ -70,7 +70,12 @@ xreflabel="Tinderbox, the Mozilla automated build management system"> <title>Tinderbox/Tinderbox2</title> - <para>We need Tinderbox integration information.</para> + <para>Tinderbox is a continuous-build system which can integrate with + Bugzilla - see + <ulink url="http://www.mozilla.org/projects/tinderbox"/> for details + of Tinderbox, and + <ulink url="http://tinderbox.mozilla.org/showbuilds.cgi"/> to see it + in action.</para> </section> </section> diff --git a/docs/xml/introduction.xml b/docs/xml/introduction.xml index 8b09fe2b5..d01e39979 100644 --- a/docs/xml/introduction.xml +++ b/docs/xml/introduction.xml @@ -1,23 +1,44 @@ <chapter id="introduction"> <title>Introduction</title> - <section id="whatis"> + <section id="what-is-bugzilla"> <title>What is Bugzilla?</title> <para> 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. + of outstanding problems with their products. </para> + + <para><emphasis>Do we need more here?</emphasis></para> + + </section> + + <section id="why-tracking"> + <title>Why use a bug-tracking system?</title> + + <para>For many years, defect-tracking software was principally + the domain of large software development houses. Most smaller shops + simply relied on + shared lists and email to monitor the status of defects. This procedure + was error-prone and tended to cause those bugs judged least significant by + developers to be dropped or ignored.</para> + + <para>Integrated + defect-tracking systems reduce downtime, increase productivity, and raise + customer satisfaction with their systems. Along with full disclosure, an + open bug-tracker allows you to keep in touch with your 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 method for accounting for unusual system or software + issues.</para> + + </section> + + <section id="why-bugzilla"> + <title>Why use Bugzilla?</title> <para>Bugzilla boasts many advanced features. These include: <itemizedlist> @@ -71,34 +92,7 @@ </listitem> </itemizedlist> </para> - </section> - - <section id="why"> - <title>Why Should We Use Bugzilla?</title> - - <para>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.</para> - - <para>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.</para> - - <para>But why should - <emphasis>you</emphasis> - - use Bugzilla?</para> - + <para>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 @@ -110,20 +104,6 @@ <ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems.</para> - - <para>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 - <emphasis>something</emphasis> - 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.</para> - - <para>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.</para> </section> </chapter> diff --git a/docs/xml/patches.xml b/docs/xml/patches.xml index b8c068fac..6b755cbce 100644 --- a/docs/xml/patches.xml +++ b/docs/xml/patches.xml @@ -1,52 +1,15 @@ <!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> <appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla"> - <title>Useful Patches and Utilities for Bugzilla</title> + <title>Contrib</title> - <para>Are you looking for a way to put your Bugzilla into overdrive? Catch - some of the niftiest tricks here in this section.</para> - - <section id="rewrite" xreflabel="Apache mod_rewrite magic"> - <title>Apache - <filename>mod_rewrite</filename> - - magic</title> - - <para>Apache's - <filename>mod_rewrite</filename> - - module lets you do some truly amazing things with URL rewriting. Here are - a couple of examples of what you can do.</para> - - <orderedlist> - <listitem> - <para>Make it so if someone types - <computeroutput>http://www.foo.com/12345</computeroutput> - - , Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try - setting up your VirtualHost section for Bugzilla with a rule like - this:</para> - - <programlisting><![CDATA[ -<VirtualHost 12.34.56.78> -RewriteEngine On -RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] -</VirtualHost> -]]></programlisting> - </listitem> - - <listitem> - <para>There are many, many more things you can do with mod_rewrite. - Please refer to the mod_rewrite documentation at - <ulink url="http://www.apache.org"/>. - </para> - </listitem> - </orderedlist> - </section> + <para>There are a number of unofficial Bugzilla add-ons in the + <filename class="directory">$BUGZILLA_ROOT/contrib/</filename> + directory. This section documents them.</para> <section id="cmdline"> - <title>Command-line Bugzilla Queries</title> + <title>Command-line Search Interface</title> - <para>There are a suite of Unix utilities for querying Bugzilla from the + <para>There are a suite of Unix utilities for searching Bugzilla from the command line. They live in the <filename class="directory">contrib/cmdline</filename> directory. However, they diff --git a/docs/xml/using.xml b/docs/xml/using.xml index f06969f57..21614e740 100644 --- a/docs/xml/using.xml +++ b/docs/xml/using.xml @@ -3,468 +3,461 @@ <chapter id="using"> <title>Using Bugzilla</title> - <section id="how"> - <title>How do I use Bugzilla?</title> - - <para>This section contains information for end-users of Bugzilla. - There is a Bugzilla test installation, called - <ulink url="http://landfill.bugzilla.org/">Landfill</ulink>, - 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.</para> - - <section id="myaccount"> - <title>Create a Bugzilla Account</title> - - <para>If you want to use Bugzilla, first you need to create an account. - Consult with the administrator responsible for your installation of - Bugzilla for the URL you should use to access it. If you're - test-driving Bugzilla, use this URL: - <ulink url="http://landfill.bugzilla.org/bugzilla-tip/"/>. - </para> - - <orderedlist> - <listitem> - <para>Click the - <quote>Open a new Bugzilla account</quote> - - link, enter your email address and, optionally, your name in the - spaces provided, then click - <quote>Create Account</quote> - - .</para> - </listitem> - - <listitem> - <para>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.</para> - </listitem> - - <listitem> - <para>Click the - <quote>Log In</quote> - 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 - <quote>Login</quote>. - </para> - - </listitem> - </orderedlist> - - <para>You are now logged in. Bugzilla uses cookies for authentication - so, unless your IP address changes, you should not have to log in - again.</para> - </section> + <para>This section contains information for end-users of Bugzilla. + There is a Bugzilla test installation, called + <ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>, + which you are welcome to play with (if it's up.) + However, it does not necessarily + have all Bugzilla features enabled, and runs an up-to-the-minute version, + so some things may not quite work as this document describes.</para> + + <section id="myaccount"> + <title>Create a Bugzilla Account</title> + + <para>If you want to use Bugzilla, first you need to create an account. + Consult with the administrator responsible for your installation of + Bugzilla for the URL you should use to access it. If you're + test-driving Bugzilla, use this URL: + <ulink url="http://landfill.bugzilla.org/bugzilla-tip/"/>. + </para> + + <orderedlist> + <listitem> + <para>Click the + <quote>Open a new Bugzilla account</quote> + + link, enter your email address and, optionally, your name in the + spaces provided, then click + <quote>Create Account</quote> + + .</para> + </listitem> + + <listitem> + <para>Within moments, you should receive an email to the address + you provided, which contains your login name (generally the + same as the email address), and a password. + This password is randomly generated, but can be + changed to something more memorable.</para> + </listitem> + + <listitem> + <para>Click the + <quote>Log In</quote> + link in the footer at the bottom of the page in your browser, + enter your email address and password into the spaces provided, and + click + <quote>Login</quote>. + </para> + + </listitem> + </orderedlist> + + <para>You are now logged in. Bugzilla uses cookies to remember you are + logged in so, unless you have cookies disabled or your IP address changes, + you should not have to log in again.</para> + </section> - <section id="bug_page"> - <title>Anatomy of a Bug</title> - - <para>The core of Bugzilla is the screen which displays a particular - bug. It's a good place to explain some Bugzilla concepts. - <ulink - url="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"> - Bug 1 on Landfill</ulink> - - 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.</para> - - <orderedlist> - <listitem> - <para> - <emphasis>Product and Component</emphasis>: - Bugs are divided up by Product and Component, with a Product - having one or more Components in it. For example, - bugzilla.mozilla.org's "Bugzilla" Product is composed of several - Components: - <simplelist> - <member> - <emphasis>Administration:</emphasis> - Administration of a Bugzilla installation.</member> - - <member> - <emphasis>Bugzilla-General:</emphasis> - Anything that doesn't fit in the other components, or spans - multiple components.</member> - - <member> - <emphasis>Creating/Changing Bugs:</emphasis> - Creating, changing, and viewing bugs.</member> - - <member> - <emphasis>Documentation:</emphasis> - The Bugzilla documentation, including The Bugzilla Guide.</member> - - <member> - <emphasis>Email:</emphasis> - Anything to do with email sent by Bugzilla.</member> - - <member> - <emphasis>Installation:</emphasis> - The installation process of Bugzilla.</member> - - <member> - <emphasis>Query/Buglist:</emphasis> - Anything to do with searching for bugs and viewing the - buglists.</member> - - <member> - <emphasis>Reporting/Charting:</emphasis> - Getting reports from Bugzilla.</member> - - <member> - <emphasis>User Accounts:</emphasis> - Anything about managing a user account from the user's perspective. - Saved queries, creating accounts, changing passwords, logging in, - etc.</member> - - <member> - <emphasis>User Interface:</emphasis> - General issues having to do with the user interface cosmetics (not - functionality) including cosmetic issues, HTML templates, - etc.</member> - </simplelist> - </para> - </listitem> - - <listitem> - <para> - <emphasis>Status and Resolution:</emphasis> - - 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.</para> - </listitem> - - <listitem> - <para> - <emphasis>Assigned To:</emphasis> - The person responsible for fixing the bug.</para> - </listitem> - - <listitem> - <para> - <emphasis>*URL:</emphasis> - A URL associated with the bug, if any.</para> - </listitem> - - <listitem> - <para> - <emphasis>Summary:</emphasis> - A one-sentence summary of the problem.</para> - </listitem> - - <listitem> - <para> - <emphasis>*Status Whiteboard:</emphasis> - (a.k.a. Whiteboard) A free-form text area for adding short notes - and tags to a bug.</para> - </listitem> - - <listitem> - <para> - <emphasis>*Keywords:</emphasis> - The administrator can define keywords which you can use to tag and - categorise bugs - e.g. The Mozilla Project has keywords like crash - and regression.</para> - </listitem> - - <listitem> - <para> - <emphasis>Platform and OS:</emphasis> - These indicate the computing environment where the bug was - found.</para> - </listitem> - - <listitem> - <para> - <emphasis>Version:</emphasis> - The "Version" field is usually used for versions of a product which - have been released, and is set to indicate which versions of a - Component have the particular problem the bug report is - about.</para> - </listitem> - - <listitem> - <para> - <emphasis>Priority:</emphasis> - The bug assignee uses this field to prioritise his or her bugs. - It's a good idea not to change this on other people's bugs.</para> - </listitem> - - <listitem> - <para> - <emphasis>Severity:</emphasis> - This indicates how severe the problem is - from blocker - ("application unusable") to trivial ("minor cosmetic issue"). You - can also use this field to indicate whether a bug is an enhancement - request.</para> - </listitem> - - <listitem> - <para> - <emphasis>*Target:</emphasis> - (a.k.a. Target Milestone) A future version by which the bug is to - be fixed. e.g. The Bugzilla Project's milestones for future - Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not - restricted to numbers, thought - you can use any text strings, such - as dates.</para> - </listitem> - - <listitem> - <para> - <emphasis>Reporter:</emphasis> - The person who filed the bug.</para> - </listitem> - - <listitem> - <para> - <emphasis>CC list:</emphasis> - A list of people who get mail when the bug changes.</para> - </listitem> - - <listitem> - <para> - <emphasis>Attachments:</emphasis> - You can attach files (e.g. testcases or patches) to bugs. If there - are any attachments, they are listed in this section.</para> - </listitem> - - <listitem> - <para> - <emphasis>*Dependencies:</emphasis> - If this bug cannot be fixed unless other bugs are fixed (depends - on), or this bug stops other bugs being fixed (blocks), their - numbers are recorded here.</para> - </listitem> - - <listitem> - <para> - <emphasis>*Votes:</emphasis> - Whether this bug has any votes.</para> - </listitem> - - <listitem> - <para> - <emphasis>Additional Comments:</emphasis> - You can add your two cents to the bug discussion here, if you have - something worthwhile to say.</para> - </listitem> - </orderedlist> - </section> + <section id="bug_page"> + <title>Anatomy of a Bug</title> + + <para>The core of Bugzilla is the screen which displays a particular + bug. It's a good place to explain some Bugzilla concepts. + <ulink + url="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"> + Bug 1 on Landfill</ulink> + + 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.</para> + + <orderedlist> + <listitem> + <para> + <emphasis>Product and Component</emphasis>: + Bugs are divided up by Product and Component, with a Product + having one or more Components in it. For example, + bugzilla.mozilla.org's "Bugzilla" Product is composed of several + Components: + <simplelist> + <member> + <emphasis>Administration:</emphasis> + Administration of a Bugzilla installation.</member> - <section id="query"> - <title>Searching for Bugs</title> + <member> + <emphasis>Bugzilla-General:</emphasis> + Anything that doesn't fit in the other components, or spans + multiple components.</member> - <para>The Bugzilla Search page is is the interface where you can find - any bug report, comment, or patch currently in the Bugzilla system. You - can play with it here: - <ulink url="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"/>.</para> + <member> + <emphasis>Creating/Changing Bugs:</emphasis> + Creating, changing, and viewing bugs.</member> - <para>The Search page has controls for selecting different possible - values for all of the fields in a bug, as described above. For some - fields, multiple values can be selected. In those cases, Bugzilla - returns bugs where the content of the field matches one of the selected - values. If none is selected, then the field can take any value.</para> - - <para>Once you've defined a search, you can either run it, or save it - as a Remembered Query, which can optionally appear in the footer of - your pages.</para> + <member> + <emphasis>Documentation:</emphasis> + The Bugzilla documentation, including The Bugzilla Guide.</member> - <para>Highly advanced querying is done using Boolean Charts.</para> - </section> + <member> + <emphasis>Email:</emphasis> + Anything to do with email sent by Bugzilla.</member> - <section id="list"> - <title>Bug Lists</title> + <member> + <emphasis>Installation:</emphasis> + The installation process of Bugzilla.</member> - <para>If you run a search, a list of matching bugs will be returned. - The default search is to return all open bugs on the system - don't try - running this search on a Bugzilla installation with a lot of - bugs!</para> + <member> + <emphasis>Query/Buglist:</emphasis> + Anything to do with searching for bugs and viewing the + buglists.</member> - <para>The format of the list is configurable. For example, it can be - sorted by clicking the column headings. Other useful features can be - accessed using the links at the bottom of the list: - <simplelist> <member> - <emphasis>Long Format:</emphasis> + <emphasis>Reporting/Charting:</emphasis> + Getting reports from Bugzilla.</member> - this gives you a large page with a non-editable summary of the fields - of each bug.</member> + <member> + <emphasis>User Accounts:</emphasis> + Anything about managing a user account from the user's perspective. + Saved queries, creating accounts, changing passwords, logging in, + etc.</member> <member> - <emphasis>Change Columns:</emphasis> + <emphasis>User Interface:</emphasis> + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, + etc.</member> + </simplelist> + </para> + </listitem> + + <listitem> + <para> + <emphasis>Status and Resolution:</emphasis> + + 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.</para> + </listitem> + + <listitem> + <para> + <emphasis>Assigned To:</emphasis> + The person responsible for fixing the bug.</para> + </listitem> + + <listitem> + <para> + <emphasis>*URL:</emphasis> + A URL associated with the bug, if any.</para> + </listitem> + + <listitem> + <para> + <emphasis>Summary:</emphasis> + A one-sentence summary of the problem.</para> + </listitem> + + <listitem> + <para> + <emphasis>*Status Whiteboard:</emphasis> + (a.k.a. Whiteboard) A free-form text area for adding short notes + and tags to a bug.</para> + </listitem> + + <listitem> + <para> + <emphasis>*Keywords:</emphasis> + The administrator can define keywords which you can use to tag and + categorise bugs - e.g. The Mozilla Project has keywords like crash + and regression.</para> + </listitem> + + <listitem> + <para> + <emphasis>Platform and OS:</emphasis> + These indicate the computing environment where the bug was + found.</para> + </listitem> + + <listitem> + <para> + <emphasis>Version:</emphasis> + The "Version" field is usually used for versions of a product which + have been released, and is set to indicate which versions of a + Component have the particular problem the bug report is + about.</para> + </listitem> + + <listitem> + <para> + <emphasis>Priority:</emphasis> + The bug assignee uses this field to prioritise his or her bugs. + It's a good idea not to change this on other people's bugs.</para> + </listitem> + + <listitem> + <para> + <emphasis>Severity:</emphasis> + This indicates how severe the problem is - from blocker + ("application unusable") to trivial ("minor cosmetic issue"). You + can also use this field to indicate whether a bug is an enhancement + request.</para> + </listitem> + + <listitem> + <para> + <emphasis>*Target:</emphasis> + (a.k.a. Target Milestone) A future version by which the bug is to + be fixed. e.g. The Bugzilla Project's milestones for future + Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not + restricted to numbers, thought - you can use any text strings, such + as dates.</para> + </listitem> + + <listitem> + <para> + <emphasis>Reporter:</emphasis> + The person who filed the bug.</para> + </listitem> + + <listitem> + <para> + <emphasis>CC list:</emphasis> + A list of people who get mail when the bug changes.</para> + </listitem> + + <listitem> + <para> + <emphasis>Attachments:</emphasis> + You can attach files (e.g. testcases or patches) to bugs. If there + are any attachments, they are listed in this section.</para> + </listitem> + + <listitem> + <para> + <emphasis>*Dependencies:</emphasis> + If this bug cannot be fixed unless other bugs are fixed (depends + on), or this bug stops other bugs being fixed (blocks), their + numbers are recorded here.</para> + </listitem> + + <listitem> + <para> + <emphasis>*Votes:</emphasis> + Whether this bug has any votes.</para> + </listitem> + + <listitem> + <para> + <emphasis>Additional Comments:</emphasis> + You can add your two cents to the bug discussion here, if you have + something worthwhile to say.</para> + </listitem> + </orderedlist> + </section> - change the bug attributes which appear in the list.</member> + <section id="query"> + <title>Searching for Bugs</title> - <member> - <emphasis>Change several bugs at once:</emphasis> + <para>The Bugzilla Search page is is the interface where you can find + any bug report, comment, or patch currently in the Bugzilla system. You + can play with it here: + <ulink url="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"/>.</para> - If your account is sufficiently empowered, you can make the same - change to all the bugs in the list - for example, changing their - owner.</member> + <para>The Search page has controls for selecting different possible + values for all of the fields in a bug, as described above. For some + fields, multiple values can be selected. In those cases, Bugzilla + returns bugs where the content of the field matches any one of the selected + values. If none is selected, then the field can take any value.</para> - <member> - <emphasis>Send mail to bug owners:</emphasis> + <para>Once you've run a search, you can save it as a Saved Search, which + appears in the page footer.</para> + + <para>Highly advanced querying is done using Boolean Charts. See the + Boolean Charts help link on the Search page for more information.</para> + </section> - Sends mail to the owners of all bugs on the list.</member> + <section id="list"> + <title>Bug Lists</title> - <member> - <emphasis>Edit this query:</emphasis> + <para>If you run a search, a list of matching bugs will be returned. + </para> - 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.</member> - </simplelist> - </para> - </section> + <para>The format of the list is configurable. For example, it can be + sorted by clicking the column headings. Other useful features can be + accessed using the links at the bottom of the list: + <simplelist> + <member> + <emphasis>Long Format:</emphasis> - <section id="bugreports"> - <title>Filing Bugs</title> + this gives you a large page with a non-editable summary of the fields + of each bug.</member> + + <member> + <emphasis>Change Columns:</emphasis> - <para>Years of bug writing experience has been distilled for your - reading pleasure into the - <ulink - url="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"> - Bug Writing Guidelines</ulink>. - While some of the advice is Mozilla-specific, the basic principles of - reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the - Hardware Platform, and Operating System you were using at the time of - the failure go a long way toward ensuring accurate, responsible fixes - for the bug that bit you.</para> - - <para>The procedure for filing a test bug is as follows:</para> - - <orderedlist> - <listitem> - <para>Go to - <ulink url="http://landfill.bugzilla.org/bugzilla-tip/"> - Landfill</ulink> - in your browser and click - <ulink - url="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"> - Enter a new bug report</ulink>. - </para> - </listitem> - - <listitem> - <para>Select a product - any one will do.</para> - </listitem> - - <listitem> - <para>Fill in the fields. Bugzilla should have made reasonable - guesses, based upon your browser, for the "Platform" and "OS" - drop-down boxes. If they are wrong, change them.</para> - </listitem> - - <listitem> - <para>Select "Commit" and send in your bug report.</para> - </listitem> - </orderedlist> + change the bug attributes which appear in the list.</member> + + <member> + <emphasis>Change several bugs at once:</emphasis> + + If your account is sufficiently empowered, you can make the same + change to all the bugs in the list - for example, changing their + owner.</member> + + <member> + <emphasis>Send mail to bug owners:</emphasis> + + Sends mail to the owners of all bugs on the list.</member> + + <member> + <emphasis>Edit this query:</emphasis> + + If you didn't get exactly the results you were looking for, you can + return to the Query page through this link and make small revisions + to the query you just made so you get more accurate results.</member> + </simplelist> + </para> + </section> + + <section id="bugreports"> + <title>Filing Bugs</title> + + <para>Years of bug writing experience has been distilled for your + reading pleasure into the + <ulink + url="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"> + Bug Writing Guidelines</ulink>. + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you.</para> + + <para>The procedure for filing a test bug is as follows:</para> + + <orderedlist> + <listitem> + <para>Go to + <ulink url="http://landfill.bugzilla.org/bugzilla-tip/"> + Landfill</ulink> + in your browser and click + <ulink + url="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"> + Enter a new bug report</ulink>. + </para> + </listitem> + + <listitem> + <para>Select a product - any one will do.</para> + </listitem> + + <listitem> + <para>Fill in the fields. Bugzilla should have made reasonable + guesses, based upon your browser, for the "Platform" and "OS" + drop-down boxes. If they are wrong, change them.</para> + </listitem> + + <listitem> + <para>Select "Commit" and send in your bug report.</para> + </listitem> + </orderedlist> + </section> + + <section id="patchviewer"> + <title>Patch Viewer</title> + + <para>Viewing and reviewing patches in Bugzilla is often difficult due to + lack of context, improper format and the inherent readability issues that + raw patches present. Patch Viewer is an enhancement to Bugzilla designed + to fix that by offering increased context, linking to sections, and + integrating with Bonsai, LXR and CVS.</para> + + <para>Patch viewer allows you to:</para> + + <simplelist> + <member>View patches in color, with side-by-side view rather than trying + to interpret the contents of the patch.</member> + <member>See the difference between two patches.</member> + <member>Get more context in a patch.</member> + <member>Collapse and expand sections of a patch for easy + reading.</member> + <member>Link to a particular section of a patch for discussion or + review</member> + <member>Go to Bonsai or LXR to see more context, blame, and + cross-references for the part of the patch you are looking at</member> + <member>Create a rawtext unified format diff out of any patch, no + matter what format it came from</member> + </simplelist> + + <section id="patchviewer_view"> + <title>Viewing Patches in Patch Viewer</title> + <para>The main way to view a patch in patch viewer is to click on the + "Diff" link next to a patch in the Attachments list on a bug. You may + also do this within the edit window by clicking the "View Attachment As + Diff" button in the Edit Attachment screen.</para> </section> - <section id="patchviewer"> - <title>Patch Viewer</title> + <section id="patchviewer_diff"> + <title>Seeing the Difference Between Two Patches</title> + <para>To see the difference between two patches, you must first view the + newer patch in Patch Viewer. Then select the older patch from the + dropdown at the top of the page ("Differences between [dropdown] and + this patch") and click the "Diff" button. This will show you what + is new or changed in the newer patch.</para> + </section> - <para>Viewing and reviewing patches in Bugzilla is often difficult due to - lack of context, improper format and the inherent readability issues that - raw patches present. Patch Viewer is an enhancement to Bugzilla designed - to fix that by offering increased context, linking to sections, and - integrating with Bonsai, LXR and CVS.</para> + <section id="patchviewer_context"> + <title>Getting More Context in a Patch</title> + <para>To get more context in a patch, you put a number in the textbox at + the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. + This will give you that many lines of context before and after each + change. Alternatively, you can click on the "File" link there and it + will show each change in the full context of the file. This feature only + works against files that were diffed using "cvs diff".</para> + </section> - <para>Patch viewer allows you to:</para> + <section id="patchviewer_collapse"> + <title>Collapsing and Expanding Sections of a Patch</title> + <para>To view only a certain set of files in a patch (for example, if a + patch is absolutely huge and you want to only review part of it at a + time), you can click the "(+)" and "(-)" links next to each file (to + expand it or collapse it). If you want to collapse all files or expand + all files, you can click the "Collapse All" and "Expand All" links at the + top of the page.</para> + </section> - <simplelist> - <member>View patches in color, with side-by-side view rather than trying - to interpret the contents of the patch.</member> - <member>See the difference between two patches.</member> - <member>Get more context in a patch.</member> - <member>Collapse and expand sections of a patch for easy - reading.</member> - <member>Link to a particular section of a patch for discussion or - review</member> - <member>Go to Bonsai or LXR to see more context, blame, and - cross-references for the part of the patch you are looking at</member> - <member>Create a rawtext unified format diff out of any patch, no - matter what format it came from</member> - </simplelist> + <section id="patchviewer_link"> + <title>Linking to a Section of a Patch</title> + <para>To link to a section of a patch (for example, if you want to be + able to give someone a URL to show them which part you are talking + about) you simply click the "Link Here" link on the section header. The + resulting URL can be copied and used in discussion. (Copy Link + Location in Mozilla works as well.)</para> + </section> - <section id="patchviewer_view"> - <title>Viewing Patches in Patch Viewer</title> - <para>The main way to view a patch in patch viewer is to click on the - "Diff" link next to a patch in the Attachments list on a bug. You may - also do this within the edit window by clicking the "View Attachment As - Diff" button in the Edit Attachment screen.</para> - </section> - - <section id="patchviewer_diff"> - <title>Seeing the Difference Between Two Patches</title> - <para>To see the difference between two patches, you must first view the - newer patch in Patch Viewer. Then select the older patch from the - dropdown at the top of the page ("Differences between [dropdown] and - this patch") and click the "Diff" button. This will show you what - is new or changed in the newer patch.</para> - </section> - - <section id="patchviewer_context"> - <title>Getting More Context in a Patch</title> - <para>To get more context in a patch, you put a number in the textbox at - the top of Patch Viewer ("Patch / File / [textbox]") and hit enter. - This will give you that many lines of context before and after each - change. Alternatively, you can click on the "File" link there and it - will show each change in the full context of the file. This feature only - works against files that were diffed using "cvs diff".</para> - </section> - - <section id="patchviewer_collapse"> - <title>Collapsing and Expanding Sections of a Patch</title> - <para>To view only a certain set of files in a patch (for example, if a - patch is absolutely huge and you want to only review part of it at a - time), you can click the "(+)" and "(-)" links next to each file (to - expand it or collapse it). If you want to collapse all files or expand - all files, you can click the "Collapse All" and "Expand All" links at the - top of the page.</para> - </section> - - <section id="patchviewer_link"> - <title>Linking to a Section of a Patch</title> - <para>To link to a section of a patch (for example, if you want to be - able to give someone a URL to show them which part you are talking - about) you simply click the "Link Here" link on the section header. The - resulting URL can be copied and used in discussion. (Copy Link - Location in Mozilla works as well.)</para> - </section> - - <section id="patchviewer_bonsai_lxr"> - <title>Going to Bonsai and LXR</title> - <para>To go to Bonsai to get blame for the lines you are interested in, - you can click the "Lines XX-YY" link on the section header you are - interested in. This works even if the patch is against an old - version of the file, since Bonsai stores all versions of the file.</para> - - <para>To go to LXR, you click on the filename on the file header - (unfortunately, since LXR only does the most recent version, line - numbers are likely to rot).</para> - </section> - - <section id="patchviewer_unified_diff"> - <title>Creating a Unified Diff</title> - <para>If the patch is not in a format that you like, you can turn it - into a unified diff format by clicking the "Raw Unified" link at the top - of the page.</para> - </section> + <section id="patchviewer_bonsai_lxr"> + <title>Going to Bonsai and LXR</title> + <para>To go to Bonsai to get blame for the lines you are interested in, + you can click the "Lines XX-YY" link on the section header you are + interested in. This works even if the patch is against an old + version of the file, since Bonsai stores all versions of the file.</para> + + <para>To go to LXR, you click on the filename on the file header + (unfortunately, since LXR only does the most recent version, line + numbers are likely to rot).</para> + </section> + <section id="patchviewer_unified_diff"> + <title>Creating a Unified Diff</title> + <para>If the patch is not in a format that you like, you can turn it + into a unified diff format by clicking the "Raw Unified" link at the top + of the page.</para> </section> + </section> <section id="hintsandtips"> @@ -475,15 +468,16 @@ <section> <title>Autolinkification</title> - <para>Bugzilla comments are plain text - so posting HTML will result - in literal HTML tags rather than being interpreted by a browser. + <para>Bugzilla comments are plain text - so typing <U> will + produce less-than, U, greater-than rather than underlined text. 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" will be turned into a link: <ulink url="http://www.bugzilla.org"/>. Other strings which get linkified in the obvious manner are: <simplelist> <member>bug 12345</member> + <member>comment 7</member> <member>bug 23456, comment 53</member> <member>attachment 4321</member> <member>mailto:george@example.com</member> @@ -532,7 +526,7 @@ <para> 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 + if you do it out of habit, but full mail/news-style four line ASCII art creations are not. </para> </section> @@ -586,7 +580,7 @@ <para>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:</para> + The preferences are split into three tabs:</para> <section id="accountsettings" xreflabel="Account Settings"> <title>Account Settings</title> @@ -608,9 +602,16 @@ <para>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.)</para> + the bug and the change that was made to it. + </para> + + <para> + You can also do further filtering on the client side by + using the X-Bugzilla-Reason mail header which Bugzilla + adds to all bugmail. This tells you what relationship you have to the + bug in question, + and can be any of Owner, Reporter, QAcontact, CClist, Voter and + WatchingComponent.</para> <para>By entering user email names, delineated by commas, into the "Users to watch" text entry box you can receive a copy of all the @@ -625,15 +626,6 @@ </note> </section> - <section id="footersettings"> - <title>Page Footer</title> - - <para>On the Search page, you can store queries in Bugzilla, so if you - regularly run a particular query it is just a drop-down menu away. - Once you have a stored query, you can come - here to request that it also be displayed in your page footer.</para> - </section> - <section id="permissionsettings"> <title>Permissions</title> @@ -643,6 +635,11 @@ functions.</para> </section> </section> + <section id="reporting"> + <title>Reports</title> + <para><emphasis>To be written</emphasis></para> + </section> + </chapter> <!-- Keep this comment at the end of the file diff --git a/docs/xml/variants.xml b/docs/xml/variants.xml deleted file mode 100644 index 4f1d2be18..000000000 --- a/docs/xml/variants.xml +++ /dev/null @@ -1,114 +0,0 @@ -<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">--> -<appendix id="variants" xreflabel="Bugzilla Variants and Competitors"> - <title>Bugzilla Variants and Competitors</title> - - <para>I created this section to answer questions about Bugzilla competitors - and variants, then found a wonderful site which covers an awful lot of what - I wanted to discuss. Rather than quote it in its entirety, I'll simply - refer you here: - <ulink url="http://linas.org/linux/pm.html"/>. - </para> - - <section id="variant-redhat"> - <title>Red Hat Bugzilla</title> - - <para>Red Hat's old fork of Bugzilla which was based on version 2.8 is now - obsolete. The newest version in use is based on version 2.17.1 and is in - the process of being integrated into the main Bugzilla source tree. The - back-end is modified to work with PostgreSQL instead of MySQL and they have - custom templates to get their desired look and feel, but other than that it - is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of - effort to make sure that the changes he made could be integrated back into - the main tree. - <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=98304">Bug 98304</ulink> - exists to track this integration. - </para> - - <para>URL: <ulink url="http://bugzilla.redhat.com/bugzilla/"/> - </para> - - <para>This section last updated 24 Dec 2002</para> - </section> - - <section id="variant-fenris"> - <title>Loki Bugzilla (Fenris)</title> - - <para>Fenris was a fork from Bugzilla made by Loki Games; when - Loki went into receivership, it died. While Loki's other code lives on, - its custodians recommend Bugzilla for future bug-tracker deployments. - </para> - - <para>This section last updated 27 Jul 2002</para> - </section> - - <section id="variant-issuezilla"> - <title>Issuezilla</title> - - <para>Issuezilla was another fork from Bugzilla, made by collab.net and - hosted at tigris.org. It is also dead; the primary focus of bug-tracking - at tigris.org is their Java-based bug-tracker, - <xref linkend="variant-scarab"/>.</para> - - <para>This section last updated 27 Jul 2002</para> - </section> - - <section id="variant-scarab"> - <title>Scarab</title> - - <para>Scarab is a new open source bug-tracking system built using Java - Servlet technology. It is currently at version 1.0 beta 13.</para> - - <para>URL: <ulink url="http://scarab.tigris.org/"/> - </para> - - <para>This section last updated 18 Jan 2003</para> - </section> - - <section id="variant-perforce"> - <title>Perforce SCM</title> - - <para>Although Perforce isn't really a bug tracker, it can be used as - such through the <quote>jobs</quote> - functionality.</para> - - <para>URL: <ulink url="http://www.perforce.com/perforce/technotes/note052.html"/> - </para> - - <para>This section last updated 27 Jul 2002</para> - </section> - - <section id="variant-sourceforge"> - <title>SourceForge</title> - - <para>SourceForge is a way of coordinating geographically - distributed free software and open source projects over the Internet. - It has a built-in bug tracker, but it's not highly thought of.</para> - - <para>URL: <ulink url="http://www.sourceforge.net"/> - </para> - - <para>This section last updated 27 Jul 2002</para> - </section> -</appendix> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-always-quote-attributes:t -sgml-auto-insert-required-elements:t -sgml-balanced-tag-edit:t -sgml-exposed-tags:nil -sgml-general-insert-case:lower -sgml-indent-data:t -sgml-indent-step:2 -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -sgml-minimize-attributes:nil -sgml-namecase-general:t -sgml-omittag:t -sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") -sgml-shorttag:t -sgml-tag-region-if-active:t -End: ---> - |