summaryrefslogtreecommitdiffstats
path: root/docs/html/faq.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/faq.html')
-rw-r--r--docs/html/faq.html3838
1 files changed, 3838 insertions, 0 deletions
diff --git a/docs/html/faq.html b/docs/html/faq.html
new file mode 100644
index 000000000..4977fc915
--- /dev/null
+++ b/docs/html/faq.html
@@ -0,0 +1,3838 @@
+<HTML
+><HEAD
+><TITLE
+>The Bugzilla FAQ</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="PREVIOUS"
+TITLE="The Future of Bugzilla"
+HREF="future.html"><LINK
+REL="NEXT"
+TITLE="Software Download Links"
+HREF="downloadlinks.html"></HEAD
+><BODY
+CLASS="APPENDIX"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="future.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="downloadlinks.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="APPENDIX"
+><H1
+><A
+NAME="FAQ"
+>Appendix A. The Bugzilla FAQ</A
+></H1
+><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#AEN1481"
+> Where can I find information about Bugzilla?</A
+></DT
+><DT
+>A.1.2. <A
+HREF="faq.html#AEN1487"
+> What license is Bugzilla distributed under?
+ </A
+></DT
+><DT
+>A.1.3. <A
+HREF="faq.html#AEN1493"
+> How do I get commercial support for Bugzilla?
+ </A
+></DT
+><DT
+>A.1.4. <A
+HREF="faq.html#AEN1500"
+> What major companies or projects are currently using
+ Bugzilla for bug-tracking?
+ </A
+></DT
+><DT
+>A.1.5. <A
+HREF="faq.html#AEN1525"
+> Who maintains Bugzilla?
+ </A
+></DT
+><DT
+>A.1.6. <A
+HREF="faq.html#AEN1530"
+> How does Bugzilla stack up against other bug-tracking
+ databases?
+ </A
+></DT
+><DT
+>A.1.7. <A
+HREF="faq.html#AEN1537"
+> How do I change my user name in Bugzilla?
+ </A
+></DT
+><DT
+>A.1.8. <A
+HREF="faq.html#AEN1542"
+> Why doesn't Bugzilla offer this or that feature or
+ compatability with this other tracking software?
+ </A
+></DT
+><DT
+>A.1.9. <A
+HREF="faq.html#AEN1549"
+> Why MySQL? I'm interested in seeing Bugzilla run on
+ Oracle/Sybase/Msql/PostgreSQL/MSSQL?
+ </A
+></DT
+><DT
+>A.1.10. <A
+HREF="faq.html#AEN1567"
+> Why do the scripts say "/usr/bonsaitools/bin/perl" instead
+ of "/usr/bin/perl" or something else?
+ </A
+></DT
+></DL
+></DD
+><DT
+>2. <A
+HREF="faq.html#FAQ_REDHAT"
+>Red Hat Bugzilla</A
+></DT
+><DD
+><DL
+><DT
+>A.2.1. <A
+HREF="faq.html#AEN1584"
+> What about Red Hat Bugzilla?
+ </A
+></DT
+><DT
+>A.2.2. <A
+HREF="faq.html#AEN1592"
+> What are the primary benefits of Red Hat Bugzilla?
+ </A
+></DT
+><DT
+>A.2.3. <A
+HREF="faq.html#AEN1620"
+> What's the current status of Red Hat Bugzilla?
+ </A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="faq.html#FAQ_LOKI"
+>Loki Bugzilla (AKA Fenris)</A
+></DT
+><DD
+><DL
+><DT
+>A.3.1. <A
+HREF="faq.html#AEN1636"
+> What about Loki Bugzilla?
+ </A
+></DT
+><DT
+>A.3.2. <A
+HREF="faq.html#AEN1643"
+> Who maintains Fenris (Loki Bugzilla) now?
+ </A
+></DT
+><DT
+>A.3.3. <A
+HREF="faq.html#AEN1648"
+>
+ </A
+></DT
+></DL
+></DD
+><DT
+>4. <A
+HREF="faq.html#FAQ_PHB"
+>Pointy-Haired-Boss Questions</A
+></DT
+><DD
+><DL
+><DT
+>A.4.1. <A
+HREF="faq.html#AEN1656"
+> Is Bugzilla web-based or do you have to have specific
+ software or specific operating system on your machine?
+ </A
+></DT
+><DT
+>A.4.2. <A
+HREF="faq.html#AEN1661"
+> Has anyone you know of already done any Bugzilla
+ integration with Perforce (SCM software)?
+ </A
+></DT
+><DT
+>A.4.3. <A
+HREF="faq.html#AEN1666"
+> Does Bugzilla allow the user to track multiple projects?
+ </A
+></DT
+><DT
+>A.4.4. <A
+HREF="faq.html#AEN1671"
+> 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.4.5. <A
+HREF="faq.html#AEN1676"
+> Does Bugzilla allow attachments (text, screenshots, urls
+ etc)? If yes, are there any that are NOT allowed?
+ </A
+></DT
+><DT
+>A.4.6. <A
+HREF="faq.html#AEN1681"
+> 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.4.7. <A
+HREF="faq.html#AEN1686"
+> The index.html page doesn't show the footer. It's really
+ annoying to have to go to the querypage just to check my
+ "my bugs" link. How do I get a footer on static HTML
+ pages?
+ </A
+></DT
+><DT
+>A.4.8. <A
+HREF="faq.html#AEN1692"
+> Does Bugzilla provide any reporting features, metrics,
+ graphs, etc? You know, the type of stuff that management
+ likes to see. :)
+ </A
+></DT
+><DT
+>A.4.9. <A
+HREF="faq.html#AEN1700"
+> Is there email notification and if so, what do you see
+ when you get an email? Do you see bug number and title or
+ is it only the number?
+ </A
+></DT
+><DT
+>A.4.10. <A
+HREF="faq.html#AEN1705"
+> 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.4.11. <A
+HREF="faq.html#AEN1710"
+> If there is email notification, do users have to have any
+ particular type of email application?
+ </A
+></DT
+><DT
+>A.4.12. <A
+HREF="faq.html#AEN1717"
+> If I just wanted to track certain bugs, as they go
+ through life, can I set it up to alert me via email
+ whenever that bug changes, whether it be owner, status or
+ description etc.?
+ </A
+></DT
+><DT
+>A.4.13. <A
+HREF="faq.html#AEN1722"
+> 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
+></DT
+><DT
+>A.4.14. <A
+HREF="faq.html#AEN1730"
+> Does Bugzilla allow fields to be added, changed or
+ deleted? If I want to customize the bug submission form to
+ meet our needs, can I do that using our terminology?
+ </A
+></DT
+><DT
+>A.4.15. <A
+HREF="faq.html#AEN1735"
+> Has anyone converted Bugzilla to another language to be
+ used in other countries? Is it localizable?
+ </A
+></DT
+><DT
+>A.4.16. <A
+HREF="faq.html#AEN1740"
+> Can a user create and save reports? Can they do this in
+ Word format? Excel format?
+ </A
+></DT
+><DT
+>A.4.17. <A
+HREF="faq.html#AEN1745"
+> Can a user re-run a report with a new project, same query?
+ </A
+></DT
+><DT
+>A.4.18. <A
+HREF="faq.html#AEN1750"
+> Can a user modify an existing report and then save it into
+ another name?
+ </A
+></DT
+><DT
+>A.4.19. <A
+HREF="faq.html#AEN1755"
+> Does Bugzilla have the ability to search by word, phrase,
+ compound search?
+ </A
+></DT
+><DT
+>A.4.20. <A
+HREF="faq.html#AEN1760"
+> Can the admin person establish separate group and
+ individual user privileges?
+ </A
+></DT
+><DT
+>A.4.21. <A
+HREF="faq.html#AEN1765"
+> 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.4.22. <A
+HREF="faq.html#AEN1770"
+> Are there any backup features provided?
+ </A
+></DT
+><DT
+>A.4.23. <A
+HREF="faq.html#AEN1776"
+> Can users be on the system while a backup is in progress?
+ </A
+></DT
+><DT
+>A.4.24. <A
+HREF="faq.html#AEN1781"
+> 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.
+ </A
+></DT
+><DT
+>A.4.25. <A
+HREF="faq.html#AEN1788"
+> 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?
+ </A
+></DT
+><DT
+>A.4.26. <A
+HREF="faq.html#AEN1793"
+> 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
+></DL
+></DD
+><DT
+>5. <A
+HREF="faq.html#FAQ_INSTALL"
+>Bugzilla Installation</A
+></DT
+><DD
+><DL
+><DT
+>A.5.1. <A
+HREF="faq.html#AEN1800"
+> How do I download and install Bugzilla?
+ </A
+></DT
+><DT
+>A.5.2. <A
+HREF="faq.html#AEN1806"
+> How do I install Bugzilla on Windows NT?
+ </A
+></DT
+><DT
+>A.5.3. <A
+HREF="faq.html#AEN1811"
+> Is there an easy way to change the Bugzilla cookie name?
+ </A
+></DT
+></DL
+></DD
+><DT
+>6. <A
+HREF="faq.html#FAQ_SECURITY"
+>Bugzilla Security</A
+></DT
+><DD
+><DL
+><DT
+>A.6.1. <A
+HREF="faq.html#AEN1818"
+> 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.6.2. <A
+HREF="faq.html#AEN1824"
+> Are there any security problems with Bugzilla?
+ </A
+></DT
+><DT
+>A.6.3. <A
+HREF="faq.html#AEN1829"
+> 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
+>7. <A
+HREF="faq.html#FAQ_EMAIL"
+>Bugzilla Email</A
+></DT
+><DD
+><DL
+><DT
+>A.7.1. <A
+HREF="faq.html#AEN1836"
+> 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.7.2. <A
+HREF="faq.html#AEN1841"
+> 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.7.3. <A
+HREF="faq.html#AEN1846"
+> I want whineatnews.pl to whine at something more, or other
+ than, only new bugs. How do I do it?
+ </A
+></DT
+><DT
+>A.7.4. <A
+HREF="faq.html#AEN1852"
+> 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.7.5. <A
+HREF="faq.html#AEN1859"
+> How do I set up the email interface to submit/change bugs
+ via email?
+ </A
+></DT
+><DT
+>A.7.6. <A
+HREF="faq.html#AEN1864"
+> Email takes FOREVER to reach me from bugzilla -- it's
+ extremely slow. What gives?
+ </A
+></DT
+><DT
+>A.7.7. <A
+HREF="faq.html#AEN1871"
+> How come email never reaches me from bugzilla changes?
+ </A
+></DT
+></DL
+></DD
+><DT
+>8. <A
+HREF="faq.html#FAQ_DB"
+>Bugzilla Database</A
+></DT
+><DD
+><DL
+><DT
+>A.8.1. <A
+HREF="faq.html#AEN1879"
+> I've heard Bugzilla can be used with Oracle?
+ </A
+></DT
+><DT
+>A.8.2. <A
+HREF="faq.html#AEN1884"
+> Bugs are missing from queries, but exist in the database
+ (and I can pull them up by specifying the bug ID). What's
+ wrong?
+ </A
+></DT
+><DT
+>A.8.3. <A
+HREF="faq.html#AEN1889"
+> I think my database might be corrupted, or contain invalid
+ entries. What do I do?
+ </A
+></DT
+><DT
+>A.8.4. <A
+HREF="faq.html#AEN1894"
+> I want to manually edit some entries in my database. How?
+ </A
+></DT
+><DT
+>A.8.5. <A
+HREF="faq.html#AEN1899"
+> I try to add myself as a user, but Bugzilla always tells
+ me my password is wrong.
+ </A
+></DT
+><DT
+>A.8.6. <A
+HREF="faq.html#AEN1904"
+> I think I've set up MySQL permissions correctly, but
+ bugzilla still can't connect.
+ </A
+></DT
+><DT
+>A.8.7. <A
+HREF="faq.html#AEN1909"
+> How do I synchronize bug information among multiple
+ different Bugzilla databases?
+ </A
+></DT
+><DT
+>A.8.8. <A
+HREF="faq.html#AEN1916"
+> Why do I get bizarre errors when trying to submit data,
+ particularly problems with "groupset"?
+ </A
+></DT
+><DT
+>A.8.9. <A
+HREF="faq.html#AEN1921"
+> How come even after I delete bugs, the long descriptions
+ show up?
+ </A
+></DT
+></DL
+></DD
+><DT
+>9. <A
+HREF="faq.html#FAQ_NT"
+>Bugzilla and Win32</A
+></DT
+><DD
+><DL
+><DT
+>A.9.1. <A
+HREF="faq.html#AEN1928"
+> What is the easiest way to run Bugzilla on Win32
+ (Win98+/NT/2K)?
+ </A
+></DT
+><DT
+>A.9.2. <A
+HREF="faq.html#AEN1933"
+> Is there a "Bundle::Bugzilla" equivalent for Win32?
+ </A
+></DT
+><DT
+>A.9.3. <A
+HREF="faq.html#AEN1938"
+> CGI's are failing with a "something.cgi is not a valid
+ Windows NT application" error. Why?
+ </A
+></DT
+><DT
+>A.9.4. <A
+HREF="faq.html#AEN1946"
+> Can I have some general instructions on how to make
+ Bugzilla on Win32 work?
+ </A
+></DT
+><DT
+>A.9.5. <A
+HREF="faq.html#AEN1952"
+> I'm having trouble with the perl modules for NT not being
+ able to talk to to the database.
+ </A
+></DT
+></DL
+></DD
+><DT
+>10. <A
+HREF="faq.html#FAQ_USE"
+>Bugzilla Usage</A
+></DT
+><DD
+><DL
+><DT
+>A.10.1. <A
+HREF="faq.html#AEN1973"
+> The query page is very confusing. Isn't there a simpler
+ way to query?
+ </A
+></DT
+><DT
+>A.10.2. <A
+HREF="faq.html#AEN1979"
+> 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?
+ </A
+></DT
+><DT
+>A.10.3. <A
+HREF="faq.html#AEN1989"
+> I can't upload anything into the database via the "Create
+ Attachment" link. What am I doing wrong?
+ </A
+></DT
+><DT
+>A.10.4. <A
+HREF="faq.html#AEN1994"
+> Email submissions to Bugzilla that have attachments end up
+ asking me to save it as a "cgi" file.
+ </A
+></DT
+><DT
+>A.10.5. <A
+HREF="faq.html#AEN1999"
+> How do I change a keyword in Bugzilla, once some bugs are
+ using it?
+ </A
+></DT
+></DL
+></DD
+><DT
+>11. <A
+HREF="faq.html#FAQ_HACKING"
+>Bugzilla Hacking</A
+></DT
+><DD
+><DL
+><DT
+>A.11.1. <A
+HREF="faq.html#AEN2006"
+> What bugs are in Bugzilla right now?
+ </A
+></DT
+><DT
+>A.11.2. <A
+HREF="faq.html#AEN2015"
+> How can I change the default priority to a null value?
+ For instance, have the default priority be "---" instead
+ of "P2"?
+ </A
+></DT
+><DT
+>A.11.3. <A
+HREF="faq.html#AEN2021"
+> 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="AEN1481"
+></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.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+> http://www.mozilla.org/projects/bugzilla/</A
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1487"
+></A
+><B
+>A.1.2. </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="AEN1493"
+></A
+><B
+>A.1.3. </B
+> How do I get commercial support for Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> <A
+HREF="http://www.collab.net/"
+TARGET="_top"
+>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 whore themselves
+ out 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="AEN1500"
+></A
+><B
+>A.1.4. </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 comapanies
+ with public Bugzilla sites to track bugs in their
+ products. A few include:
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Netscape/AOL</TD
+></TR
+><TR
+><TD
+>Mozilla.org</TD
+></TR
+><TR
+><TD
+>AtHome Corporation</TD
+></TR
+><TR
+><TD
+>Red Hat Software</TD
+></TR
+><TR
+><TD
+>Loki Entertainment Software</TD
+></TR
+><TR
+><TD
+>SuSe Corp</TD
+></TR
+><TR
+><TD
+>The Horde Project</TD
+></TR
+><TR
+><TD
+>The Eazel Project</TD
+></TR
+><TR
+><TD
+>AbiSource</TD
+></TR
+><TR
+><TD
+>Real Time Enterprises, Inc</TD
+></TR
+><TR
+><TD
+>Eggheads.org</TD
+></TR
+><TR
+><TD
+>Strata Software</TD
+></TR
+><TR
+><TD
+>RockLinux</TD
+></TR
+><TR
+><TD
+>Creative Labs (makers of SoundBlaster)</TD
+></TR
+><TR
+><TD
+>The Apache Foundation</TD
+></TR
+><TR
+><TD
+>The Gnome Foundation</TD
+></TR
+><TR
+><TD
+>Linux-Mandrake</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ </P
+><P
+> Suffice to say, there are more than enough huge projects
+ using Bugzilla that we can safely say it's extremely
+ popular.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1525"
+></A
+><B
+>A.1.5. </B
+> Who maintains Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> There are many, many contributors from around the world
+ maintaining Bugzilla. The designated "Maintainer" is Tara
+ Hernandez, with QA support by Matthew Tuck. Dan Mosedale
+ and Dawn Endico are employees of Mozilla.org responsible
+ for the installation of Bugzilla there, and are very
+ frequent code contributors. Terry Weissman originally
+ ported Bugzilla, but "these days, Terry just hangs around
+ and heckles." The rest of us are mostly transient
+ developers; Bugzilla suits our needs, and we contribute
+ code as we have needs for updates.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1530"
+></A
+><B
+>A.1.6. </B
+> How does Bugzilla stack up against other bug-tracking
+ databases?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> A year has gone by, and I <EM
+>still</EM
+> can't
+ find any head-to-head comparisons of Bugzilla against
+ other defect-tracking software. However, from my personal
+ experience with other bug-trackers, 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, open source code, greater
+ flexibility, and superior ease-of-use.
+ </P
+><P
+> If you happen to be a commercial Bugzilla vendor, please
+ step forward with a rebuttal so I can include it in the
+ FAQ. We're not in pursuit of Bugzilla ueber alles; we
+ simply love having a powerful, open-source tool to get our
+ jobs done.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1537"
+></A
+><B
+>A.1.7. </B
+> How do I change my user name in Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> You can't. However, the administrative account can, by
+ simply opening your user account in editusers.cgi and
+ changing the login name.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1542"
+></A
+><B
+>A.1.8. </B
+> Why doesn't Bugzilla offer this or that feature or
+ compatability 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. Bugzilla is making tremendous
+ strides in usability, customizability, scalability, and
+ user interface. It is widely considered the most complete
+ and popular open-source bug-tracking software in
+ existence.
+ </P
+><P
+> That doesn't mean it can't use improvement! You can help
+ the project along by either hacking a patch yourself that
+ supports the functionality you require, or else submitting
+ a "Request for Enhancement" (RFE) using the bug submission
+ interface at <A
+HREF="http://bugzilla.mozilla.org/"
+TARGET="_top"
+>bugzilla.mozilla.org</A
+>.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1549"
+></A
+><B
+>A.1.9. </B
+> Why MySQL? I'm interested in seeing Bugzilla run on
+ Oracle/Sybase/Msql/PostgreSQL/MSSQL?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+>Terry Weissman answers,
+ <A
+NAME="AEN1553"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> You're not the only one. But <EM
+>I</EM
+> am
+ not very interested. I'm not a real SQL or database
+ person. I just wanted to make a useful tool, and build
+ it on top of free software. So, I picked MySQL, and
+ learned SQL by staring at the MySQL manual and some
+ code lying around here, and wrote Bugzilla. I didn't
+ know that Enum's were non-standard SQL. I'm not sure
+ if I would have cared, but I didn't even know. So, to
+ me, things are "portable" because it uses MySQL, and
+ MySQL is portable enough. I fully understand (now)
+ that people want to be portable to other databases,
+ but that's never been a real concern of mine.
+ </P
+></BLOCKQUOTE
+>
+ </P
+><P
+> Things aren't quite that grim these days, however. Terry
+ pretty much sums up much of the thinking many of us have
+ for Bugzilla, but there is light on the horizon for
+ database-independence! Here are some options:
+ </P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <EM
+><A
+HREF="http://bugzilla.redhat.com/"
+TARGET="_top"
+>Red
+ Hat Bugzilla</A
+></EM
+>: Runs a modified
+ Bugzilla 2.8 atop an Oracle database.
+ </TD
+></TR
+><TR
+><TD
+> <EM
+><A
+HREF="http://sourceforge.net/projects/interzilla"
+TARGET="_top"
+>Interzilla</A
+></EM
+>: A project to run Bugzilla on Interbase. No code released yet, however.
+ </TD
+></TR
+><TR
+><TD
+> <EM
+>Bugzilla 3.0</EM
+>: One of the primary
+ stated goals is multiple database support.
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1567"
+></A
+><B
+>A.1.10. </B
+> Why do the scripts say "/usr/bonsaitools/bin/perl" instead
+ of "/usr/bin/perl" or something else?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime
+ rule in making submissions is "don't break
+ bugzilla.mozilla.org". If it breaks it, your patch will be
+ reverted faster than you can do a diff.
+ </P
+><P
+> Here's Terry Weissman's comment, for some historical
+ context:
+ <A
+NAME="AEN1572"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> [This was] purely my own convention. I wanted a place
+ to put a version of Perl and other tools that was
+ strictly under my control for the various webtools,
+ and not subject to anyone else. Edit it to point to
+ whatever you like.
+ </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 always recommend that, if possible, you keep the
+ path as /usr/bonsaitools/bin/perl, and simply add a
+ /usr/bonsaitools and /usr/bonsaitools/bin directory,
+ then symlink your version of perl to
+ /usr/bonsaitools/bin/perl. This will make upgrading
+ your Bugzilla much easier in the future.
+ </P
+><P
+> Obviously, if you do not have root access to your
+ Bugzilla box, our suggestion is irrelevant.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></BLOCKQUOTE
+>
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_REDHAT"
+></A
+>2. Red Hat Bugzilla</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
+> <EM
+>This section is no longer up-to-date.</EM
+>
+ Please see the section on "Red Hat Bugzilla" under
+ "Variants" in The Bugzilla Guide.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1584"
+></A
+><B
+>A.2.1. </B
+> What about Red Hat Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Red Hat Bugzilla is arguably more user-friendly,
+ customizable, and scalable than stock Bugzilla. Check it
+ out at http://bugzilla.redhat.com and the sources at
+ ftp://people.redhat.com/dkl/. They've set their Bugzilla
+ up to work with Oracle out of the box. Note that Redhat
+ Bugzilla is based upon the 2.8 Bugzilla tree; Bugzilla has
+ made some tremendous advances since the 2.8 release. Why
+ not download both Bugzillas to check out the differences
+ for yourself?
+ </P
+><P
+> Dave Lawrence, the original Red Hat Bugzilla maintainer,
+ mentions:
+ <A
+NAME="AEN1589"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> Somebody needs to take the ball and run with it. I'm
+ the only maintainer and am very pressed for time.
+ </P
+></BLOCKQUOTE
+> If you, or someone you know, has the time
+ and expertise to do the integration work so main-tree
+ Bugzilla 2.12 and higher integrates the Red Hat Bugzilla
+ Oracle modifications, please donate your time to
+ supporting the Bugzilla project.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1592"
+></A
+><B
+>A.2.2. </B
+> What are the primary benefits of Red Hat Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> <EM
+>Dave Lawrence</EM
+>:
+ <A
+NAME="AEN1597"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> For the record, we are not using any template type
+ implementation for the cosmetic changes maded to
+ Bugzilla. It is just alot of html changes in the code
+ itself. I admit I may have gotten a little carried
+ away with it but the corporate types asked for a more
+ standardized interface to match up with other projects
+ relating to Red Hat web sites. A lot of other web
+ based internal tools I am working on also look like
+ Bugzilla.
+ </P
+><P
+> I do want to land the changes that I have made to
+ Bugzilla but I may have to back out a good deal and
+ make a different version of Red Hat's Bugzilla for
+ checking in to CVS. Especially the cosmetic changes
+ because it seems they may not fit the general public.
+ I will do that as soon as I can. I also still do my
+ regular QA responsibilities along with Bugzilla so
+ time is difficult sometimes to come by.
+ </P
+><P
+> There are also a good deal of other changes that were
+ requested by management for things like support
+ contracts and different permission groups for making
+ bugs private. Here is a short list of the major
+ changes that have been made:
+ </P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> No enum types. All old enum types are now separate
+ smaller tables.
+ </P
+></LI
+><LI
+><P
+> No bit wise operations. Not all databases support
+ this so they were changed to a more generic way of
+ doing this task
+ </P
+></LI
+><LI
+><P
+> Bug reports can only be altered by the reporter,
+ assignee, or a privileged bugzilla user. The rest
+ of the world can see the bug but in a
+ non-changeable format (unless the bug has been
+ marked private). They can however add comments,
+ add and remove themselves from the CC list
+ </P
+></LI
+><LI
+><P
+> Different group scheme. Each group has an id
+ number related to it. There is a user_group table
+ which contains userid to groupid mappings to
+ determine which groups each user belongs to.
+ Additionally there is a bug_group table that has
+ bugid to groupid mappings to show which groups can
+ see a particular bug. If there are no entries for
+ a bug in this table then the bug is public.
+ </P
+></LI
+><LI
+><P
+> Product groups. product_table created to only
+ allow certain products to be visible for certain
+ groups in both bug entry and query. This was
+ particulary helpful for support contracts.
+ </P
+></LI
+><LI
+><P
+> Of course many (too many) changes to Bugzilla code
+ itself to allow use with Oracle and still allow
+ operation with Mysql if so desired. Currently if
+ you use Mysql it is set to use Mysql's old
+ permission scheme to keep breakage to a minimum.
+ Hopefully one day this will standardize on one
+ style which may of course be something completely
+ different.
+ </P
+></LI
+><LI
+><P
+> Uses Text::Template perl module for rendering of
+ the dynamic HTML pages such as enter_bug.cgi,
+ query.cgi, bug_form.pl, and for the header and
+ footer parts of the page. This allows the html to
+ be separate from the perl code for customizing the
+ look and feel of the page to one's preference.
+ </P
+></LI
+><LI
+><P
+> There are many other smaller changes. There is
+ also a port to Oracle that I have been working on
+ as time permits but is not completely finished but
+ somewhat usable. I will merge it into our standard
+ code base when it becomes production quality.
+ Unfortunately there will have to be some
+ conditionals in the code to make it work with
+ other than Oracle due to some differences between
+ Oracle and Mysql.
+ </P
+></LI
+></OL
+><P
+> Both the Mysql and Oracle versions of our current code
+ base are available from ftp://people.redhat.com/dkl.
+ If Terry/Tara wants I can submit patch files for all
+ of the changes I have made and he can determine what
+ is suitable for addition to the main bugzilla cade
+ base. But for me to commit changes to the actual CVS I
+ will need to back out alot of things that are not
+ suitable for the rest of the Bugzilla community. I am
+ open to suggestions.
+ </P
+></BLOCKQUOTE
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1620"
+></A
+><B
+>A.2.3. </B
+> What's the current status of Red Hat Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </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
+> This information is somewhat dated; I last updated it
+ 7 June 2000. Please see the "Variants" section of
+ "The Bugzilla Guide" for more up-to-date information
+ regarding Red Hat Bugzilla.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+> <EM
+>Dave Lawrence</EM
+>:
+ <A
+NAME="AEN1627"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> I suppose the current thread warrants an update
+ on the status of Oracle and bugzilla ;) We have now
+ been running Bugzilla 2.8 on Oracle for the last two
+ days in our production environment. I tried to do as
+ much testing as possible with it before going live
+ which is some of the reason for the long delay. I did
+ not get enough feedback as I would have liked from
+ internal developers to help weed out any bugs still
+ left so I said "Fine, i will take it live and then I
+ will get the feedback I want :)" So it is now starting
+ to stabilize and it running quite well after working
+ feverishly the last two days fixing problems as soon
+ as they came in from the outside world. The current
+ branch in cvs is up2date if anyone would like to grab
+ it and try it out. The oracle _setup.pl is broken
+ right now due to some last minute changes but I will
+ update that soon. Therefore you would probably need to
+ create the database tables the old fashioned way using
+ the supplied sql creation scripts located in the
+ ./oracle directory. We have heavy optimizations in the
+ database it self thanks to the in-house DBA here at
+ Red Hat so it is running quite fast. The database
+ itself is located on a dual PII450 with 1GB ram and 14
+ high voltage differential raided scsi drives. The
+ tables and indexes are partitioned in 4 chuncks across
+ the raided drive which is nice because when ever you
+ need to do a full table scan, it is actually starting
+ in 4 different locations on 4 different drives
+ simultaneously. And the indexes of course are on
+ separate drives from the data so that speeds things up
+ tremendously. When I can find the time I will
+ document all that we have done to get this thing going
+ to help others that may need it.
+ </P
+><P
+> As Matt has mentioned it is still using out-dated code
+ and with a little help I would like to bring
+ everything up to date for eventual incorporation with
+ the main cvs tree. Due to other duties I have with the
+ company any help with this wiould be appreciated. What
+ we are using now is what I call a best first effort.
+ It definitely can be improved on and may even need
+ complete rewrites in a lot of areas. A lot of changes
+ may have to be made in the way Bugzilla does things
+ currently to make this transition to a more generic
+ database interface. Fortunately when making the
+ Oracle changes I made sure I didn't do anything that
+ I would consider Oracle specific and could not be
+ easily done with other databases. Alot of the sql
+ statements need to be broken up into smaller utilities
+ that themselves would need to make decisions on what
+ database they are using but the majority of the code
+ can be made database neutral.
+ </P
+></BLOCKQUOTE
+>
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_LOKI"
+></A
+>3. Loki Bugzilla (AKA Fenris)</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
+> Loki's "Fenris" Bugzilla is based upon the (now ancient)
+ Bugzilla 2.8 tree, and is no longer actively maintained.
+ It works well enough for Loki. Additionally, the major
+ differences in Fenris have now been integrated into the
+ main source tree of Bugzilla, so there's not much reason
+ to go grab the source. I leave this section of the FAQ
+ principally for historical interest, but unless Loki has
+ further input into Bugzilla's future, it will be
+ deprecated in future versions of the Guide.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1636"
+></A
+><B
+>A.3.1. </B
+> What about Loki Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Loki Games has a customized version of Bugzilla available
+ at http://fenris.lokigames.com. From that page,
+ <A
+NAME="AEN1640"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> You may have noticed that Fenris is a fork from
+ Bugzilla-- our patches weren't suitable for
+ integration --and a few people have expressed interest
+ in the code. Fenris has one major improvement over
+ Bugzilla, and that is individual comments are not
+ appended onto a string blob, they are stored as a
+ record in a separate table. This allows you to, for
+ instance, separate comments out according to privilege
+ levels in case your bug database could contain
+ sensitive information not for public eyes. We also
+ provide things like email hiding to protect user's
+ privacy, additional fields such as 'user_affected' in
+ case someone enters someone else's bug, comment
+ editing and deletion, and more conditional system
+ variables than Bugzilla does (turn off attachments,
+ qacontact, etc.).
+ </P
+></BLOCKQUOTE
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1643"
+></A
+><B
+>A.3.2. </B
+> Who maintains Fenris (Loki Bugzilla) now?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Raphael Barrerro &#60;raistlin@lokigames.com&#62;. Michael
+ Vance created the initial fork, but no longer maintains
+ the project.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1648"
+></A
+><B
+>A.3.3. </B
+>
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_PHB"
+></A
+>4. Pointy-Haired-Boss 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
+> The title of this section doesn't mean you're a PHB -- it
+ just means you probably HAVE a PHB who wants to know this
+ :)
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1656"
+></A
+><B
+>A.4.1. </B
+> Is Bugzilla web-based or do you have to have specific
+ software or specific operating system on your machine?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><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="AEN1661"
+></A
+><B
+>A.4.2. </B
+> Has anyone you know of already done any Bugzilla
+ integration 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. The section on Perforce isn't very
+ large, but as the maintainer of the Guide is charged with
+ Perforce/Bugzilla integration by his company, you can
+ expect this section to grow.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1666"
+></A
+><B
+>A.4.3. </B
+> Does Bugzilla allow the user to track multiple projects?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Absolutely! You can track up to a "soft-limit" of around
+ 64 individual "Products", that can each be composed of as
+ many "Components" as you want. Check the Administration
+ section of the Bugzilla Guide for more information
+ regarding setting up Products and Components.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1671"
+></A
+><B
+>A.4.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="AEN1676"
+></A
+><B
+>A.4.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. There are many specific MIME-types that are
+ pre-defined by Bugzilla, but you may specify any arbitrary
+ MIME-type you need when you upload the file. Since all
+ attachments are stored in the database, however, I
+ recommend storing large binary attachments elsewhere in
+ the web server's file system and providing a hyperlink as
+ a comment, or in the provided "URL" field in the bug
+ report.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1681"
+></A
+><B
+>A.4.6. </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
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1686"
+></A
+><B
+>A.4.7. </B
+> The index.html page doesn't show the footer. It's really
+ annoying to have to go to the querypage just to check my
+ "my bugs" link. How do I get a footer on static HTML
+ pages?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> This was a late-breaking question for the Guide, so I just
+ have to quote the relevant newsgroup thread on it.
+ </P
+><P
+CLASS="LITERALLAYOUT"
+>&#62;&nbsp;AFAIK,&nbsp;most&nbsp;sites&nbsp;(even&nbsp;if&nbsp;they&nbsp;have&nbsp;SSI&nbsp;enabled)&nbsp;won't&nbsp;have&nbsp;#exec<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;cmd&nbsp;&#62;&nbsp;enabled.&nbsp;&nbsp;Perhaps&nbsp;what&nbsp;would&nbsp;be&nbsp;better&nbsp;is&nbsp;a&nbsp;#include<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;virtual&nbsp;and&nbsp;a&nbsp;&#62;&nbsp;footer.cgi&nbsp;the&nbsp;basically&nbsp;has&nbsp;the&nbsp;"require<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;'CGI.pl'&nbsp;and&nbsp;PutFooter&nbsp;command.&nbsp;&#62;&nbsp;&#62;&nbsp;Please&nbsp;note&nbsp;that&nbsp;under<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;most&nbsp;configurations,&nbsp;this&nbsp;also&nbsp;requires&nbsp;naming&nbsp;&#62;&nbsp;the&nbsp;file<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;index.html&nbsp;to&nbsp;index.shtml&nbsp;(and&nbsp;making&nbsp;sure&nbsp;that&nbsp;it<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;will&nbsp;&#62;&nbsp;still&nbsp;be&nbsp;reconized&nbsp;as&nbsp;an&nbsp;index).&nbsp;&nbsp;Personally,&nbsp;I<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;think&nbsp;this&nbsp;is&nbsp;better&nbsp;on&nbsp;&#62;&nbsp;a&nbsp;per-installation&nbsp;basis<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;(perhaps&nbsp;add&nbsp;something&nbsp;to&nbsp;the&nbsp;FAQ&nbsp;that&nbsp;says&nbsp;how&nbsp;&#62;&nbsp;to&nbsp;do<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;this).&nbsp;Good&nbsp;point.&nbsp;&nbsp;Yeah,&nbsp;easy&nbsp;enough&nbsp;to&nbsp;do,&nbsp;that&nbsp;it<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;shouldn't&nbsp;be&nbsp;a&nbsp;big&nbsp;deal&nbsp;for&nbsp;someone&nbsp;to&nbsp;take&nbsp;it&nbsp;on&nbsp;if&nbsp;they<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;want&nbsp;it.&nbsp;&nbsp;FAQ&nbsp;is&nbsp;a&nbsp;good&nbsp;place&nbsp;for&nbsp;it.&nbsp;&#62;&nbsp;Dave&nbsp;Miller&nbsp;wrote:<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&#62;&nbsp;&#62;&#62;&nbsp;I&nbsp;did&nbsp;a&nbsp;little&nbsp;experimenting&nbsp;with&nbsp;getting&nbsp;the&nbsp;command<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;menu&nbsp;and&nbsp;footer&nbsp;on&nbsp;&#62;&#62;&nbsp;the&nbsp;end&nbsp;of&nbsp;the&nbsp;index&nbsp;page&nbsp;while<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;leaving&nbsp;it&nbsp;as&nbsp;an&nbsp;HTML&nbsp;file...&nbsp;&#62;&#62;&nbsp;&#62;&#62;&nbsp;I&nbsp;was&nbsp;successful.&nbsp;:)<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&#62;&#62;&nbsp;&#62;&#62;&nbsp;I&nbsp;added&nbsp;this&nbsp;line:&nbsp;&#62;&#62;&nbsp;&#62;&#62;&nbsp;&nbsp;&#62;&#62;&nbsp;&#62;&#62;&nbsp;Just&nbsp;before&nbsp;the<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&#60;/BODY&#62;&nbsp;&#60;/HTML&#62;&nbsp;at&nbsp;the&nbsp;end&nbsp;of&nbsp;the&nbsp;file.&nbsp;&nbsp;And<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;it&nbsp;worked.&nbsp;&#62;&#62;&nbsp;&#62;&#62;&nbsp;Thought&nbsp;I'd&nbsp;toss&nbsp;that&nbsp;out&nbsp;there.&nbsp;&nbsp;Should<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;I&nbsp;check&nbsp;this&nbsp;in?&nbsp;&nbsp;For&nbsp;those&nbsp;that&nbsp;&#62;&#62;&nbsp;have&nbsp;SSI&nbsp;disabled,<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;it'll&nbsp;act&nbsp;like&nbsp;a&nbsp;comment,&nbsp;so&nbsp;I&nbsp;wouldn't&nbsp;think&nbsp;it&nbsp;would&nbsp;&#62;&#62;<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;break&nbsp;anything.<br>
+ &nbsp;&nbsp;</P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1692"
+></A
+><B
+>A.4.8. </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/reports.cgi"
+TARGET="_top"
+> http://bugzilla.mozilla.org/reports.cgi</A
+> for basic reporting facilities.
+ </P
+><P
+> For more advanced reporting, I recommend hooking up a
+ professional reporting package, such as Crystal Reports,
+ and use ODBC to access the MySQL database. You can do a
+ lot through the Query page of Bugzilla as well, but right
+ now Advanced Reporting is much better accomplished through
+ third-party utilities that can interface with the database
+ directly.
+ </P
+><P
+> Advanced Reporting is a Bugzilla 3.X proposed feature.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1700"
+></A
+><B
+>A.4.9. </B
+> Is there email notification and if so, what do you see
+ when you get an email? Do you see bug number and title or
+ is it only the number?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Email notification is user-configurable. The bug id and
+ Topic 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="AEN1705"
+></A
+><B
+>A.4.10. </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="AEN1710"
+></A
+><B
+>A.4.11. </B
+> If there is email notification, 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
+> 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.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1717"
+></A
+><B
+>A.4.12. </B
+> If I just wanted to track certain bugs, as they go
+ through life, can I set it up to alert me via email
+ whenever that bug changes, whether it be owner, status or
+ description etc.?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Yes. Place yourself in the "cc" field of the bug you wish
+ to monitor. Then change your "Notify me of changes to"
+ field in the Email Settings tab of the User Preferences
+ screen in Bugzilla to the "Only those bugs which I am
+ listed on the CC line" option.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1722"
+></A
+><B
+>A.4.13. </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 "matching"
+ 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
+> Mozilla allows data export through a custom DTD in XML
+ format. It does not, however, export to specific formats
+ other than the XML Mozilla DTD. Importing the data into
+ Excel or any other application is left as an exercise for
+ the reader.
+ </P
+><P
+> If you create import filters to other applications from
+ Mozilla's XML, please submit your modifications for
+ inclusion in future Bugzilla distributions.
+ </P
+><P
+> As for data import, any application can send data to
+ Bugzilla through the HTTP protocol, or through Mozilla's
+ XML API. However, it seems kind of silly to put another
+ front-end in front of Bugzilla; it makes more sense to
+ create a simplified bug submission form in HTML. You can
+ find an excellent example at <A
+HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html"
+TARGET="_top"
+> http://www.mozilla.org/quality/help/bugzilla-helper.html</A
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1730"
+></A
+><B
+>A.4.14. </B
+> Does Bugzilla allow fields to be added, changed or
+ deleted? If I want to customize the bug submission form to
+ meet our needs, can I do that using our terminology?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Yes.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1735"
+></A
+><B
+>A.4.15. </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
+> Currently, no. Internationalization support for Perl did
+ not exist in a robust fashion until the recent release of
+ version 5.6.0; Bugzilla is, and likely will remain (until
+ 3.X) completely non-localized.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1740"
+></A
+><B
+>A.4.16. </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. No.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1745"
+></A
+><B
+>A.4.17. </B
+> Can a user re-run a report with a new project, same query?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Yes.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1750"
+></A
+><B
+>A.4.18. </B
+> Can a user modify an existing report and then save it into
+ another name?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> You can save an unlimited number of queries in Bugzilla.
+ You are free to modify them and rename them to your
+ heart's desire.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1755"
+></A
+><B
+>A.4.19. </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="AEN1760"
+></A
+><B
+>A.4.20. </B
+> Can the admin person establish separate group and
+ individual user privileges?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Yes.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1765"
+></A
+><B
+>A.4.21. </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, and offers the offending user a
+ choice of options to deal with the conflict.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1770"
+></A
+><B
+>A.4.22. </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="AEN1776"
+></A
+><B
+>A.4.23. </B
+> Can users be on the system while a backup is in progress?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> 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.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1781"
+></A
+><B
+>A.4.24. </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.
+ </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 completed by
+ unskilled labor. Things like rotate backup tapes and
+ check log files for the word "error".
+ </P
+><P
+> 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.
+ </P
+><P
+> As an example, as of this writing I typically charge $115
+ for the first hour, and $89 each hour thereafter for
+ consulting work. It takes me three to five hours to make
+ Bugzilla happy on a Development installation of
+ Linux-Mandrake.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1788"
+></A
+><B
+>A.4.25. </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 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 with reasonable
+ UNIX or Perl skills to handle your process management and
+ bug-tracking maintenance &#38; customization.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1793"
+></A
+><B
+>A.4.26. </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. MySQL asks, if you find their product valuable, that
+ you purchase a support contract from them that suits your
+ needs.
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_INSTALL"
+></A
+>5. Bugzilla Installation</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1800"
+></A
+><B
+>A.5.1. </B
+> How do I download and install Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Check <A
+HREF="http://www.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+> http://www.mozilla.org/projects/bugzilla/</A
+> for details. Once you download it, untar it, read the Bugzilla Guide.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1806"
+></A
+><B
+>A.5.2. </B
+> How do I install Bugzilla on Windows NT?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Installation on Windows NT has its own section in "The
+ Bugzilla Guide".
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1811"
+></A
+><B
+>A.5.3. </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
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_SECURITY"
+></A
+>6. Bugzilla Security</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1818"
+></A
+><B
+>A.6.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: "mysqld --skip-grant-tables". Please
+ remember <EM
+>this makes mysql as secure as taping a
+ $100 to the floor of a football stadium bathroom for
+ safekeeping.</EM
+> Please read the Security
+ section of the Administration chapter of "The Bugzilla
+ Guide" before proceeding.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1824"
+></A
+><B
+>A.6.2. </B
+> Are there any security problems with Bugzilla?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> The Bugzilla code has not undergone a complete security
+ audit. 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
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1829"
+></A
+><B
+>A.6.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"
+><H3
+><A
+NAME="FAQ_EMAIL"
+></A
+>7. Bugzilla Email</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1836"
+></A
+><B
+>A.7.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
+> With the email changes to 2.12, the user should be able to
+ set this in user email preferences.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1841"
+></A
+><B
+>A.7.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
+> Edit the param for the mail text. Replace "To:" with
+ "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a
+ "To: (myemailaddress)".
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1846"
+></A
+><B
+>A.7.3. </B
+> I want whineatnews.pl to whine at something more, or other
+ than, only new bugs. How do I do it?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Try Klaas Freitag's excellent patch for "whineatassigned"
+ functionality. You can find it at<A
+HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
+TARGET="_top"
+> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
+>. This patch is against an older version of Bugzilla, so you must apply the diffs manually.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1852"
+></A
+><B
+>A.7.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="AEN1856"
+></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="AEN1859"
+></A
+><B
+>A.7.5. </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="AEN1864"
+></A
+><B
+>A.7.6. </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 an alternate Mail Transport Agent (MTA
+ other than sendmail), make sure the options given in the
+ "processmail" script for all instances of "sendmail" are
+ correct for your MTA. If you are using Sendmail, you may
+ wish to delete the "-ODeliveryMode=deferred" option in the
+ "processmail" script for every invocation of "sendmail".
+ (Be sure and leave the "-t" option, though!)
+ </P
+><P
+> A better alternative is to change the "-O" option to
+ "-ODeliveryMode=background". This prevents Sendmail from
+ hanging your Bugzilla Perl processes if the domain to
+ which it must send mail is unavailable.
+ </P
+><P
+> This is now a configurable parameter called "sendmailnow",
+ available from editparams.cgi.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1871"
+></A
+><B
+>A.7.7. </B
+> How come email never reaches me from bugzilla changes?
+ </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 "Log In" link of your Bugzilla
+ installation and clicking the "Email me a password" button
+ after entering your email address.
+ </P
+><P
+> If you never receive mail from Bugzilla, chances you do
+ not have sendmail in "/usr/lib/sendmail". Ensure sendmail
+ lives in, or is symlinked to, "/usr/lib/sendmail".
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_DB"
+></A
+>8. Bugzilla Database</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1879"
+></A
+><B
+>A.8.1. </B
+> I've heard Bugzilla can be used with Oracle?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Red Hat Bugzilla, mentioned above, works with Oracle. The
+ current version from Mozilla.org does not have this
+ capability. Unfortunately, though you will sacrifice a
+ lot of the really great features available in Bugzilla
+ 2.10 and 2.12 if you go with the 2.8-based Redhat version.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1884"
+></A
+><B
+>A.8.2. </B
+> Bugs are missing from queries, but exist in the database
+ (and I can pull them up by specifying the bug ID). What's
+ wrong?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> You've almost certainly enabled the "shadow database",
+ but for some reason it hasn't been updated for all your
+ bugs. This is the database against which queries are run,
+ so that really complex or slow queries won't lock up
+ portions of the database for other users. You can turn off
+ the shadow database in editparams.cgi. If you wish to
+ continue using the shadow database, then as your "bugs"
+ user run "./syncshadowdb -syncall" from the command line
+ in the bugzilla installation directory to recreate your
+ shadow database. After it finishes, be sure to check the
+ params and make sure that "queryagainstshadowdb" is still
+ turned on. The syncshadowdb program turns it off if it was
+ on, and is supposed to turn it back on when completed;
+ that way, if it crashes in the middle of recreating the
+ database, it will stay off forever until someone turns it
+ back on by hand. Apparently, it doesn't always do that
+ yet.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1889"
+></A
+><B
+>A.8.3. </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 "sanity check" utility (./sanitycheck.cgi in the
+ bugzilla_home directory) to see! If it all comes back,
+ you're 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...
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1894"
+></A
+><B
+>A.8.4. </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. However, if you understand SQL
+ you can use the mysqladmin utility to manually insert,
+ delete, and modify table information. Personally, I use
+ "phpMyAdmin". You have to compile a PHP module with MySQL
+ support to make it work, but it's very clean and easy to
+ use.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1899"
+></A
+><B
+>A.8.5. </B
+> I try to add myself as a user, but Bugzilla always tells
+ me my password is wrong.
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Certain version of MySQL (notably, 3.23.29 and 3.23.30)
+ accidentally disabled the "crypt()" function. This
+ prevented MySQL from storing encrypted passwords. Upgrade
+ to the "3.23 stable" version of MySQL and you should be
+ good to go.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1904"
+></A
+><B
+>A.8.6. </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: "mysqld
+ --skip-grant-tables". This will allow you to completely
+ rule out grant tables as the cause of your frustration.
+ However, I do not recommend you run it this way on a
+ regular basis, unless you really want your web site
+ defaced and your machine cracked.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1909"
+></A
+><B
+>A.8.7. </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
+> MySQL has some synchronization features builtin 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
+> If you simply need to transfer bugs from one Bugzilla to
+ another, checkout the "move.pl" script in the Bugzilla
+ distribution.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1916"
+></A
+><B
+>A.8.8. </B
+> Why do I get bizarre errors when trying to submit data,
+ particularly problems with "groupset"?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> If you're sure your MySQL parameters are correct, you
+ might want turn "strictvaluechecks" OFF in editparams.cgi.
+ If you have "usebugsentry" set "On", you also cannot
+ submit a bug as readable by more than one group with
+ "strictvaluechecks" ON.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1921"
+></A
+><B
+>A.8.9. </B
+> How come even after I delete bugs, the long descriptions
+ show up?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Delete everything from $BUZILLA_HOME/shadow. Bugzilla
+ creates shadow files there, with each filename
+ corresponding to a bug number. Also be sure to run
+ syncshadowdb to make sure, if you are using a shadow
+ database, that the shadow database is current.
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_NT"
+></A
+>9. Bugzilla and Win32</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1928"
+></A
+><B
+>A.9.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.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1933"
+></A
+><B
+>A.9.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="AEN1938"
+></A
+><B
+>A.9.3. </B
+> CGI's are failing with a "something.cgi is not a valid
+ Windows NT application" 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
+> Microsoft has some advice on this matter, as well:
+ <A
+NAME="AEN1943"
+></A
+><BLOCKQUOTE
+CLASS="BLOCKQUOTE"
+><P
+> "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:
+ c:\perl\bin\perl.exe %s %s"
+ </P
+></BLOCKQUOTE
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1946"
+></A
+><B
+>A.9.4. </B
+> Can I have some general instructions on how to make
+ Bugzilla on Win32 work?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> The following couple entries are deprecated in favor of
+ the Windows installation instructions available in the
+ "Administration" portion of "The Bugzilla Guide". However,
+ they are provided here for historical interest and
+ insight. <P
+CLASS="LITERALLAYOUT"
+>&nbsp;1.&nbsp;#!C:/perl/bin/perl&nbsp;had&nbsp;to&nbsp;be<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;added&nbsp;to&nbsp;every&nbsp;perl&nbsp;file.&nbsp;2.&nbsp;Converted&nbsp;to&nbsp;Net::SMTP&nbsp;to<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;handle&nbsp;mail&nbsp;messages&nbsp;instead&nbsp;of&nbsp;/usr/bin/sendmail.&nbsp;3.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The&nbsp;crypt&nbsp;function&nbsp;isn't&nbsp;available&nbsp;on&nbsp;Windows&nbsp;NT&nbsp;(at<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;least&nbsp;none&nbsp;that&nbsp;I&nbsp;am&nbsp;aware),&nbsp;so&nbsp;I&nbsp;made&nbsp;encrypted<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;passwords&nbsp;=&nbsp;plaintext&nbsp;passwords.&nbsp;4.&nbsp;The&nbsp;system&nbsp;call&nbsp;to<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;diff&nbsp;had&nbsp;to&nbsp;be&nbsp;changed&nbsp;to&nbsp;the&nbsp;Cygwin&nbsp;diff.&nbsp;5.&nbsp;This&nbsp;was<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;just&nbsp;to&nbsp;get&nbsp;a&nbsp;demo&nbsp;running&nbsp;under&nbsp;NT,&nbsp;it&nbsp;seems&nbsp;to&nbsp;be<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;working&nbsp;good,&nbsp;and&nbsp;I&nbsp;have&nbsp;inserted&nbsp;almost&nbsp;100&nbsp;bugs&nbsp;from<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;another&nbsp;bug&nbsp;tracking&nbsp;system.&nbsp;Since&nbsp;this&nbsp;work&nbsp;was&nbsp;done<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;just&nbsp;to&nbsp;get&nbsp;an&nbsp;in-house&nbsp;demo,&nbsp;I&nbsp;am&nbsp;NOT&nbsp;planning&nbsp;on<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;making&nbsp;a&nbsp;patch&nbsp;for&nbsp;submission&nbsp;to&nbsp;Bugzilla.&nbsp;If&nbsp;you&nbsp;would<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;like&nbsp;a&nbsp;zip&nbsp;file,&nbsp;let&nbsp;me&nbsp;know.&nbsp;Q:&nbsp;Hmm,&nbsp;couldn't&nbsp;figure&nbsp;it<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;out&nbsp;from&nbsp;the&nbsp;general&nbsp;instructions&nbsp;above.&nbsp;&nbsp;How&nbsp;about<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;step-by-step?&nbsp;A:&nbsp;Sure!&nbsp;Here&nbsp;ya&nbsp;go!&nbsp;1.&nbsp;Install&nbsp;IIS&nbsp;4.0<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;the&nbsp;NT&nbsp;Option&nbsp;Pack&nbsp;#4.&nbsp;2.&nbsp;Download&nbsp;and&nbsp;install<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Active&nbsp;Perl.&nbsp;3.&nbsp;Install&nbsp;the&nbsp;Windows&nbsp;GNU&nbsp;tools&nbsp;from<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Cygwin.&nbsp;Make&nbsp;sure&nbsp;to&nbsp;add&nbsp;the&nbsp;bin&nbsp;directory&nbsp;to&nbsp;your<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;system&nbsp;path.&nbsp;(Everyone&nbsp;should&nbsp;have&nbsp;these,&nbsp;whether&nbsp;they<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;decide&nbsp;to&nbsp;use&nbsp;Bugzilla&nbsp;or&nbsp;not.&nbsp;:-)&nbsp;)&nbsp;4.&nbsp;Download<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;relevant&nbsp;packages&nbsp;from&nbsp;ActiveState&nbsp;at<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.activestate.com/packages/zips/.&nbsp;+<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DBD-Mysql.zip&nbsp;5.&nbsp;Extract&nbsp;each&nbsp;zip&nbsp;file&nbsp;with&nbsp;WinZip,&nbsp;and<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;install&nbsp;each&nbsp;ppd&nbsp;file&nbsp;using&nbsp;the&nbsp;notation:&nbsp;ppm&nbsp;install<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#60;module&#62;.ppd&nbsp;6.&nbsp;Install&nbsp;Mysql.&nbsp;&nbsp;*Note:&nbsp;If&nbsp;you&nbsp;move<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the&nbsp;default&nbsp;install&nbsp;from&nbsp;c:\mysql,&nbsp;you&nbsp;must&nbsp;add&nbsp;the<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;appropriate&nbsp;startup&nbsp;parameters&nbsp;to&nbsp;the&nbsp;NT&nbsp;service.&nbsp;(ex.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-b&nbsp;e:\\programs\\mysql)&nbsp;7.&nbsp;Download&nbsp;any&nbsp;Mysql&nbsp;client.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.mysql.com/download_win.html&nbsp;8.&nbsp;Setup&nbsp;MySql.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(These&nbsp;are&nbsp;the&nbsp;commands&nbsp;that&nbsp;I&nbsp;used.)&nbsp;I.&nbsp;Cleanup&nbsp;default<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;database&nbsp;settings.&nbsp;C:\mysql\bin\mysql&nbsp;-u&nbsp;root&nbsp;mysql<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mysql&#62;&nbsp;DELETE&nbsp;FROM&nbsp;user&nbsp;WHERE&nbsp;Host='localhost'&nbsp;AND<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;User='';&nbsp;mysql&#62;&nbsp;quit&nbsp;C:\mysql\bin\mysqladmin&nbsp;reload&nbsp;II.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Set&nbsp;password&nbsp;for&nbsp;root.&nbsp;C:\mysql\bin\mysql&nbsp;-u&nbsp;root&nbsp;mysql<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mysql&#62;&nbsp;UPDATE&nbsp;user&nbsp;SET&nbsp;Password=PASSWORD('new_password')<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;WHERE&nbsp;user='root';&nbsp;mysql&#62;&nbsp;FLUSH&nbsp;PRIVILEGES;&nbsp;mysql&#62;&nbsp;quit<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C:\mysql\bin\mysqladmin&nbsp;-u&nbsp;root&nbsp;reload&nbsp;III.&nbsp;Create&nbsp;bugs<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;user.&nbsp;C:\mysql\bin\mysql&nbsp;-u&nbsp;root&nbsp;-p&nbsp;mysql&#62;&nbsp;insert&nbsp;into<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;user&nbsp;(host,user,password)&nbsp;values('localhost','bugs','');<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mysql&#62;&nbsp;quit&nbsp;C:\mysql\bin\mysqladmin&nbsp;-u&nbsp;root&nbsp;reload&nbsp;IV.<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Create&nbsp;the&nbsp;bugs&nbsp;database.&nbsp;C:\mysql\bin\mysql&nbsp;-u&nbsp;root&nbsp;-p<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mysql&#62;&nbsp;create&nbsp;database&nbsp;bugs;&nbsp;V.&nbsp;Give&nbsp;the&nbsp;bugs&nbsp;user<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;access&nbsp;to&nbsp;the&nbsp;bugs&nbsp;database.&nbsp;mysql&#62;&nbsp;insert&nbsp;into&nbsp;db<br>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv)&nbsp;values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N')&nbsp;mysql&#62;&nbsp;quit&nbsp;C:\mysql\bin\mysqladmin&nbsp;-u&nbsp;root&nbsp;reload&nbsp;9.&nbsp;Run&nbsp;the&nbsp;table&nbsp;scripts&nbsp;to&nbsp;setup&nbsp;the&nbsp;bugs&nbsp;database.&nbsp;10.&nbsp;Change&nbsp;CGI.pm&nbsp;to&nbsp;use&nbsp;the&nbsp;following&nbsp;regular&nbsp;expression&nbsp;because&nbsp;of&nbsp;differing&nbsp;backslashes&nbsp;in&nbsp;NT&nbsp;versus&nbsp;UNIX.&nbsp;o&nbsp;$0&nbsp;=~&nbsp;m:[^\\]*$:;&nbsp;11.&nbsp;Had&nbsp;to&nbsp;make&nbsp;the&nbsp;crypt&nbsp;password&nbsp;=&nbsp;plain&nbsp;text&nbsp;password&nbsp;in&nbsp;the&nbsp;database.&nbsp;(Thanks&nbsp;to&nbsp;Andrew&nbsp;Lahser"&nbsp;&#60;andrew_lahser@merck.com&#62;"&nbsp;on&nbsp;this&nbsp;one.)&nbsp;The&nbsp;files&nbsp;that&nbsp;I&nbsp;changed&nbsp;were:&nbsp;o&nbsp;globals.pl&nbsp;o&nbsp;CGI.pl&nbsp;o&nbsp;alternately,&nbsp;you&nbsp;can&nbsp;try&nbsp;commenting&nbsp;all&nbsp;references&nbsp;to&nbsp;'crypt'&nbsp;string&nbsp;and&nbsp;replace&nbsp;them&nbsp;with&nbsp;similar&nbsp;lines&nbsp;but&nbsp;without&nbsp;encrypt()&nbsp;or&nbsp;crypr()&nbsp;functions&nbsp;insida&nbsp;all&nbsp;files.&nbsp;12.&nbsp;Replaced&nbsp;sendmail&nbsp;with&nbsp;Windmail.&nbsp;Basically,&nbsp;you&nbsp;have&nbsp;to&nbsp;come&nbsp;up&nbsp;with&nbsp;a&nbsp;sendmail&nbsp;substitute&nbsp;for&nbsp;NT.&nbsp;Someone&nbsp;said&nbsp;that&nbsp;they&nbsp;used&nbsp;a&nbsp;Perl&nbsp;module&nbsp;(Net::SMTP),&nbsp;but&nbsp;I&nbsp;was&nbsp;trying&nbsp;to&nbsp;save&nbsp;time&nbsp;and&nbsp;do&nbsp;as&nbsp;little&nbsp;Perl&nbsp;coding&nbsp;as&nbsp;possible.&nbsp;13.&nbsp;Added&nbsp;"perl"&nbsp;to&nbsp;the&nbsp;beginning&nbsp;of&nbsp;all&nbsp;Perl&nbsp;system&nbsp;calls&nbsp;that&nbsp;use&nbsp;a&nbsp;perl&nbsp;script&nbsp;as&nbsp;an&nbsp;argument&nbsp;and&nbsp;renamed&nbsp;processmail&nbsp;to&nbsp;processmail.pl.&nbsp;14.&nbsp;In&nbsp;processmail.pl,&nbsp;I&nbsp;added&nbsp;binmode(HANDLE)&nbsp;before&nbsp;all&nbsp;read()&nbsp;calls.&nbsp;I'm&nbsp;not&nbsp;sure&nbsp;about&nbsp;this&nbsp;one,&nbsp;but&nbsp;the&nbsp;read()&nbsp;under&nbsp;NT&nbsp;wasn't&nbsp;counting&nbsp;the&nbsp;EOLs&nbsp;without&nbsp;the&nbsp;binary&nbsp;read."&nbsp;</P
+>
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1952"
+></A
+><B
+>A.9.5. </B
+> I'm having trouble with the perl modules for NT not being
+ able to talk to 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
+> Hitting http://www.activestate.com/ActivePerl
+ </P
+></LI
+><LI
+><P
+> Download ActivePerl
+ </P
+></LI
+><LI
+><P
+> Go to your prompt
+ </P
+></LI
+><LI
+><P
+> Type 'ppm'
+ </P
+></LI
+><LI
+><P
+> <TT
+CLASS="PROMPT"
+>PPM&#62;</TT
+> <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
+>10. Bugzilla Usage</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1973"
+></A
+><B
+>A.10.1. </B
+> The query page is very confusing. Isn't there a simpler
+ way to query?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> We are developing in that direction. You can follow
+ progress on this at <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"
+TARGET="_top"
+> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A
+>. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html"
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1979"
+></A
+><B
+>A.10.2. </B
+> 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?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> The current behavior is acceptable to bugzilla.mozilla.org
+ and most users. I personally don't like it. You have
+ your choice of patches to change this behavior, however.
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+><A
+HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"
+TARGET="_top"
+> Add a "and accept bug" radio button</A
+></TD
+></TR
+><TR
+><TD
+><A
+HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"
+TARGET="_top"
+> "Accept" button automatically assigns to you</A
+></TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+> Note that these patches are somewhat dated.
+ You will need to do the find and replace manually to apply
+ them. They are very small, though. It is easy.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1989"
+></A
+><B
+>A.10.3. </B
+> I can't upload anything into the database via the "Create
+ Attachment" 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 Netscape, Microsoft, or Mozilla browser to
+ handle uploads correctly.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1994"
+></A
+><B
+>A.10.4. </B
+> Email submissions to Bugzilla that have attachments end up
+ asking me to save it as a "cgi" file.
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> Yup. Just rename it once you download it, or save it
+ under a different filename. This will not be fixed
+ anytime too soon, because it would cripple some other
+ functionality.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN1999"
+></A
+><B
+>A.10.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
+ sanitycheck.cgi to fix it.
+ </P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="QANDADIV"
+><H3
+><A
+NAME="FAQ_HACKING"
+></A
+>11. Bugzilla Hacking</H3
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN2006"
+></A
+><B
+>A.11.1. </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&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"
+TARGET="_top"
+> this link</A
+> to view current bugs or requests for enhancement for Bugzilla.
+ </P
+><P
+> You can view bugs marked for 2.14 release <A
+HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14"
+TARGET="_top"
+>here</A
+>. This list includes bugs for the 2.14 release that have already been fixed and checked into CVS. Please consult the <A
+HREF="http://www.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+> 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="AEN2015"
+></A
+><B
+>A.11.2. </B
+> How can I change the default priority to a null value?
+ For instance, have the default priority be "---" instead
+ of "P2"?
+ </P
+></DIV
+><DIV
+CLASS="ANSWER"
+><P
+><B
+> </B
+> This is well-documented here: <A
+HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
+TARGET="_top"
+> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
+>. Ultimately, it's as easy as adding the "---" priority field to your localconfig file in the appropriate area, re-running checksetup.pl, and then changing the default priority in your browser using "editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle it, but for now it's what we have! Although the bug has been closed "resolved wontfix", there may be a better way to handle this...
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="QANDAENTRY"
+><DIV
+CLASS="QUESTION"
+><P
+><A
+NAME="AEN2021"
+></A
+><B
+>A.11.3. </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
+> Enter a bug into bugzilla.mozilla.org for the
+ "Webtools" product, "Bugzilla" component.
+ </P
+></LI
+><LI
+><P
+> Upload your patch as a unified DIFF (having used
+ "diff -u" against the <EM
+>current
+ sources</EM
+> checked out of CVS), or new
+ source file by clicking "Create a new attachment"
+ 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 "Patch" radio button to indicate
+ the text you are sending is a patch!
+ </P
+></LI
+><LI
+><P
+> Announce your patch and the associated URL
+ (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX)
+ 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
+> 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
+> 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
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="future.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="downloadlinks.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>The Future of Bugzilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Software Download Links</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file