* Bug 191971 - The guide incorrectly stated that you could resolve a bug via email
* Provide an example of a glossary term in the document conventions section
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
+>Term found in the glossary</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <A
+HREF="#gloss-bugzilla"
+><I
+CLASS="glossterm"
+>Bugzilla</I
+></A
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
><HR><H2
CLASS="section"
><A
-NAME="AEN336"
+NAME="AEN340"
></A
>3.2.1. Autolinkification</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN365"
+NAME="AEN369"
></A
>3.2.5. Filing Bugs</H2
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN552"
+NAME="AEN556"
></A
>4.1.5.1. DBI</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN555"
+NAME="AEN559"
></A
>4.1.5.2. Data::Dumper</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN558"
+NAME="AEN562"
></A
>4.1.5.3. MySQL-related modules</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN563"
+NAME="AEN567"
></A
>4.1.5.4. TimeDate modules</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN566"
+NAME="AEN570"
></A
>4.1.5.5. GD (optional)</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN573"
+NAME="AEN577"
></A
>4.1.5.6. Chart::Base (optional)</H3
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN576"
+NAME="AEN580"
></A
>4.1.5.7. Template Toolkit</H3
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN586"
+NAME="AEN590"
></A
>4.1.7. Bugzilla</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN611"
+NAME="AEN615"
></A
>4.1.8. Setting Up the MySQL Database</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN647"
+NAME="AEN651"
></A
>4.1.9. <TT
CLASS="filename"
><HR><H2
CLASS="section"
><A
-NAME="AEN679"
+NAME="AEN683"
></A
>4.1.10. Securing MySQL</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN745"
+NAME="AEN749"
></A
>4.1.11. Configuring Bugzilla</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN751"
+NAME="AEN755"
></A
>4.2.1. Dependency Charts</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN766"
+NAME="AEN770"
></A
>4.2.2. Bug Graphs</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN779"
+NAME="AEN783"
></A
>4.2.3. The Whining Cron</H2
><P
><HR><H4
CLASS="section"
><A
-NAME="AEN926"
+NAME="AEN930"
></A
>4.3.1.3.3. System Calls</H4
><P
COLOR="#000000"
><PRE
CLASS="programlisting"
-> Options +ExecCGI
+> Options +ExecCGI
AllowOverride Limit
</PRE
></FONT
><HR><H2
CLASS="section"
><A
-NAME="AEN1059"
+NAME="AEN1063"
></A
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN1064"
+NAME="AEN1068"
></A
>4.5.2. DBD::Sponge::db prepare failed</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN1409"
+NAME="AEN1413"
></A
>5.7.1. What to Edit</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN1428"
+NAME="AEN1432"
></A
>5.7.2. How To Edit Templates</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN1438"
+NAME="AEN1442"
></A
>5.7.3. Template Formats</H2
><P
><HR><H2
CLASS="section"
><A
-NAME="AEN1451"
+NAME="AEN1455"
></A
>5.7.4. Particular Templates</H2
><P
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
><P
>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
><DL
><DT
>A.1.1. <A
-HREF="#AEN1612"
+HREF="#AEN1617"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="#AEN1618"
+HREF="#AEN1623"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="#AEN1624"
+HREF="#AEN1629"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="#AEN1633"
+HREF="#AEN1638"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="#AEN1657"
+HREF="#AEN1662"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="#AEN1663"
+HREF="#AEN1668"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="#AEN1669"
+HREF="#AEN1674"
> Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
-HREF="#AEN1676"
+HREF="#AEN1681"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
-HREF="#AEN1685"
+HREF="#AEN1690"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
><DT
>A.1.10. <A
-HREF="#AEN1691"
+HREF="#AEN1696"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DL
><DT
>A.2.1. <A
-HREF="#AEN1701"
+HREF="#AEN1706"
> 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="#AEN1706"
+HREF="#AEN1711"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="#AEN1711"
+HREF="#AEN1716"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="#AEN1716"
+HREF="#AEN1721"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="#AEN1721"
+HREF="#AEN1726"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="#AEN1726"
+HREF="#AEN1731"
> 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?
></DT
><DT
>A.2.7. <A
-HREF="#AEN1733"
+HREF="#AEN1738"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="#AEN1740"
+HREF="#AEN1745"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="#AEN1745"
+HREF="#AEN1750"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="#AEN1750"
+HREF="#AEN1755"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="#AEN1757"
+HREF="#AEN1762"
> 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
></DT
><DT
>A.2.12. <A
-HREF="#AEN1769"
+HREF="#AEN1774"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="#AEN1776"
+HREF="#AEN1781"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="#AEN1781"
+HREF="#AEN1786"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="#AEN1786"
+HREF="#AEN1791"
> 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?
></DT
><DT
>A.2.16. <A
-HREF="#AEN1791"
+HREF="#AEN1796"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="#AEN1797"
+HREF="#AEN1802"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="#AEN1802"
+HREF="#AEN1807"
> 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
></DT
><DT
>A.2.19. <A
-HREF="#AEN1808"
+HREF="#AEN1813"
> 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
></DT
><DT
>A.2.20. <A
-HREF="#AEN1813"
+HREF="#AEN1818"
> 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
><DL
><DT
>A.3.1. <A
-HREF="#AEN1820"
+HREF="#AEN1825"
> 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.3.2. <A
-HREF="#AEN1826"
+HREF="#AEN1831"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="#AEN1831"
+HREF="#AEN1836"
> 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.
><DL
><DT
>A.4.1. <A
-HREF="#AEN1838"
+HREF="#AEN1843"
> 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.4.2. <A
-HREF="#AEN1844"
+HREF="#AEN1849"
> 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.4.3. <A
-HREF="#AEN1849"
+HREF="#AEN1854"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="#AEN1855"
+HREF="#AEN1860"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="#AEN1862"
+HREF="#AEN1867"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="#AEN1867"
+HREF="#AEN1872"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="#AEN1874"
+HREF="#AEN1879"
> How come email from Bugzilla changes never reaches me?
</A
></DT
><DL
><DT
>A.5.1. <A
-HREF="#AEN1882"
+HREF="#AEN1887"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="#AEN1887"
+HREF="#AEN1892"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="#AEN1895"
+HREF="#AEN1900"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="#AEN1903"
+HREF="#AEN1908"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
>A.5.5. <A
-HREF="#AEN1911"
+HREF="#AEN1916"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
><DL
><DT
>A.6.1. <A
-HREF="#AEN1920"
+HREF="#AEN1925"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="#AEN1925"
+HREF="#AEN1930"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="#AEN1930"
+HREF="#AEN1935"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="#AEN1938"
+HREF="#AEN1943"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
><DL
><DT
>A.7.1. <A
-HREF="#AEN1959"
+HREF="#AEN1964"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="#AEN1964"
+HREF="#AEN1969"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="#AEN1969"
+HREF="#AEN1974"
> 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.7.4. <A
-HREF="#AEN1979"
+HREF="#AEN1984"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="#AEN1984"
+HREF="#AEN1989"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DL
><DT
>A.8.1. <A
-HREF="#AEN1991"
+HREF="#AEN1996"
> What kind of style should I use for templatization?
</A
></DT
><DT
>A.8.2. <A
-HREF="#AEN1999"
+HREF="#AEN2004"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.3. <A
-HREF="#AEN2008"
+HREF="#AEN2013"
> 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.8.4. <A
-HREF="#AEN2014"
+HREF="#AEN2019"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
CLASS="question"
><P
><A
-NAME="AEN1612"
+NAME="AEN1617"
></A
><B
>A.1.1. </B
CLASS="question"
><P
><A
-NAME="AEN1618"
+NAME="AEN1623"
></A
><B
>A.1.2. </B
CLASS="question"
><P
><A
-NAME="AEN1624"
+NAME="AEN1629"
></A
><B
>A.1.3. </B
CLASS="question"
><P
><A
-NAME="AEN1633"
+NAME="AEN1638"
></A
><B
>A.1.4. </B
CLASS="question"
><P
><A
-NAME="AEN1657"
+NAME="AEN1662"
></A
><B
>A.1.5. </B
CLASS="question"
><P
><A
-NAME="AEN1663"
+NAME="AEN1668"
></A
><B
>A.1.6. </B
CLASS="question"
><P
><A
-NAME="AEN1669"
+NAME="AEN1674"
></A
><B
>A.1.7. </B
CLASS="question"
><P
><A
-NAME="AEN1676"
+NAME="AEN1681"
></A
><B
>A.1.8. </B
CLASS="question"
><P
><A
-NAME="AEN1685"
+NAME="AEN1690"
></A
><B
>A.1.9. </B
CLASS="question"
><P
><A
-NAME="AEN1691"
+NAME="AEN1696"
></A
><B
>A.1.10. </B
CLASS="question"
><P
><A
-NAME="AEN1701"
+NAME="AEN1706"
></A
><B
>A.2.1. </B
CLASS="question"
><P
><A
-NAME="AEN1706"
+NAME="AEN1711"
></A
><B
>A.2.2. </B
CLASS="question"
><P
><A
-NAME="AEN1711"
+NAME="AEN1716"
></A
><B
>A.2.3. </B
CLASS="question"
><P
><A
-NAME="AEN1716"
+NAME="AEN1721"
></A
><B
>A.2.4. </B
CLASS="question"
><P
><A
-NAME="AEN1721"
+NAME="AEN1726"
></A
><B
>A.2.5. </B
CLASS="question"
><P
><A
-NAME="AEN1726"
+NAME="AEN1731"
></A
><B
>A.2.6. </B
CLASS="question"
><P
><A
-NAME="AEN1733"
+NAME="AEN1738"
></A
><B
>A.2.7. </B
CLASS="question"
><P
><A
-NAME="AEN1740"
+NAME="AEN1745"
></A
><B
>A.2.8. </B
CLASS="question"
><P
><A
-NAME="AEN1745"
+NAME="AEN1750"
></A
><B
>A.2.9. </B
CLASS="question"
><P
><A
-NAME="AEN1750"
+NAME="AEN1755"
></A
><B
>A.2.10. </B
CLASS="question"
><P
><A
-NAME="AEN1757"
+NAME="AEN1762"
></A
><B
>A.2.11. </B
CLASS="question"
><P
><A
-NAME="AEN1769"
+NAME="AEN1774"
></A
><B
>A.2.12. </B
CLASS="question"
><P
><A
-NAME="AEN1776"
+NAME="AEN1781"
></A
><B
>A.2.13. </B
CLASS="question"
><P
><A
-NAME="AEN1781"
+NAME="AEN1786"
></A
><B
>A.2.14. </B
CLASS="question"
><P
><A
-NAME="AEN1786"
+NAME="AEN1791"
></A
><B
>A.2.15. </B
CLASS="question"
><P
><A
-NAME="AEN1791"
+NAME="AEN1796"
></A
><B
>A.2.16. </B
CLASS="question"
><P
><A
-NAME="AEN1797"
+NAME="AEN1802"
></A
><B
>A.2.17. </B
CLASS="question"
><P
><A
-NAME="AEN1802"
+NAME="AEN1807"
></A
><B
>A.2.18. </B
CLASS="question"
><P
><A
-NAME="AEN1808"
+NAME="AEN1813"
></A
><B
>A.2.19. </B
CLASS="question"
><P
><A
-NAME="AEN1813"
+NAME="AEN1818"
></A
><B
>A.2.20. </B
CLASS="question"
><P
><A
-NAME="AEN1820"
+NAME="AEN1825"
></A
><B
>A.3.1. </B
CLASS="question"
><P
><A
-NAME="AEN1826"
+NAME="AEN1831"
></A
><B
>A.3.2. </B
CLASS="question"
><P
><A
-NAME="AEN1831"
+NAME="AEN1836"
></A
><B
>A.3.3. </B
CLASS="question"
><P
><A
-NAME="AEN1838"
+NAME="AEN1843"
></A
><B
>A.4.1. </B
CLASS="question"
><P
><A
-NAME="AEN1844"
+NAME="AEN1849"
></A
><B
>A.4.2. </B
CLASS="question"
><P
><A
-NAME="AEN1849"
+NAME="AEN1854"
></A
><B
>A.4.3. </B
CLASS="question"
><P
><A
-NAME="AEN1855"
+NAME="AEN1860"
></A
><B
>A.4.4. </B
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1859"
+NAME="AEN1864"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN1862"
+NAME="AEN1867"
></A
><B
>A.4.5. </B
CLASS="question"
><P
><A
-NAME="AEN1867"
+NAME="AEN1872"
></A
><B
>A.4.6. </B
CLASS="question"
><P
><A
-NAME="AEN1874"
+NAME="AEN1879"
></A
><B
>A.4.7. </B
CLASS="question"
><P
><A
-NAME="AEN1882"
+NAME="AEN1887"
></A
><B
>A.5.1. </B
CLASS="question"
><P
><A
-NAME="AEN1887"
+NAME="AEN1892"
></A
><B
>A.5.2. </B
CLASS="question"
><P
><A
-NAME="AEN1895"
+NAME="AEN1900"
></A
><B
>A.5.3. </B
CLASS="question"
><P
><A
-NAME="AEN1903"
+NAME="AEN1908"
></A
><B
>A.5.4. </B
CLASS="question"
><P
><A
-NAME="AEN1911"
+NAME="AEN1916"
></A
><B
>A.5.5. </B
CLASS="question"
><P
><A
-NAME="AEN1920"
+NAME="AEN1925"
></A
><B
>A.6.1. </B
CLASS="question"
><P
><A
-NAME="AEN1925"
+NAME="AEN1930"
></A
><B
>A.6.2. </B
CLASS="question"
><P
><A
-NAME="AEN1930"
+NAME="AEN1935"
></A
><B
>A.6.3. </B
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1935"
+NAME="AEN1940"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN1938"
+NAME="AEN1943"
></A
><B
>A.6.4. </B
CLASS="question"
><P
><A
-NAME="AEN1959"
+NAME="AEN1964"
></A
><B
>A.7.1. </B
CLASS="question"
><P
><A
-NAME="AEN1964"
+NAME="AEN1969"
></A
><B
>A.7.2. </B
CLASS="question"
><P
><A
-NAME="AEN1969"
+NAME="AEN1974"
></A
><B
>A.7.3. </B
CLASS="question"
><P
><A
-NAME="AEN1979"
+NAME="AEN1984"
></A
><B
>A.7.4. </B
CLASS="question"
><P
><A
-NAME="AEN1984"
+NAME="AEN1989"
></A
><B
>A.7.5. </B
CLASS="question"
><P
><A
-NAME="AEN1991"
+NAME="AEN1996"
></A
><B
>A.8.1. </B
CLASS="question"
><P
><A
-NAME="AEN1999"
+NAME="AEN2004"
></A
><B
>A.8.2. </B
CLASS="question"
><P
><A
-NAME="AEN2008"
+NAME="AEN2013"
></A
><B
>A.8.3. </B
CLASS="question"
><P
><A
-NAME="AEN2014"
+NAME="AEN2019"
></A
><B
>A.8.4. </B
><HR><H2
CLASS="section"
><A
-NAME="AEN2057"
+NAME="AEN2062"
></A
>B.2.1. Bugzilla Database Basics</H2
><P
><HR><H3
CLASS="section"
><A
-NAME="AEN2084"
+NAME="AEN2089"
></A
>B.2.1.1. Bugzilla Database Tables</H3
><P
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2172"
+NAME="AEN2177"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
-NAME="AEN2262"
+NAME="AEN2267"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2267"
+NAME="AEN2272"
></A
>0-9, high ascii</H1
><DL
"Find" box.</P
></DD
><DT
+><A
+NAME="gloss-bugzilla"
+></A
><B
>Bugzilla</B
></DT
><DL
><DT
>5.7.1. <A
-HREF="cust-templates.html#AEN1409"
+HREF="cust-templates.html#AEN1413"
>What to Edit</A
></DT
><DT
>5.7.2. <A
-HREF="cust-templates.html#AEN1428"
+HREF="cust-templates.html#AEN1432"
>How To Edit Templates</A
></DT
><DT
>5.7.3. <A
-HREF="cust-templates.html#AEN1438"
+HREF="cust-templates.html#AEN1442"
>Template Formats</A
></DT
><DT
>5.7.4. <A
-HREF="cust-templates.html#AEN1451"
+HREF="cust-templates.html#AEN1455"
>Particular Templates</A
></DT
></DL
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
+>Term found in the glossary</TD
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
+> <A
+HREF="glossary.html#gloss-bugzilla"
+><I
+CLASS="glossterm"
+>Bugzilla</I
+></A
+>
+ </TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
><H2
CLASS="section"
><A
-NAME="AEN1409"
+NAME="AEN1413"
></A
>5.7.1. What to Edit</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN1428"
+NAME="AEN1432"
></A
>5.7.2. How To Edit Templates</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN1438"
+NAME="AEN1442"
></A
>5.7.3. Template Formats</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN1451"
+NAME="AEN1455"
></A
>5.7.4. Particular Templates</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN2057"
+NAME="AEN2062"
></A
>B.2.1. Bugzilla Database Basics</H2
><P
><H3
CLASS="section"
><A
-NAME="AEN2084"
+NAME="AEN2089"
></A
>B.2.1.1. Bugzilla Database Tables</H3
><P
><H2
CLASS="section"
><A
-NAME="AEN751"
+NAME="AEN755"
></A
>4.2.1. Dependency Charts</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN766"
+NAME="AEN770"
></A
>4.2.2. Bug Graphs</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN779"
+NAME="AEN783"
></A
>4.2.3. The Whining Cron</H2
><P
><DL
><DT
>A.1.1. <A
-HREF="faq.html#AEN1612"
+HREF="faq.html#AEN1617"
> Where can I find information about Bugzilla?</A
></DT
><DT
>A.1.2. <A
-HREF="faq.html#AEN1618"
+HREF="faq.html#AEN1623"
> What license is Bugzilla distributed under?
</A
></DT
><DT
>A.1.3. <A
-HREF="faq.html#AEN1624"
+HREF="faq.html#AEN1629"
> How do I get commercial support for Bugzilla?
</A
></DT
><DT
>A.1.4. <A
-HREF="faq.html#AEN1633"
+HREF="faq.html#AEN1638"
> What major companies or projects are currently using Bugzilla
for bug-tracking?
</A
></DT
><DT
>A.1.5. <A
-HREF="faq.html#AEN1657"
+HREF="faq.html#AEN1662"
> Who maintains Bugzilla?
</A
></DT
><DT
>A.1.6. <A
-HREF="faq.html#AEN1663"
+HREF="faq.html#AEN1668"
> How does Bugzilla stack up against other bug-tracking databases?
</A
></DT
><DT
>A.1.7. <A
-HREF="faq.html#AEN1669"
+HREF="faq.html#AEN1674"
> Why doesn't Bugzilla offer this or that feature or compatibility
with this other tracking software?
</A
></DT
><DT
>A.1.8. <A
-HREF="faq.html#AEN1676"
+HREF="faq.html#AEN1681"
> Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</A
></DT
><DT
>A.1.9. <A
-HREF="faq.html#AEN1685"
+HREF="faq.html#AEN1690"
> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
"/usr/bin/perl" or something else?
</A
></DT
><DT
>A.1.10. <A
-HREF="faq.html#AEN1691"
+HREF="faq.html#AEN1696"
> Is there an easy way to change the Bugzilla cookie name?
</A
></DT
><DL
><DT
>A.2.1. <A
-HREF="faq.html#AEN1701"
+HREF="faq.html#AEN1706"
> 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#AEN1706"
+HREF="faq.html#AEN1711"
> Can Bugzilla integrate with
Perforce (SCM software)?
</A
></DT
><DT
>A.2.3. <A
-HREF="faq.html#AEN1711"
+HREF="faq.html#AEN1716"
> Does Bugzilla allow the user to track multiple projects?
</A
></DT
><DT
>A.2.4. <A
-HREF="faq.html#AEN1716"
+HREF="faq.html#AEN1721"
> If I am on many projects, and search for all bugs assigned to me, will
Bugzilla list them for me and allow me to sort by project, severity etc?
</A
></DT
><DT
>A.2.5. <A
-HREF="faq.html#AEN1721"
+HREF="faq.html#AEN1726"
> Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</A
></DT
><DT
>A.2.6. <A
-HREF="faq.html#AEN1726"
+HREF="faq.html#AEN1731"
> 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?
></DT
><DT
>A.2.7. <A
-HREF="faq.html#AEN1733"
+HREF="faq.html#AEN1738"
> Does Bugzilla provide any reporting features, metrics, graphs, etc? You
know, the type of stuff that management likes to see. :)
</A
></DT
><DT
>A.2.8. <A
-HREF="faq.html#AEN1740"
+HREF="faq.html#AEN1745"
> Is there email notification and if so, what do you see when you get an
email?
</A
></DT
><DT
>A.2.9. <A
-HREF="faq.html#AEN1745"
+HREF="faq.html#AEN1750"
> Can email notification be set up to send to multiple
people, some on the To List, CC List, BCC List etc?
</A
></DT
><DT
>A.2.10. <A
-HREF="faq.html#AEN1750"
+HREF="faq.html#AEN1755"
> Do users have to have any particular
type of email application?
</A
></DT
><DT
>A.2.11. <A
-HREF="faq.html#AEN1757"
+HREF="faq.html#AEN1762"
> 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
></DT
><DT
>A.2.12. <A
-HREF="faq.html#AEN1769"
+HREF="faq.html#AEN1774"
> Has anyone converted Bugzilla to another language to be used in other
countries? Is it localizable?
</A
></DT
><DT
>A.2.13. <A
-HREF="faq.html#AEN1776"
+HREF="faq.html#AEN1781"
> Can a user create and save reports? Can they do this in Word format?
Excel format?
</A
></DT
><DT
>A.2.14. <A
-HREF="faq.html#AEN1781"
+HREF="faq.html#AEN1786"
> Does Bugzilla have the ability to search by word, phrase, compound
search?
</A
></DT
><DT
>A.2.15. <A
-HREF="faq.html#AEN1786"
+HREF="faq.html#AEN1791"
> 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?
></DT
><DT
>A.2.16. <A
-HREF="faq.html#AEN1791"
+HREF="faq.html#AEN1796"
> Are there any backup features provided?
</A
></DT
><DT
>A.2.17. <A
-HREF="faq.html#AEN1797"
+HREF="faq.html#AEN1802"
> Can users be on the system while a backup is in progress?
</A
></DT
><DT
>A.2.18. <A
-HREF="faq.html#AEN1802"
+HREF="faq.html#AEN1807"
> 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
></DT
><DT
>A.2.19. <A
-HREF="faq.html#AEN1808"
+HREF="faq.html#AEN1813"
> 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
></DT
><DT
>A.2.20. <A
-HREF="faq.html#AEN1813"
+HREF="faq.html#AEN1818"
> 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
><DL
><DT
>A.3.1. <A
-HREF="faq.html#AEN1820"
+HREF="faq.html#AEN1825"
> 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.3.2. <A
-HREF="faq.html#AEN1826"
+HREF="faq.html#AEN1831"
> Are there any security problems with Bugzilla?
</A
></DT
><DT
>A.3.3. <A
-HREF="faq.html#AEN1831"
+HREF="faq.html#AEN1836"
> 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.
><DL
><DT
>A.4.1. <A
-HREF="faq.html#AEN1838"
+HREF="faq.html#AEN1843"
> 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.4.2. <A
-HREF="faq.html#AEN1844"
+HREF="faq.html#AEN1849"
> 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.4.3. <A
-HREF="faq.html#AEN1849"
+HREF="faq.html#AEN1854"
> I want whineatnews.pl to whine at something more, or other than, only new
bugs. How do I do it?
</A
></DT
><DT
>A.4.4. <A
-HREF="faq.html#AEN1855"
+HREF="faq.html#AEN1860"
> I don't like/want to use Procmail to hand mail off to bug_email.pl.
What alternatives do I have?
</A
></DT
><DT
>A.4.5. <A
-HREF="faq.html#AEN1862"
+HREF="faq.html#AEN1867"
> How do I set up the email interface to submit/change bugs via email?
</A
></DT
><DT
>A.4.6. <A
-HREF="faq.html#AEN1867"
+HREF="faq.html#AEN1872"
> Email takes FOREVER to reach me from Bugzilla -- it's extremely slow.
What gives?
</A
></DT
><DT
>A.4.7. <A
-HREF="faq.html#AEN1874"
+HREF="faq.html#AEN1879"
> How come email from Bugzilla changes never reaches me?
</A
></DT
><DL
><DT
>A.5.1. <A
-HREF="faq.html#AEN1882"
+HREF="faq.html#AEN1887"
> I've heard Bugzilla can be used with Oracle?
</A
></DT
><DT
>A.5.2. <A
-HREF="faq.html#AEN1887"
+HREF="faq.html#AEN1892"
> I think my database might be corrupted, or contain invalid entries. What
do I do?
</A
></DT
><DT
>A.5.3. <A
-HREF="faq.html#AEN1895"
+HREF="faq.html#AEN1900"
> I want to manually edit some entries in my database. How?
</A
></DT
><DT
>A.5.4. <A
-HREF="faq.html#AEN1903"
+HREF="faq.html#AEN1908"
> I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</A
></DT
><DT
>A.5.5. <A
-HREF="faq.html#AEN1911"
+HREF="faq.html#AEN1916"
> How do I synchronize bug information among multiple different Bugzilla
databases?
</A
><DL
><DT
>A.6.1. <A
-HREF="faq.html#AEN1920"
+HREF="faq.html#AEN1925"
> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
</A
></DT
><DT
>A.6.2. <A
-HREF="faq.html#AEN1925"
+HREF="faq.html#AEN1930"
> Is there a "Bundle::Bugzilla" equivalent for Win32?
</A
></DT
><DT
>A.6.3. <A
-HREF="faq.html#AEN1930"
+HREF="faq.html#AEN1935"
> CGI's are failing with a "something.cgi is not a valid Windows NT
application" error. Why?
</A
></DT
><DT
>A.6.4. <A
-HREF="faq.html#AEN1938"
+HREF="faq.html#AEN1943"
> I'm having trouble with the perl modules for NT not being able to talk to
to the database.
</A
><DL
><DT
>A.7.1. <A
-HREF="faq.html#AEN1959"
+HREF="faq.html#AEN1964"
> How do I change my user name (email address) in Bugzilla?
</A
></DT
><DT
>A.7.2. <A
-HREF="faq.html#AEN1964"
+HREF="faq.html#AEN1969"
> The query page is very confusing. Isn't there a simpler way to query?
</A
></DT
><DT
>A.7.3. <A
-HREF="faq.html#AEN1969"
+HREF="faq.html#AEN1974"
> 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.7.4. <A
-HREF="faq.html#AEN1979"
+HREF="faq.html#AEN1984"
> I can't upload anything into the database via the "Create Attachment"
link. What am I doing wrong?
</A
></DT
><DT
>A.7.5. <A
-HREF="faq.html#AEN1984"
+HREF="faq.html#AEN1989"
> How do I change a keyword in Bugzilla, once some bugs are using it?
</A
></DT
><DL
><DT
>A.8.1. <A
-HREF="faq.html#AEN1991"
+HREF="faq.html#AEN1996"
> What kind of style should I use for templatization?
</A
></DT
><DT
>A.8.2. <A
-HREF="faq.html#AEN1999"
+HREF="faq.html#AEN2004"
> What bugs are in Bugzilla right now?
</A
></DT
><DT
>A.8.3. <A
-HREF="faq.html#AEN2008"
+HREF="faq.html#AEN2013"
> 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.8.4. <A
-HREF="faq.html#AEN2014"
+HREF="faq.html#AEN2019"
> What's the best way to submit patches? What guidelines should I follow?
</A
></DT
CLASS="question"
><P
><A
-NAME="AEN1612"
+NAME="AEN1617"
></A
><B
>A.1.1. </B
CLASS="question"
><P
><A
-NAME="AEN1618"
+NAME="AEN1623"
></A
><B
>A.1.2. </B
CLASS="question"
><P
><A
-NAME="AEN1624"
+NAME="AEN1629"
></A
><B
>A.1.3. </B
CLASS="question"
><P
><A
-NAME="AEN1633"
+NAME="AEN1638"
></A
><B
>A.1.4. </B
CLASS="question"
><P
><A
-NAME="AEN1657"
+NAME="AEN1662"
></A
><B
>A.1.5. </B
CLASS="question"
><P
><A
-NAME="AEN1663"
+NAME="AEN1668"
></A
><B
>A.1.6. </B
CLASS="question"
><P
><A
-NAME="AEN1669"
+NAME="AEN1674"
></A
><B
>A.1.7. </B
CLASS="question"
><P
><A
-NAME="AEN1676"
+NAME="AEN1681"
></A
><B
>A.1.8. </B
CLASS="question"
><P
><A
-NAME="AEN1685"
+NAME="AEN1690"
></A
><B
>A.1.9. </B
CLASS="question"
><P
><A
-NAME="AEN1691"
+NAME="AEN1696"
></A
><B
>A.1.10. </B
CLASS="question"
><P
><A
-NAME="AEN1701"
+NAME="AEN1706"
></A
><B
>A.2.1. </B
CLASS="question"
><P
><A
-NAME="AEN1706"
+NAME="AEN1711"
></A
><B
>A.2.2. </B
CLASS="question"
><P
><A
-NAME="AEN1711"
+NAME="AEN1716"
></A
><B
>A.2.3. </B
CLASS="question"
><P
><A
-NAME="AEN1716"
+NAME="AEN1721"
></A
><B
>A.2.4. </B
CLASS="question"
><P
><A
-NAME="AEN1721"
+NAME="AEN1726"
></A
><B
>A.2.5. </B
CLASS="question"
><P
><A
-NAME="AEN1726"
+NAME="AEN1731"
></A
><B
>A.2.6. </B
CLASS="question"
><P
><A
-NAME="AEN1733"
+NAME="AEN1738"
></A
><B
>A.2.7. </B
CLASS="question"
><P
><A
-NAME="AEN1740"
+NAME="AEN1745"
></A
><B
>A.2.8. </B
CLASS="question"
><P
><A
-NAME="AEN1745"
+NAME="AEN1750"
></A
><B
>A.2.9. </B
CLASS="question"
><P
><A
-NAME="AEN1750"
+NAME="AEN1755"
></A
><B
>A.2.10. </B
CLASS="question"
><P
><A
-NAME="AEN1757"
+NAME="AEN1762"
></A
><B
>A.2.11. </B
CLASS="question"
><P
><A
-NAME="AEN1769"
+NAME="AEN1774"
></A
><B
>A.2.12. </B
CLASS="question"
><P
><A
-NAME="AEN1776"
+NAME="AEN1781"
></A
><B
>A.2.13. </B
CLASS="question"
><P
><A
-NAME="AEN1781"
+NAME="AEN1786"
></A
><B
>A.2.14. </B
CLASS="question"
><P
><A
-NAME="AEN1786"
+NAME="AEN1791"
></A
><B
>A.2.15. </B
CLASS="question"
><P
><A
-NAME="AEN1791"
+NAME="AEN1796"
></A
><B
>A.2.16. </B
CLASS="question"
><P
><A
-NAME="AEN1797"
+NAME="AEN1802"
></A
><B
>A.2.17. </B
CLASS="question"
><P
><A
-NAME="AEN1802"
+NAME="AEN1807"
></A
><B
>A.2.18. </B
CLASS="question"
><P
><A
-NAME="AEN1808"
+NAME="AEN1813"
></A
><B
>A.2.19. </B
CLASS="question"
><P
><A
-NAME="AEN1813"
+NAME="AEN1818"
></A
><B
>A.2.20. </B
CLASS="question"
><P
><A
-NAME="AEN1820"
+NAME="AEN1825"
></A
><B
>A.3.1. </B
CLASS="question"
><P
><A
-NAME="AEN1826"
+NAME="AEN1831"
></A
><B
>A.3.2. </B
CLASS="question"
><P
><A
-NAME="AEN1831"
+NAME="AEN1836"
></A
><B
>A.3.3. </B
CLASS="question"
><P
><A
-NAME="AEN1838"
+NAME="AEN1843"
></A
><B
>A.4.1. </B
CLASS="question"
><P
><A
-NAME="AEN1844"
+NAME="AEN1849"
></A
><B
>A.4.2. </B
CLASS="question"
><P
><A
-NAME="AEN1849"
+NAME="AEN1854"
></A
><B
>A.4.3. </B
CLASS="question"
><P
><A
-NAME="AEN1855"
+NAME="AEN1860"
></A
><B
>A.4.4. </B
You can call bug_email.pl directly from your aliases file, with
an entry like this:
<A
-NAME="AEN1859"
+NAME="AEN1864"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN1862"
+NAME="AEN1867"
></A
><B
>A.4.5. </B
CLASS="question"
><P
><A
-NAME="AEN1867"
+NAME="AEN1872"
></A
><B
>A.4.6. </B
CLASS="question"
><P
><A
-NAME="AEN1874"
+NAME="AEN1879"
></A
><B
>A.4.7. </B
CLASS="question"
><P
><A
-NAME="AEN1882"
+NAME="AEN1887"
></A
><B
>A.5.1. </B
CLASS="question"
><P
><A
-NAME="AEN1887"
+NAME="AEN1892"
></A
><B
>A.5.2. </B
CLASS="question"
><P
><A
-NAME="AEN1895"
+NAME="AEN1900"
></A
><B
>A.5.3. </B
CLASS="question"
><P
><A
-NAME="AEN1903"
+NAME="AEN1908"
></A
><B
>A.5.4. </B
CLASS="question"
><P
><A
-NAME="AEN1911"
+NAME="AEN1916"
></A
><B
>A.5.5. </B
CLASS="question"
><P
><A
-NAME="AEN1920"
+NAME="AEN1925"
></A
><B
>A.6.1. </B
CLASS="question"
><P
><A
-NAME="AEN1925"
+NAME="AEN1930"
></A
><B
>A.6.2. </B
CLASS="question"
><P
><A
-NAME="AEN1930"
+NAME="AEN1935"
></A
><B
>A.6.3. </B
><P
> Microsoft has some advice on this matter, as well:
<A
-NAME="AEN1935"
+NAME="AEN1940"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CLASS="question"
><P
><A
-NAME="AEN1938"
+NAME="AEN1943"
></A
><B
>A.6.4. </B
CLASS="question"
><P
><A
-NAME="AEN1959"
+NAME="AEN1964"
></A
><B
>A.7.1. </B
CLASS="question"
><P
><A
-NAME="AEN1964"
+NAME="AEN1969"
></A
><B
>A.7.2. </B
CLASS="question"
><P
><A
-NAME="AEN1969"
+NAME="AEN1974"
></A
><B
>A.7.3. </B
CLASS="question"
><P
><A
-NAME="AEN1979"
+NAME="AEN1984"
></A
><B
>A.7.4. </B
CLASS="question"
><P
><A
-NAME="AEN1984"
+NAME="AEN1989"
></A
><B
>A.7.5. </B
CLASS="question"
><P
><A
-NAME="AEN1991"
+NAME="AEN1996"
></A
><B
>A.8.1. </B
CLASS="question"
><P
><A
-NAME="AEN1999"
+NAME="AEN2004"
></A
><B
>A.8.2. </B
CLASS="question"
><P
><A
-NAME="AEN2008"
+NAME="AEN2013"
></A
><B
>A.8.3. </B
CLASS="question"
><P
><A
-NAME="AEN2014"
+NAME="AEN2019"
></A
><B
>A.8.4. </B
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
-NAME="AEN2262"
+NAME="AEN2267"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Version 1.1, March 2000</P
><A
-NAME="AEN2172"
+NAME="AEN2177"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><H1
CLASS="glossdiv"
><A
-NAME="AEN2267"
+NAME="AEN2272"
></A
>0-9, high ascii</H1
><DL
"Find" box.</P
></DD
><DT
+><A
+NAME="gloss-bugzilla"
+></A
><B
>Bugzilla</B
></DT
><H2
CLASS="section"
><A
-NAME="AEN336"
+NAME="AEN340"
></A
>3.2.1. Autolinkification</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN365"
+NAME="AEN369"
></A
>3.2.5. Filing Bugs</H2
><P
COLOR="#000000"
><PRE
CLASS="programlisting"
-> Options +ExecCGI
+> Options +ExecCGI
AllowOverride Limit
</PRE
></FONT
></DT
><DT
>4.1.7. <A
-HREF="stepbystep.html#AEN586"
+HREF="stepbystep.html#AEN590"
>Bugzilla</A
></DT
><DT
>4.1.8. <A
-HREF="stepbystep.html#AEN611"
+HREF="stepbystep.html#AEN615"
>Setting Up the MySQL Database</A
></DT
><DT
>4.1.9. <A
-HREF="stepbystep.html#AEN647"
+HREF="stepbystep.html#AEN651"
><TT
CLASS="filename"
>checksetup.pl</TT
></DT
><DT
>4.1.10. <A
-HREF="stepbystep.html#AEN679"
+HREF="stepbystep.html#AEN683"
>Securing MySQL</A
></DT
><DT
>4.1.11. <A
-HREF="stepbystep.html#AEN745"
+HREF="stepbystep.html#AEN749"
>Configuring Bugzilla</A
></DT
></DL
><DL
><DT
>4.2.1. <A
-HREF="extraconfig.html#AEN751"
+HREF="extraconfig.html#AEN755"
>Dependency Charts</A
></DT
><DT
>4.2.2. <A
-HREF="extraconfig.html#AEN766"
+HREF="extraconfig.html#AEN770"
>Bug Graphs</A
></DT
><DT
>4.2.3. <A
-HREF="extraconfig.html#AEN779"
+HREF="extraconfig.html#AEN783"
>The Whining Cron</A
></DT
><DT
><DL
><DT
>4.5.1. <A
-HREF="troubleshooting.html#AEN1059"
+HREF="troubleshooting.html#AEN1063"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.5.2. <A
-HREF="troubleshooting.html#AEN1064"
+HREF="troubleshooting.html#AEN1068"
>DBD::Sponge::db prepare failed</A
></DT
><DT
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</P
+ you want to have the bug be closed automatically, you'll have to modify
+ the <TT
+CLASS="filename"
+>contrib/bugzilla_email_append.pl</TT
+> script.
+ </P
><P
>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
><H4
CLASS="section"
><A
-NAME="AEN926"
+NAME="AEN930"
></A
>4.3.1.3.3. System Calls</H4
><P
><H3
CLASS="section"
><A
-NAME="AEN552"
+NAME="AEN556"
></A
>4.1.5.1. DBI</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN555"
+NAME="AEN559"
></A
>4.1.5.2. Data::Dumper</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN558"
+NAME="AEN562"
></A
>4.1.5.3. MySQL-related modules</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN563"
+NAME="AEN567"
></A
>4.1.5.4. TimeDate modules</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN566"
+NAME="AEN570"
></A
>4.1.5.5. GD (optional)</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN573"
+NAME="AEN577"
></A
>4.1.5.6. Chart::Base (optional)</H3
><P
><H3
CLASS="section"
><A
-NAME="AEN576"
+NAME="AEN580"
></A
>4.1.5.7. Template Toolkit</H3
><P
><H2
CLASS="section"
><A
-NAME="AEN586"
+NAME="AEN590"
></A
>4.1.7. Bugzilla</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN611"
+NAME="AEN615"
></A
>4.1.8. Setting Up the MySQL Database</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN647"
+NAME="AEN651"
></A
>4.1.9. <TT
CLASS="filename"
><H2
CLASS="section"
><A
-NAME="AEN679"
+NAME="AEN683"
></A
>4.1.10. Securing MySQL</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN745"
+NAME="AEN749"
></A
>4.1.11. Configuring Bugzilla</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN1059"
+NAME="AEN1063"
></A
>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
><H2
CLASS="section"
><A
-NAME="AEN1064"
+NAME="AEN1068"
></A
>4.5.2. DBD::Sponge::db prepare failed</H2
><P
><DL
><DT
>3.2.1. <A
-HREF="hintsandtips.html#AEN336"
+HREF="hintsandtips.html#AEN340"
>Autolinkification</A
></DT
><DT
></DT
><DT
>3.2.5. <A
-HREF="hintsandtips.html#AEN365"
+HREF="hintsandtips.html#AEN369"
>Filing Bugs</A
></DT
></DL
</entry>
</row>
+ <row>
+ <entry>Term found in the glossary</entry>
+
+ <entry>
+ <glossterm linkend="gloss-bugzilla">Bugzilla</glossterm>
+ </entry>
+ </row>
+
<row>
<entry>Code Example</entry>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gloss-bugzilla">
<glossterm>Bugzilla</glossterm>
<glossdef>
(either the Bugzilla directory or one of its parents).
</para>
<programlisting>
-Options +ExecCGI
+Options +ExecCGI
AllowOverride Limit
</programlisting>
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</para>
+ you want to have the bug be closed automatically, you'll have to modify
+ the <filename>contrib/bugzilla_email_append.pl</filename> script.
+ </para>
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
Prompt of user command under tcsh shell tcsh$
Environment Variables VARIABLE
Emphasized word word
+ Term found in the glossary Bugzilla
Code Example
<para>
Beginning and end of paragraph
Follow the instructions in this Guide for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to your
Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
- have CVS check-in comments append to your Bugzilla bug. If you have
- your check-in script include an @resolution field, you can even change
- the Bugzilla bug state.
+ have CVS check-in comments append to your Bugzilla bug. If you want to
+ have the bug be closed automatically, you'll have to modify the
+ contrib/bugzilla_email_append.pl script.
There is also a CVSZilla project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to email.
</entry>
</row>
+ <row>
+ <entry>Term found in the glossary</entry>
+
+ <entry>
+ <glossterm linkend="gloss-bugzilla">Bugzilla</glossterm>
+ </entry>
+ </row>
+
<row>
<entry>Code Example</entry>
</glossdef>
</glossentry>
- <glossentry>
+ <glossentry id="gloss-bugzilla">
<glossterm>Bugzilla</glossterm>
<glossdef>
(either the Bugzilla directory or one of its parents).
</para>
<programlisting>
-Options +ExecCGI
+Options +ExecCGI
AllowOverride Limit
</programlisting>
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
- you have your check-in script include an @resolution field, you can even
- change the Bugzilla bug state.</para>
+ you want to have the bug be closed automatically, you'll have to modify
+ the <filename>contrib/bugzilla_email_append.pl</filename> script.
+ </para>
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
projects / thirdparty / bugzilla.git / commitdiff
