Google Git
Sign in
webkit / WebKit / refs/heads/Safari-3-1-branch / . / BugsSite / docs / html / faq.html
blob: c2d11f6d8e68c6804ff843e41ba2cc6cb7e909ac [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>The Bugzilla FAQ</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 2.20.1
Release"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Whining"
HREF="whining.html"><LINK
REL="NEXT"
TITLE="Troubleshooting"
HREF="troubleshooting.html"></HEAD
><BODY
CLASS="appendix"
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.20.1
Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="whining.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="faq"
></A
>Appendix A. The Bugzilla FAQ</H1
><P
>&#13; This FAQ includes questions not covered elsewhere in the Guide.
</P
><DIV
CLASS="qandaset"
><DL
><DT
>1. <A
HREF="faq.html#faq-general"
>General Questions</A
></DT
><DD
><DL
><DT
>A.1.1. <A
HREF="faq.html#faq-general-license"
>&#13; What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.2. <A
HREF="faq.html#faq-general-support"
>&#13; How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.3. <A
HREF="faq.html#faq-general-companies"
>&#13; What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.4. <A
HREF="faq.html#faq-general-maintainers"
>&#13; Who maintains Bugzilla?
</A
></DT
><DT
>A.1.5. <A
HREF="faq.html#faq-general-compare"
>&#13; How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.6. <A
HREF="faq.html#faq-general-bzmissing"
>&#13; Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</A
></DT
><DT
>A.1.7. <A
HREF="faq.html#faq-general-mysql"
>&#13; Why MySQL? I'm interested in seeing Bugzilla run on
PostgreSQL/Sybase/Oracle/Msql/MSSQL.
</A
></DT
><DT
>A.1.8. <A
HREF="faq.html#faq-general-bonsaitools"
>&#13; What is <TT
CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
>?
</A
></DT
><DT
>A.1.9. <A
HREF="faq.html#faq-general-perlpath"
>&#13; My perl is located at <TT
CLASS="filename"
>/usr/local/bin/perl</TT
>
and not <TT
CLASS="filename"
>/usr/bin/perl</TT
>. Is there an easy
to change that in all the files that have this hard-coded?
</A
></DT
><DT
>A.1.10. <A
HREF="faq.html#faq-general-cookie"
>&#13; Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DT
>A.1.11. <A
HREF="faq.html#faq-mod-perl"
>&#13; Does bugzilla run under <TT
CLASS="filename"
>mod_perl</TT
>?
</A
></DT
></DL
></DD
><DT
>2. <A
HREF="faq.html#faq-phb"
>Managerial Questions</A
></DT
><DD
><DL
><DT
>A.2.1. <A
HREF="faq.html#faq-phb-client"
>&#13; Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</A
></DT
><DT
>A.2.2. <A
HREF="faq.html#faq-phb-priorities"
>&#13; 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?
</A
></DT
><DT
>A.2.3. <A
HREF="faq.html#faq-phb-reporting"
>&#13; 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.4. <A
HREF="faq.html#faq-phb-email"
>&#13; Is there email notification? If so, what do you see
when you get an email?
</A
></DT
><DT
>A.2.5. <A
HREF="faq.html#faq-phb-emailapp"
>&#13; Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.6. <A
HREF="faq.html#faq-phb-data"
>&#13; 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 <SPAN
CLASS="QUOTE"
>"matching"</SPAN
>
fields? If I wanted to take the results of a query and export
that data to MS Excel, could I do that?
</A
></DT
><DT
>A.2.7. <A
HREF="faq.html#faq-phb-l10n"
>&#13; Has anyone converted Bugzilla to another language to be
used in other countries? Is it localizable?
</A
></DT
><DT
>A.2.8. <A
HREF="faq.html#faq-phb-reports"
>&#13; Can a user create and save reports?
Can they do this in Word format? Excel format?
</A
></DT
><DT
>A.2.9. <A
HREF="faq.html#faq-phb-backup"
>&#13; Are there any backup features provided?
</A
></DT
><DT
>A.2.10. <A
HREF="faq.html#faq-phb-maintenance"
>&#13; 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 what types of individuals
would we need to hire and how much would that cost if we were to
go with Bugzilla vs. buying an <SPAN
CLASS="QUOTE"
>"out-of-the-box"</SPAN
>
solution.
</A
></DT
><DT
>A.2.11. <A
HREF="faq.html#faq-phb-installtime"
>&#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 days 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?
</A
></DT
><DT
>A.2.12. <A
HREF="faq.html#faq-phb-cost"
>&#13; Is there any licensing fee or other fees for using Bugzilla? Any
out-of-pocket cost other than the bodies needed as identified above?
</A
></DT
><DT
>A.2.13. <A
HREF="faq.html#faq-phb-renameBugs"
>&#13; We don't like referring to problems as 'bugs'. Can we change that?
</A
></DT
></DL
></DD
><DT
>3. <A
HREF="faq.html#faq-admin"
>Administrative Questions</A
></DT
><DD
><DL
><DT
>A.3.1. <A
HREF="faq.html#faq-admin-midair"
>&#13; 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
></DT
><DT
>A.3.2. <A
HREF="faq.html#faq-admin-livebackup"
>&#13; Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.3.3. <A
HREF="faq.html#faq-admin-cvsupdate"
>&#13; How can I update the code and the database using CVS?
</A
></DT
><DT
>A.3.4. <A
HREF="faq.html#faq-admin-enable-unconfirmed"
>&#13; How do I make it so that bugs can have an UNCONFIRMED status?
</A
></DT
><DT
>A.3.5. <A
HREF="faq.html#faq-admin-moving"
>&#13; How do I move a Bugzilla installation from one machine to another?
</A
></DT
></DL
></DD
><DT
>4. <A
HREF="faq.html#faq-security"
>Bugzilla Security</A
></DT
><DD
><DL
><DT
>A.4.1. <A
HREF="faq.html#faq-security-mysql"
>&#13; How do I completely disable MySQL security if it's giving
me problems? (I've followed the instructions in the installation
section of this guide...)
</A
></DT
><DT
>A.4.2. <A
HREF="faq.html#faq-security-knownproblems"
>&#13; Are there any security problems with Bugzilla?
</A
></DT
></DL
></DD
><DT
>5. <A
HREF="faq.html#faq-email"
>Bugzilla Email</A
></DT
><DD
><DL
><DT
>A.5.1. <A
HREF="faq.html#faq-email-nomail"
>&#13; I have a user who doesn't want to receive any more email
from Bugzilla. How do I stop it entirely for this user?
</A
></DT
><DT
>A.5.2. <A
HREF="faq.html#faq-email-testing"
>&#13; I'm evaluating/testing Bugzilla, and don't want it to send email
to anyone but me. How do I do it?
</A
></DT
><DT
>A.5.3. <A
HREF="faq.html#faq-email-whine"
>&#13; I want whineatnews.pl to whine at something other than new and
reopened bugs. How do I do it?
</A
></DT
><DT
>A.5.4. <A
HREF="faq.html#faq-email-mailif"
>&#13; How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.5.5. <A
HREF="faq.html#faq-email-sendmailnow"
>&#13; Email takes FOREVER to reach me from Bugzilla -- it's
extremely slow. What gives?
</A
></DT
><DT
>A.5.6. <A
HREF="faq.html#faq-email-nonreceived"
>&#13; How come email from Bugzilla changes never reaches me?
</A
></DT
></DL
></DD
><DT
>6. <A
HREF="faq.html#faq-db"
>Bugzilla Database</A
></DT
><DD
><DL
><DT
>A.6.1. <A
HREF="faq.html#faq-db-corrupted"
>&#13; I think my database might be corrupted, or contain
invalid entries. What do I do?
</A
></DT
><DT
>A.6.2. <A
HREF="faq.html#faq-db-manualedit"
>&#13; I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.6.3. <A
HREF="faq.html#faq-db-permissions"
>&#13; I think I've set up MySQL permissions correctly, but Bugzilla still
can't connect.
</A
></DT
><DT
>A.6.4. <A
HREF="faq.html#faq-db-synchronize"
>&#13; How do I synchronize bug information among multiple
different Bugzilla databases?
</A
></DT
></DL
></DD
><DT
>7. <A
HREF="faq.html#faq-nt"
>Bugzilla and Win32</A
></DT
><DD
><DL
><DT
>A.7.1. <A
HREF="faq.html#faq-nt-easiest"
>&#13; What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.7.2. <A
HREF="faq.html#faq-nt-bundle"
>&#13; Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.7.3. <A
HREF="faq.html#faq-nt-mappings"
>&#13; CGI's are failing with a <SPAN
CLASS="QUOTE"
>"something.cgi is not a valid
Windows NT application"</SPAN
> error. Why?
</A
></DT
><DT
>A.7.4. <A
HREF="faq.html#faq-nt-dbi"
>&#13; I'm having trouble with the perl modules for NT not being
able to talk to the database.
</A
></DT
></DL
></DD
><DT
>8. <A
HREF="faq.html#faq-use"
>Bugzilla Usage</A
></DT
><DD
><DL
><DT
>A.8.1. <A
HREF="faq.html#faq-use-changeaddress"
>&#13; How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.8.2. <A
HREF="faq.html#faq-use-query"
>&#13; The query page is very confusing.
Isn't there a simpler way to query?
</A
></DT
><DT
>A.8.3. <A
HREF="faq.html#faq-use-accept"
>&#13; I'm confused by the behavior of the <SPAN
CLASS="QUOTE"
>"Accept"</SPAN
>
button in the Show Bug form. Why doesn't it assign the bug
to me when I accept it?
</A
></DT
><DT
>A.8.4. <A
HREF="faq.html#faq-use-attachment"
>&#13; I can't upload anything into the database via the
<SPAN
CLASS="QUOTE"
>"Create Attachment"</SPAN
> link. What am I doing wrong?
</A
></DT
><DT
>A.8.5. <A
HREF="faq.html#faq-use-keyword"
>&#13; How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DT
>A.8.6. <A
HREF="faq.html#faq-use-close"
>&#13; Why can't I close bugs from the <SPAN
CLASS="QUOTE"
>"Change Several Bugs
at Once"</SPAN
> page?
</A
></DT
></DL
></DD
><DT
>9. <A
HREF="faq.html#faq-hacking"
>Bugzilla Hacking</A
></DT
><DD
><DL
><DT
>A.9.1. <A
HREF="faq.html#faq-hacking-templatestyle"
>&#13; What kind of style should I use for templatization?
</A
></DT
><DT
>A.9.2. <A
HREF="faq.html#faq-hacking-bugzillabugs"
>&#13; What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.9.3. <A
HREF="faq.html#faq-hacking-priority"
>&#13; How can I change the default priority to a null value?
For instance, have the default priority be <SPAN
CLASS="QUOTE"
>"---"</SPAN
>
instead of <SPAN
CLASS="QUOTE"
>"P2"</SPAN
>?
</A
></DT
><DT
>A.9.4. <A
HREF="faq.html#faq-hacking-patches"
>&#13; What's the best way to submit patches? What guidelines
should I follow?
</A
></DT
></DL
></DD
></DL
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-general"
></A
>1. General Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-license"
></A
><B
>A.1.1. </B
>
What license is Bugzilla distributed under?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Bugzilla is covered by the Mozilla Public License.
See details at <A
HREF="http://www.mozilla.org/MPL/"
TARGET="_top"
>http://www.mozilla.org/MPL/</A
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-support"
></A
><B
>A.1.2. </B
>
How do I get commercial support for Bugzilla?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<A
HREF="http://www.bugzilla.org/support/consulting.html"
TARGET="_top"
>http://www.bugzilla.org/support/consulting.html</A
>
is a list of companies and individuals who have asked us to
list them as consultants for Bugzilla.
</P
><P
>&#13; 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.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-companies"
></A
><B
>A.1.3. </B
>
What major companies or projects are currently using Bugzilla
for bug-tracking?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
There are <EM
>dozens</EM
> of major companies with public
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/"
TARGET="_top"
>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
Gerv <CODE
CLASS="email"
>&#60;<A
HREF="mailto:gerv@mozilla.org"
>gerv@mozilla.org</A
>&#62;</CODE
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-maintainers"
></A
><B
>A.1.4. </B
>
Who maintains Bugzilla?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
A <A
HREF="http://www.bugzilla.org/developers/profiles.html"
TARGET="_top"
>core
team</A
>, led by Dave Miller (justdave@bugzilla.org).
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-compare"
></A
><B
>A.1.5. </B
>
How does Bugzilla stack up against other bug-tracking databases?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
We can't find any head-to-head comparisons of Bugzilla against
other defect-tracking software. If you know of one, please get
in touch. In the experience of Matthew Barnson (the original
author of this FAQ), though, Bugzilla offers superior
performance on commodity hardware, better price (free!), more
developer-friendly features (such as stored queries, email
integration, and platform independence), improved scalability,
greater flexibility, and superior ease-of-use when compared
to commercial bug-tracking software.
</P
><P
>&#13; If you happen to be a vendor for commercial bug-tracking
software, and would like to submit a list of advantages your
product has over Bugzilla, simply send it to
<CODE
CLASS="email"
>&#60;<A
HREF="mailto:documentation@bugzilla.org"
>documentation@bugzilla.org</A
>&#62;</CODE
> and we'd be happy to
include the comparison in our documentation.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-bzmissing"
></A
><B
>A.1.6. </B
>
Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
It may be that the support has not been built yet, or that you
have not yet found it. While Bugzilla makes strides in usability,
customizability, scalability, and user interface with each release,
that doesn't mean it can't still use improvement!
</P
><P
>&#13; The best way to make an enhancement request is to <A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
TARGET="_top"
>file
a bug at bugzilla.mozilla.org</A
> and set the Severity
to 'enhancement'. Your 'request for enhancement' (RFE) will
start out in the UNCONFIRMED state, and will stay there until
someone with the ability to COMFIRM the bug reviews it.
If that person feels it to be a good request that fits in with
Bugzilla's overall direction, the status will be changed to
NEW; if not, they will probably explain why and set the bug
to RESOLVED/WONTFIX. If someone else has made the same (or
almost the same) request before, your request will be marked
RESOLVED/DUPLICATE, and a pointer to the previous RFE will be
added.
</P
><P
>&#13; Even if your RFE gets approved, that doesn't mean it's going
to make it right into the next release; there are a limited
number of developers, and a whole lot of RFEs... some of
which are <EM
>quite</EM
> complex. If you're a
code-hacking sort of person, you can help the project along
by making a patch yourself that supports the functionality
you require. If you have never contributed anything to
Bugzilla before, please be sure to read the
<A
HREF="http://www.bugzilla.org/docs/developer.html"
TARGET="_top"
>Developers' Guide</A
>
and
<A
HREF="http://www.bugzilla.org/docs/contributor.html"
TARGET="_top"
>Contributors' Guide</A
>
before going ahead.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-mysql"
></A
><B
>A.1.7. </B
>
Why MySQL? I'm interested in seeing Bugzilla run on
PostgreSQL/Sybase/Oracle/Msql/MSSQL.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
MySQL was originally chosen because it is free, easy to install,
and was available for the hardware Netscape intended to run it on.
</P
><P
>&#13; There is currently work in progress to make Bugzilla work on
PostgreSQL; track the progress of this initiative in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
TARGET="_top"
>bug 98304</A
>.
</P
><P
>&#13; Sybase support is no longer being worked on. Even if it eventually
happens, it's VERY unlikely to work without the end-user-company
having to stick a few developers on making several manual changes.
Sybase is just NOT very standards-compliant (despite all the hype),
and it turned out that way too much had to be changed to make it
work -- like moving half of the application logic into stored
procedures to get any kind of decent performance out of it.
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
TARGET="_top"
>Bug
173130</A
> is the relevant bug.
</P
><P
>&#13; Red Hat once ran a version of Bugzilla that worked on Oracle,
but that was long, long ago; that version (Bugzilla 2.8) is
now obsolete, insecure, and totally unsupported. Red Hat's
current Bugzilla (based on Bugzilla 2.17.1) uses PostgreSQL,
and work is being done to merge those changes into the main
distribution. (See above.) At this time we know of no recent
ports of Bugzilla to Oracle. (In our honest opinion, Bugzilla
doesn't need what Oracle offers.)
</P
><P
>&#13; <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=237862"
TARGET="_top"
>Bug
237862</A
> is a good bug to read through if you'd like to see
what progress is being made on general database compatibility.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-bonsaitools"
></A
><B
>A.1.8. </B
>
What is <TT
CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
>?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Bugzilla used to have the path to perl on the shebang line set
to <TT
CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
> because when
Terry first started writing the code for mozilla.org he needed a
version of Perl and other tools that were completely under his
control. This location was abandoned for the 2.18 release in favor
of the more sensible <TT
CLASS="filename"
>/usr/bin/perl</TT
>. If you
installed an older verion of Bugzilla and created the symlink we
suggested, you can remove it now (provided that you don't have
anything else, such as Bonsai, using it and you don't intend to
reinstall an older version of Bugzilla).
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-perlpath"
></A
><B
>A.1.9. </B
>
My perl is located at <TT
CLASS="filename"
>/usr/local/bin/perl</TT
>
and not <TT
CLASS="filename"
>/usr/bin/perl</TT
>. Is there an easy
to change that in all the files that have this hard-coded?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The easiest way to get around this is to create a link from
one to the other:
<B
CLASS="command"
>ln -s /usr/local/bin/perl /usr/bin/perl</B
>.
If that's not an option for you, the following bit of perl
magic will change all the shebang lines (that is to say,
the line at the top of each file that starts with '#!'
and contains the path) to something else:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; Sadly, this command-line won't work on Windows unless you
also have Cygwin. However, MySQL comes with a binary called
<B
CLASS="command"
>replace</B
> which can do the job:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;C:\mysql\bin\replace "#!/usr/bin/perl" "#!C:\perl\bin\perl" -- *.cgi *.pl
</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
>&#13; If your perl path is something else again, just follow the
above examples and replace
<TT
CLASS="filename"
>/usr/local/bin/perl</TT
> with your own perl path.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Once you've modified all your files, you'll also need to modify the
<TT
CLASS="filename"
>t/002goodperl.t</TT
> test, as it tests that all
shebang lines are equal to <TT
CLASS="filename"
>/usr/bin/perl</TT
>.
(For more information on the test suite, please check out the
appropriate section in the <A
HREF="http://www.bugzilla.org/docs/developer.html#testsuite"
TARGET="_top"
>Developers'
Guide</A
>.) Having done this, run the test itself:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;perl runtests.pl 2 --verbose
</PRE
></FONT
></TD
></TR
></TABLE
>
to ensure that you've modified all the relevant files.
</P
><P
>&#13; If using Apache on Windows, you can avoid the whole problem
by setting the <A
HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"
TARGET="_top"
>&#13; ScriptInterpreterSource</A
> directive to 'Registry'.
(If using Apache 2 or higher, set it to 'Registry-Strict'.)
ScriptInterperterSource requires a registry entry
<SPAN
CLASS="QUOTE"
>"HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command"</SPAN
> to
associate .cgi files with your perl executable. If one does
not already exist, create it with a default value of
<SPAN
CLASS="QUOTE"
>"&#60;full path to perl&#62; -T"</SPAN
>, e.g.
<SPAN
CLASS="QUOTE"
>"C:\Perl\bin\perl.exe -T"</SPAN
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-general-cookie"
></A
><B
>A.1.10. </B
>
Is there an easy way to change the Bugzilla cookie name?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
At present, no.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-mod-perl"
></A
><B
>A.1.11. </B
>
Does bugzilla run under <TT
CLASS="filename"
>mod_perl</TT
>?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
At present, no. Work is slowly taking place to remove global
variables, use $cgi, and use DBI. These are all necessary for
mod_perl (as well as being good for other reasons). Visit
<A
HREF="https://bugzilla.mozilla.org/show_bug.cgi?id=87406"
TARGET="_top"
>&#13; bug 87406</A
> to view the discussion and progress.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-phb"
></A
>2. Managerial Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-client"
></A
><B
>A.2.1. </B
>
Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
It is web and e-mail based.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-priorities"
></A
><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 the choice of acceptable values?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes. However, modifying some fields, notably those related to bug
progression states, also require adjusting the program logic to
compensate for the change.
</P
><P
>&#13; There is no GUI for adding fields to Bugzilla at this
time. You can follow development of this feature in
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
TARGET="_top"
>bug 91037</A
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-reporting"
></A
><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. :)
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes. Look at <A
HREF="http://bugzilla.mozilla.org/report.cgi"
TARGET="_top"
>http://bugzilla.mozilla.org/report.cgi</A
>
for samples of what Bugzilla can do in reporting and graphing.
Fuller documentation is provided in <A
HREF="reporting.html"
>Section 6.11</A
>.
</P
><P
>&#13; If you can not get the reports you want from the included reporting
scripts, it is possible to hook up a professional reporting package
such as Crystal Reports using ODBC. If you choose to do this,
beware that giving direct access to the database does contain some
security implications. Even if you give read-only access to the
bugs database it will bypass the secure bugs features of Bugzilla.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-email"
></A
><B
>A.2.4. </B
>
Is there email notification? If so, what do you see
when you get an email?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Email notification is user-configurable. By default, the bug id
and summary of the bug report accompany each email notification,
along with a list of the changes made.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-emailapp"
></A
><B
>A.2.5. </B
>
Do users have to have any particular
type of email application?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Bugzilla email is sent in plain text, the most compatible
mail format on the planet.
<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
>&#13; 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 <SPAN
CLASS="QUOTE"
>"respond to messages in the format in
which they were sent"</SPAN
>. 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.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-data"
></A
><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 imported into <SPAN
CLASS="QUOTE"
>"matching"</SPAN
>
fields? If I wanted to take the results of a query and export
that data to MS Excel, could I do that?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
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 spreadsheet applications.
</P
><P
>&#13; To use the RDF format of the buglist it is necessary to append a
<SAMP
CLASS="computeroutput"
>&#38;ctype=rdf</SAMP
> to the URL. RDF
is meant to be machine readable and thus it is assumed that the
URL would be generated programmatically so there is no user visible
link to this format.
</P
><P
>&#13; Currently the only script included with Bugzilla that can import
data is <TT
CLASS="filename"
>importxml.pl</TT
> which is intended to be
used for importing the data generated by the XML ctype of
<TT
CLASS="filename"
>show_bug.cgi</TT
> in association with bug moving.
Any other use is left as an exercise for the user.
</P
><P
>&#13; There are also scripts included in the <TT
CLASS="filename"
>contrib/</TT
>
directory for using e-mail to import information into Bugzilla,
but these scripts are not currently supported and included for
educational purposes.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-l10n"
></A
><B
>A.2.7. </B
>
Has anyone converted Bugzilla to another language to be
used in other countries? Is it localizable?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes. For more information including available translated templates,
see <A
HREF="http://www.bugzilla.org/download.html#localizations"
TARGET="_top"
>http://www.bugzilla.org/download.html#localizations</A
>.
Some admin interfaces have been templatized (for easy localization)
but many of them are still available in English only. Also, there
may be issues with the charset not being declared. See <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
TARGET="_top"
>bug 126226</A
>
for more information.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-reports"
></A
><B
>A.2.8. </B
>
Can a user create and save reports?
Can they do this in Word format? Excel format?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes. No. Yes (using the CSV format).
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-backup"
></A
><B
>A.2.9. </B
>
Are there any backup features provided?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
MySQL, the database back-end for Bugzilla, allows hot-backup
of data. You can find strategies for dealing with backup
considerations at <A
HREF="http://www.mysql.com/doc/B/a/Backup.html"
TARGET="_top"
>http://www.mysql.com/doc/B/a/Backup.html</A
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-maintenance"
></A
><B
>A.2.10. </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 what types of individuals
would we need to hire and how much would that cost if we were to
go with Bugzilla vs. buying an <SPAN
CLASS="QUOTE"
>"out-of-the-box"</SPAN
>
solution.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
If Bugzilla is set up correctly from the start, continuing
maintenance needs are minimal and can be done easily using
the web interface.
</P
><P
>&#13; Commercial Bug-tracking software typically costs somewhere
upwards of $20,000 or more for 5-10 floating licenses. Bugzilla
consultation is available from skilled members of the newsgroup.
Simple questions are answered there and then.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-installtime"
></A
><B
>A.2.11. </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 days 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?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
It all depends on your level of commitment. Someone with much
Bugzilla experience can get you up and running in less than a day,
and your Bugzilla install can run untended for years. If your
Bugzilla strategy is critical to your business workflow, hire
somebody to who has reasonable Perl skills, and a familiarity
with the operating system on which Bugzilla will be running,
and have them handle your process management, bug-tracking
maintenance, and local customization.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-cost"
></A
><B
>A.2.12. </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?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
No. Bugzilla, Perl, the Template Toolkit, and all other support
software needed to make Bugzilla work can be downloaded for free.
MySQL -- the database used by Bugzilla -- is also open-source, but
they ask that if you find their product valuable, you purchase a
support contract from them that suits your needs.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-phb-renameBugs"
></A
><B
>A.2.13. </B
>
We don't like referring to problems as 'bugs'. Can we change that?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes! As of Bugzilla 2.18, it is a simple matter to change the
word 'bug' into whatever word/phrase is used by your organization.
See the documentation on Customization for more details,
specifically <A
HREF="cust-templates.html#template-specific"
>Section 5.1.5</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-admin"
></A
>3. Administrative Questions</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-admin-midair"
></A
><B
>A.3.1. </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 or how are they notified?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Bugzilla does not lock records. It provides mid-air collision
detection -- which means that it warns a user when a commit is
about to conflict with commits recently made by another user,
and offers the second user a choice of options to deal with
the conflict.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-admin-livebackup"
></A
><B
>A.3.2. </B
>
Can users be on the system while a backup is in progress?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Yes, but 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. If your database
is larger, you may want to look into alternate backup
techniques, such as database replication, or backing up from
a read-only mirror. (Read up on these in the MySQL docs
on the MySQL site.)
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-admin-cvsupdate"
></A
><B
>A.3.3. </B
>
How can I update the code and the database using CVS?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Make a backup of both your Bugzilla directory and the
database. For the Bugzilla directory this is as easy as
doing <B
CLASS="command"
>cp -rp bugzilla bugzilla.bak</B
>.
For the database, there's a number of options - see the
MySQL docs and pick the one that fits you best (the easiest
is to just make a physical copy of the database on the disk,
but you have to have the database server shut down to do
that without risking dataloss).
</P
></LI
><LI
><P
>&#13; Make the Bugzilla directory your current directory.
</P
></LI
><LI
><P
>&#13; Use <B
CLASS="command"
>cvs -q update -AdP</B
> if you want to
update to the tip or
<B
CLASS="command"
>cvs -q update -dP -rTAGNAME</B
>
if you want a specific version (in that case you'll have to
replace TAGNAME with a CVS tag name such as BUGZILLA-2_16_5).
</P
><P
>&#13; If you've made no local changes, this should be very clean.
If you have made local changes, then watch the cvs output
for C results. If you get any lines that start with a C
it means there were conflicts between your local changes
and what's in CVS. You'll need to fix those manually before
continuing.
</P
></LI
><LI
><P
>&#13; After resolving any conflicts that the cvs update operation
generated, running <B
CLASS="command"
>./checksetup.pl</B
> will
take care of updating the database for you as well as any
other changes required for the new version to operate.
</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
>&#13; Once you run checksetup.pl, the only way to go back is
to restore the database backups. You can't
<SPAN
CLASS="QUOTE"
>"downgrade"</SPAN
> the system cleanly under most
circumstances.
</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
>
</P
><P
>&#13; See also the instructions in <A
HREF="upgrading.html#upgrade-cvs"
>Section 3.11.2.1</A
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-admin-enable-unconfirmed"
></A
><B
>A.3.4. </B
>
How do I make it so that bugs can have an UNCONFIRMED status?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
To use the UNCONFIRMED status, you must have the 'usevotes'
parameter set to <SPAN
CLASS="QUOTE"
>"On"</SPAN
>. You must then visit the
<TT
CLASS="filename"
>editproducts.cgi</TT
> page and set the <SPAN
CLASS="QUOTE"
>"
Number of votes a bug in this product needs to automatically
get out of the UNCONFIRMED state"</SPAN
> to be a non-zero number.
(You will have to do this for each product that wants to use
the UNCONFIRMED state.) If you do not actually want users to be
able to vote for bugs entered against this product, leave the
<SPAN
CLASS="QUOTE"
>"Maximum votes per person"</SPAN
> value at '0'.
</P
><P
>&#13; There is work being done to decouple the UNCONFIRMED state from
the 'usevotes' parameter for future versions of Bugzilla.
Follow the discussion and progress at <A
HREF="https://bugzilla.mozilla.org/show_bug.cgi?id=162060"
TARGET="_top"
>bug
162060</A
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-admin-moving"
></A
><B
>A.3.5. </B
>
How do I move a Bugzilla installation from one machine to another?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Use mysqldump to make a backup of the bugs database. For a
typical Bugzilla setup, such a command might look like this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;/usr/bin/mysqldump -u(username) -p(password) --database bugs &#62; bugzilla-backup.txt
</PRE
></FONT
></TD
></TR
></TABLE
>
See the <A
HREF="http://dev.mysql.com/doc/mysql/en/mysqldump.html"
TARGET="_top"
>&#13; mysqldump documentation</A
> for more information on using
the tool, including how to restore your copy onto the destination
machine.
</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
>&#13; Depending on the size of your database, and the power of your
machine, the mysqldump command could be running long enough
that the password would be visible to someone using the
<B
CLASS="command"
>ps</B
> command. If you are on a multi-user
machine, and this is a concern to you, create an entry in
the file <TT
CLASS="filename"
>~/.my.cnf</TT
> that looks like this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;[mysqldump]
user=bugs
password=mypassword
</PRE
></FONT
></TD
></TR
></TABLE
>
and then leave the 'user' and 'password' params out of the
command line.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; On your new machine, follow the instructions found in <A
HREF="installing-bugzilla.html"
>Chapter 2</A
> as far as setting up the physical
environment of the new machine with perl, webserver, modules, etc.
Having done that, you can either: copy your entire Bugzilla
directory from the old machine to a new one (if you want to keep
your existing code and modifications), or download a newer version
(if you are planning to upgrade at the same time). Even if you are
upgrading to clean code, you will still want to bring over the
<TT
CLASS="filename"
>localconfig</TT
> file, and the
<TT
CLASS="filename"
>data</TT
> directory from the
old machine, as they contain configuration information that you
probably won't want to re-create.
</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
>&#13; If the location or port number of your SQL server changed
as part of the move, you'll need to update the appropriate
variables in localconfig before taking the next step.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Once you have your code in place, and your database has
been restored from the backup you made in step 1, run
<B
CLASS="command"
>checksetup.pl</B
>. This will upgrade your
database (if necessary), rebuild your templates, etc.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-security"
></A
>4. Bugzilla Security</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-security-mysql"
></A
><B
>A.4.1. </B
>
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...)
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Run MySQL like this: <B
CLASS="command"
>mysqld --skip-grant-tables</B
>.
Please remember that <EM
>this makes MySQL as secure as
taping a $100 to the floor of a football stadium bathroom for
safekeeping.</EM
>
</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
>&#13; This can't be stressed enough. Doing this is a bad idea.
Please consult <A
HREF="security-mysql.html"
>Section 4.2</A
> of this guide
and the MySQL documentation for better solutions.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-security-knownproblems"
></A
><B
>A.4.2. </B
>
Are there any security problems with Bugzilla?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The Bugzilla code has undergone a reasonably complete security
audit, and user-facing CGIs run under Perl's taint mode. However,
it is recommended that you closely examine permissions on your
Bugzilla installation, and follow the recommended security
guidelines found in The Bugzilla Guide.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-email"
></A
>5. Bugzilla Email</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-nomail"
></A
><B
>A.5.1. </B
>
I have a user who doesn't want to receive any more email
from Bugzilla. How do I stop it entirely for this user?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The user can stop Bugzilla from sending any mail by unchecking
all boxes on the 'Edit prefs' -&#62; 'Email settings' page.
(As of 2.18,this is made easier by the addition of a 'Disable
All Mail' button.) Alternately, you can add their email address
to the <TT
CLASS="filename"
>data/nomail</TT
> file (one email address
per line). This will override their personal preferences, and
they will never be sent mail again.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-testing"
></A
><B
>A.5.2. </B
>
I'm evaluating/testing Bugzilla, and don't want it to send email
to anyone but me. How do I do it?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
To disable email, set the
<VAR
CLASS="option"
>mail_delivery_method</VAR
> parameter to
<VAR
CLASS="literal"
>none</VAR
> (2.20 and later), or
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>$enableSendMail</PRE
></FONT
></TD
></TR
></TABLE
> parameter to '0'
in either <TT
CLASS="filename"
>BugMail.pm</TT
> (2.18 and later) or
<TT
CLASS="filename"
>processmail</TT
> (up to 2.16.x).
</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
>&#13; Up to 2.16.x, changing
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>$enableSendMail</PRE
></FONT
></TD
></TR
></TABLE
>
will only affect bugmail; email related to password changes,
email address changes, bug imports, flag changes, etc. will
still be sent out. As of the final release of 2.18, however,
the above step will disable <EM
>all</EM
> mail
sent from Bugzilla for any purpose.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; To have bugmail (and only bugmail) redirected to you instead of
its intended recipients, leave
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>$enableSendMail</PRE
></FONT
></TD
></TR
></TABLE
> alone;
instead, edit the <SPAN
CLASS="QUOTE"
>"newchangedmail"</SPAN
> parameter
as follows:
</P
><P
></P
><UL
><LI
><P
>&#13; Replace <SPAN
CLASS="QUOTE"
>"To:"</SPAN
> with <SPAN
CLASS="QUOTE"
>"X-Real-To:"</SPAN
>
</P
></LI
><LI
><P
>&#13; Replace <SPAN
CLASS="QUOTE"
>"Cc:"</SPAN
> with <SPAN
CLASS="QUOTE"
>"X-Real-CC:"</SPAN
>
</P
></LI
><LI
><P
>&#13; Add a <SPAN
CLASS="QUOTE"
>"To: %lt;your_email_address&#62;"</SPAN
>
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-whine"
></A
><B
>A.5.3. </B
>
I want whineatnews.pl to whine at something other than new and
reopened bugs. How do I do it?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
For older versions of Bugzilla, you may be able to apply
Klaas Freitag's patch for <SPAN
CLASS="QUOTE"
>"whineatassigned"</SPAN
>,
which can be found in
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
TARGET="_top"
>bug
6679</A
>. Note that this patch was made in 2000, so it may take
some work to apply cleanly to any releases of Bugzilla newer than
that, but you can use it as a starting point.
</P
><P
>&#13; An updated (and much-expanded) version of this functionality is
due to be released as part of Bugzilla 2.20; see
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=185090"
TARGET="_top"
>bug
185090</A
> for the discussion, and for more up-to-date patches
if you just can't wait.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-mailif"
></A
><B
>A.5.4. </B
>
How do I set up the email interface to submit/change bugs via email?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
You can find an updated README.mailif file in the contrib/ directory
of your Bugzilla distribution that walks you through the setup.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-sendmailnow"
></A
><B
>A.5.5. </B
>
Email takes FOREVER to reach me from Bugzilla -- it's
extremely slow. What gives?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
If you are using <SPAN
CLASS="application"
>sendmail</SPAN
>, try
enabling <VAR
CLASS="option"
>sendmailnow</VAR
> in
<TT
CLASS="filename"
>editparams.cgi</TT
>. For earlier versions of
<SPAN
CLASS="application"
>sendmail</SPAN
>, one could achieve
significant performance improvement in the UI (at the cost of
delaying the sending of mail) by setting this parameter to
<VAR
CLASS="literal"
>off</VAR
>. Sites with
<SPAN
CLASS="application"
>sendmail</SPAN
> version 8.12 (or higher)
should leave this <VAR
CLASS="literal"
>on</VAR
>, as they will not see
any performance benefit.
</P
><P
>&#13; If you are using an alternate
<A
HREF="glossary.html#gloss-mta"
><I
CLASS="glossterm"
>MTA</I
></A
>, make sure the
options given in <TT
CLASS="filename"
>Bugzilla/BugMail.pm</TT
>
and any other place where <SPAN
CLASS="application"
>sendmail</SPAN
>
is called are correct for your MTA.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-email-nonreceived"
></A
><B
>A.5.6. </B
>
How come email from Bugzilla changes never reaches me?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Double-check that you have not turned off email in your user
preferences. Confirm that Bugzilla is able to send email by
visiting the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
> link of your Bugzilla
installation and clicking the <SPAN
CLASS="QUOTE"
>"Submit Request"</SPAN
>
button after entering your email address.
</P
><P
>&#13; 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
><P
>&#13; If you are using an MTA other than
<SPAN
CLASS="application"
>sendmail</SPAN
> the
<VAR
CLASS="option"
>sendmailnow</VAR
> param must be set to
<VAR
CLASS="literal"
>on</VAR
> or no mail will be sent.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-db"
></A
>6. Bugzilla Database</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-db-corrupted"
></A
><B
>A.6.1. </B
>
I think my database might be corrupted, or contain
invalid entries. What do I do?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Run the <SPAN
CLASS="QUOTE"
>"sanity check"</SPAN
> utility
(<TT
CLASS="filename"
>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
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.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-db-manualedit"
></A
><B
>A.6.2. </B
>
I want to manually edit some entries in my database. How?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
There is no facility in Bugzilla itself to do this. It's also
generally not a smart thing to do if you don't know exactly what
you're doing. If you understand SQL, though, you can use the
<B
CLASS="command"
>mysql</B
> command line utility to manually insert,
delete and modify table information. There are also more intuitive
GUI clients available. Personal favorites of the Bugzilla team
are <A
HREF="http://www.phpmyadmin.net/"
TARGET="_top"
>phpMyAdmin</A
>
and <A
HREF="http://www.mysql.com/products/mysqlcc/"
TARGET="_top"
>MySQL
Control Center</A
>.
</P
><P
>&#13; Remember, backups are your friend. Everyone makes mistakes, and
it's nice to have a safety net in case you mess something up.
Consider using <B
CLASS="command"
>mysqldump</B
> to make a duplicate
of your database before altering it manually.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-db-permissions"
></A
><B
>A.6.3. </B
>
I think I've set up MySQL permissions correctly, but Bugzilla still
can't connect.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Try running MySQL from its binary:
<B
CLASS="command"
>mysqld --skip-grant-tables</B
>.
This will allow you to completely rule out grant tables as the
cause of your frustration. If this Bugzilla is able to connect
at this point then you need to check that you have granted proper
permission to the user password combo defined in
<TT
CLASS="filename"
>localconfig</TT
>.
</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
>&#13; 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.
</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-db-synchronize"
></A
><B
>A.6.4. </B
>
How do I synchronize bug information among multiple
different Bugzilla databases?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Well, you can synchronize or you can move bugs.
Synchronization will only work one way -- you can create
a read-only copy of the database at one site, and have it
regularly updated at intervals from the main database.
</P
><P
>&#13; MySQL has some synchronization features built-in to the
latest releases. It would be great if someone looked into
the possibilities there and provided a report to the
newsgroup on how to effectively synchronize two Bugzilla
installations.
</P
><P
>&#13; If you simply need to transfer bugs from one Bugzilla to another,
checkout the <SPAN
CLASS="QUOTE"
>"move.pl"</SPAN
> script in the Bugzilla
distribution.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-nt"
></A
>7. Bugzilla and Win32</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-nt-easiest"
></A
><B
>A.7.1. </B
>
What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference. B^)
</P
><P
>&#13; Seriously though, making Bugzilla work easily with Windows
was one of the major goals of the 2.18 milestone. If the
necessary components are in place (perl, a webserver, an MTA, etc.)
then installation of Bugzilla on a Windows box should be no more
difficult than on any other platform. As with any installation,
we recommend that you carefully and completely follow the
installation instructions in <A
HREF="os-specific.html#os-win32"
>Section 2.4.1</A
>.
</P
><P
>&#13; While doing so, don't forget to check out the very excellent guide
to <A
HREF="http://www.bugzilla.org/docs/win32install.html"
TARGET="_top"
>&#13; Installing Bugzilla on Microsoft Windows</A
> written by
Byron Jones. Thanks, Byron!
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-nt-bundle"
></A
><B
>A.7.2. </B
>
Is there a "Bundle::Bugzilla" equivalent for Win32?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
installation on UNIX systems. If someone can volunteer to
create a suitable PPM bundle for Win32, it would be appreciated.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-nt-mappings"
></A
><B
>A.7.3. </B
>
CGI's are failing with a <SPAN
CLASS="QUOTE"
>"something.cgi is not a valid
Windows NT application"</SPAN
> error. Why?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Depending on what Web server you are using, you will have to
configure the Web server to treat *.cgi files as CGI scripts.
In IIS, you do this by adding *.cgi to the App Mappings with
the &#60;path&#62;\perl.exe %s %s as the executable.
</P
><P
>&#13; Microsoft has some advice on this matter, as well:
<A
NAME="AEN2969"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13; <SPAN
CLASS="QUOTE"
>"Set application mappings. In the ISM, map the extension
for the script file(s) to the executable for the script
interpreter. For example, you might map the extension .py to
Python.exe, the executable for the Python script interpreter.
Note For the ActiveState Perl script interpreter, the extension
'.pl' is associated with PerlIS.dll by default. If you want
to change the association of .pl to perl.exe, you need to
change the application mapping. In the mapping, you must add
two percent (%) characters to the end of the pathname for
perl.exe, as shown in this example:
<B
CLASS="command"
>c:\perl\bin\perl.exe %s %s</B
>"</SPAN
>
</P
></BLOCKQUOTE
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-nt-dbi"
></A
><B
>A.7.4. </B
>
I'm having trouble with the perl modules for NT not being
able to talk to the database.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Your modules may be outdated or inaccurate. Try:
<P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Hitting http://www.activestate.com/ActivePerl
</P
></LI
><LI
><P
>&#13; Download ActivePerl
</P
></LI
><LI
><P
>&#13; Go to your prompt
</P
></LI
><LI
><P
>&#13; Type 'ppm'
</P
></LI
><LI
><P
>&#13; <SAMP
CLASS="prompt"
>PPM&#62;</SAMP
> <B
CLASS="command"
>install DBI DBD-mysql GD</B
>
</P
></LI
></OL
>
I reckon TimeDate and Data::Dumper come with the activeperl.
You can check the ActiveState site for packages for installation
through PPM. <A
HREF="http://www.activestate.com/Packages/"
TARGET="_top"
>http://www.activestate.com/Packages/</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-use"
></A
>8. Bugzilla Usage</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-changeaddress"
></A
><B
>A.8.1. </B
>
How do I change my user name (email address) in Bugzilla?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
New in 2.16 - go to the Account section of the Preferences. You
will be emailed at both addresses for confirmation.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-query"
></A
><B
>A.8.2. </B
>
The query page is very confusing.
Isn't there a simpler way to query?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The interface was simplified by a UI designer for 2.16. Further
suggestions for improvement are welcome, but we won't sacrifice
power for simplicity.
</P
><P
>&#13; As of 2.18, there is also a 'simpler' search available. At the top
of the search page are two links; <SPAN
CLASS="QUOTE"
>"Advanced Search"</SPAN
>
will take you to the familiar full-power/full-complexity search
page. The <SPAN
CLASS="QUOTE"
>"Find a Specific Bug"</SPAN
> link will take you
to a much-simplified page where you can pick a product and
status (open,closed, or both), then enter words that appear in
the bug you want to find. This search will scour the 'Summary'
and 'Comment' fields, and return a list of bugs sorted so that
the bugs with the most hits/matches are nearer to the top.
</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
>&#13; Matches in the Summary will 'trump' matches in comments,
and bugs with summary-matches will be placed higher in
the buglist -- even if a lower-ranked bug has more matches
in the comments section.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Bugzilla uses a cookie to remember which version of the page
you visited last, and brings that page up when you next do a
search. The default page for new users (or after an upgrade)
is the 'simple' search.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-accept"
></A
><B
>A.8.3. </B
>
I'm confused by the behavior of the <SPAN
CLASS="QUOTE"
>"Accept"</SPAN
>
button in the Show Bug form. Why doesn't it assign the bug
to me when I accept it?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The current behavior is acceptable to bugzilla.mozilla.org and
most users. If you want to change this behavior, though, you
have your choice of patches:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=35195"
TARGET="_top"
>Bug 35195</A
>
seeks to add an <SPAN
CLASS="QUOTE"
>"...and accept the bug"</SPAN
> checkbox
to the UI. It has two patches attached to it:
<A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
TARGET="_top"
>attachment 8029</A
>
was originally created for Bugzilla 2.12, while
<A
HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=91372"
TARGET="_top"
>attachment 91372</A
>
is an updated version for Bugzilla 2.16
</TD
></TR
><TR
><TD
>&#13; <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=37613"
TARGET="_top"
>Bug
37613</A
> also provides two patches (against Bugzilla
2.12): one to add a 'Take Bug' option, and the other to
automatically reassign the bug on 'Accept'.
</TD
></TR
></TBODY
></TABLE
><P
></P
>
These patches are all somewhat dated now, and cannot be applied
directly, but they are simple enough to provide a guide on how
Bugzilla can be customized and updated to suit your needs.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-attachment"
></A
><B
>A.8.4. </B
>
I can't upload anything into the database via the
<SPAN
CLASS="QUOTE"
>"Create Attachment"</SPAN
> link. What am I doing wrong?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The most likely cause is a very old browser or a browser that is
incompatible with file upload via POST. Download the latest version
of your favourite browser to handle uploads correctly.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-keyword"
></A
><B
>A.8.5. </B
>
How do I change a keyword in Bugzilla, once some bugs are using it?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
In the Bugzilla administrator UI, edit the keyword and
it will let you replace the old keyword name with a new one.
This will cause a problem with the keyword cache; run
<B
CLASS="command"
>sanitycheck.cgi</B
> to fix it.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-use-close"
></A
><B
>A.8.6. </B
>
Why can't I close bugs from the <SPAN
CLASS="QUOTE"
>"Change Several Bugs
at Once"</SPAN
> page?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Simple answer; you can.
</P
><P
>&#13; The logic behind the page checks every bug in the list to
determine legal state changes, and then only shows you controls
to do things that could apply to <EM
>every</EM
> bug
on the list. The reason for this is that if you try to do something
illegal to a bug, the whole process will grind to a halt, and all
changes after the failed one will <EM
>also</EM
> fail.
Since that isn't a good outcome, the page doesn't even present
you with the option.
</P
><P
>&#13; In practical terms, that means that in order to mark
multiple bugs as CLOSED, then every bug on the page has to be
either RESOLVED or VERIFIED already; if this is not the case,
then the option to close the bugs will not appear on the page.
</P
><P
>&#13; The rationale is that if you pick one of the bugs that's not
VERIFIED and try to CLOSE it, the bug change will fail
miserably (thus killing any changes in the list after it
while doing the bulk change) so it doesn't even give you the
choice.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="faq-hacking"
></A
>9. Bugzilla Hacking</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-hacking-templatestyle"
></A
><B
>A.9.1. </B
>
What kind of style should I use for templatization?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Gerv and Myk suggest a 2-space indent, with embedded code sections on
their own line, in line with outer tags. Like this:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;&#60;fred&#62;
[% IF foo %]
&#60;bar&#62;
[% FOREACH x = barney %]
&#60;tr&#62;
&#60;td&#62;
[% x %]
&#60;/td&#62;
&#60;tr&#62;
[% END %]
[% END %]
&#60;/fred&#62;
</PRE
></FONT
></TD
></TR
></TABLE
><P
> Myk also recommends you turn on PRE_CHOMP in the template
initialization to prevent bloating of HTML with unnecessary whitespace.
</P
><P
>Please note that many have differing opinions on this subject,
and the existing templates in Bugzilla espouse both this and a 4-space
style. Either is acceptable; the above is preferred.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-hacking-bugzillabugs"
></A
><B
>A.9.2. </B
>
What bugs are in Bugzilla right now?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Try <A
HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&#38;bug_status=ASSIGNED&#38;bug_status=REOPENED&#38;product=Bugzilla"
TARGET="_top"
>&#13; this link</A
> to view current bugs or requests for
enhancement for Bugzilla.
</P
><P
>&#13; You can view bugs marked for 2.20.2 release
<A
HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&#38;target_milestone=Bugzilla+&#38;bz-nextver;"
TARGET="_top"
>here</A
>.
This list includes bugs for the 2.20.2 release that have already
been fixed and checked into CVS. Please consult the
<A
HREF="http://www.bugzilla.org/"
TARGET="_top"
>&#13; Bugzilla Project Page</A
> for details on how to
check current sources out of CVS so you can have these
bug fixes early!
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-hacking-priority"
></A
><B
>A.9.3. </B
>
How can I change the default priority to a null value?
For instance, have the default priority be <SPAN
CLASS="QUOTE"
>"---"</SPAN
>
instead of <SPAN
CLASS="QUOTE"
>"P2"</SPAN
>?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
This is well-documented in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
TARGET="_top"
>bug
49862</A
>. Ultimately, it's as easy as adding the
<SPAN
CLASS="QUOTE"
>"---"</SPAN
> priority field to your localconfig file
in the appropriate area, re-running checksetup.pl, and then
changing the default priority in your browser using
<B
CLASS="command"
>editparams.cgi</B
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="faq-hacking-patches"
></A
><B
>A.9.4. </B
>
What's the best way to submit patches? What guidelines
should I follow?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Enter a bug into bugzilla.mozilla.org for the <SPAN
CLASS="QUOTE"
>"<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
TARGET="_top"
>Bugzilla</A
>"</SPAN
>
product.
</P
></LI
><LI
><P
>&#13; Upload your patch as a unified diff (having used <SPAN
CLASS="QUOTE"
>"diff
-u"</SPAN
> against the <EM
>current sources</EM
>
checked out of CVS), or new source file by clicking
<SPAN
CLASS="QUOTE"
>"Create a new attachment"</SPAN
> link on the bug
page you've just created, and include any descriptions of
database changes you may make, into the bug ID you submitted
in step #1. Be sure and click the <SPAN
CLASS="QUOTE"
>"Patch"</SPAN
> checkbox
to indicate the text you are sending is a patch!
</P
></LI
><LI
><P
>&#13; Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX)
for discussion in the newsgroup
(netscape.public.mozilla.webtools). You'll get a
really good, fairly immediate reaction to the
implications of your patch, which will also give us
an idea how well-received the change would be.
</P
></LI
><LI
><P
>&#13; If it passes muster with minimal modification, the
person to whom the bug is assigned in Bugzilla is
responsible for seeing the patch is checked into CVS.
</P
></LI
><LI
><P
>&#13; Bask in the glory of the fact that you helped write
the most successful open-source bug-tracking software
on the planet :)
</P
></LI
></OL
></P
></DIV
></DIV
></DIV
></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="whining.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="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Whining</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Troubleshooting</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>