<center>or "It's not a bug. It's a feature."</center>
<hr WIDTH="100%">
-<p><b><i>Q</i></b>: <i>Where can I find information about bugzilla?</i>
-<br><b><i>A</i></b>: You can stay up-to-date with the latest bugzilla information
+<p><b><i>Q:</i></b> <i>Where can I find information about bugzilla?</i>
+<br><b><i>A:</i></b> You can stay up-to-date with the latest bugzilla information
at <a href="http://www.mozilla.org/projects/bugzilla/">http://www.mozilla.org/projects/bugzilla/</a>.
-<p><b><i>Q</i></b>: <i>What license is Bugzilla distributed under?</i>
-<br><b><i>A</i></b>: Bugzilla is under the Mozilla Public License. See
+<p><b><i>Q:</i></b> <i>What license is Bugzilla distributed under?</i>
+<br><b><i>A:</i></b> Bugzilla is under the Mozilla Public License. See
details at <a href="http://www.mozilla.org/MPL/">http://www.mozilla.org/MPL/</a>
<p><b><i>Q:</i></b> <i>How do I get commercial support for Bugzilla?</i>
-<br><b><i>A</i></b>: As far as I know, there are not yet any companies
+<br><b><i>A:</i></b> As far as I know, there are not yet any companies
that offer commercial Bugzilla support. However, I've heard there are consulting
companies that will install and maintain a Bugzilla installation for charge,
and would accept responsibility for its upkeep. I'm not sure which large
consulting firms do this yet -- I'm open to more contributions in this
area.
-<p><b><i>Q</i></b>: <i>What major companies or projects are currently using
+<p><b><i>Q:</i></b> <i>What major companies or projects are currently using
Bugzilla for bug-tracking?</i>
-<br><b><i>A</i></b>: This is by no means a complete list, and is assembled
+<br><b><i>A:</i></b> This is by no means a complete list, and is assembled
from contributions and about 10 minutes of searching on AltaVista. Contributions
welcome:
<ul>
<li>
<a href="http://www.eazel.com/">The Eazel Project</a></li>
</ul>
-<b><i>Q</i></b>: <i>Who maintains Bugzilla?</i>
-<br><b><i>A
</i></b>: <a href="mailto:tara@tequilarista.org">Tara Hernandez</a>
+<b><i>Q:</i></b> <i>Who maintains Bugzilla?</i>
+<br><b><i>A
:</i></b> <a href="mailto:tara@tequilarista.org">Tara Hernandez</a>
is the current maintainer of Bugzilla. It was originally written and maintained
by <a href="mailto:terry@mozilla.org">Terry Weissman</a>, but he is no
longer heavily involved (Tara adds, "These days, <a href="mailto:terry@mozilla.org">Terry</a>
They bear primary responsibility for keeping the current bugzilla.mozilla.org
site up-to-date, and have a vital interest in ensuring Bugzilla moves forward
(and doesn't break!)
-<p><b><i>Q</i></b>: <i>Why does Bugzilla use .png files instead of .gifs
+<p><b><i>Q:</i></b> <i>Why does Bugzilla use .png files instead of .gifs
for graphs?</i>
-<br><b><i>A
</i></b>: Patent restrictions (see <a href="http://www.gnu.org/philosophy/gif.html">http://www.gnu.org/philosophy/gif.html</a>
+<br><b><i>A
:</i></b> Patent restrictions (see <a href="http://www.gnu.org/philosophy/gif.html">http://www.gnu.org/philosophy/gif.html</a>
for details). If you're using a recent version of the GD library and a
recent version of Bugzilla, this is no longer a FAQ.
-<p><b><i>Q</i></b>: <i>How does Bugzilla stack up against other bug-tracking
+<p><b><i>Q:</i></b> <i>How does Bugzilla stack up against other bug-tracking
databases?</i>
-<br><b><i>A</i></b>: As far as I know, there have been no feature-by-feature
+<br><b><i>A:</i></b> As far as I know, there have been no feature-by-feature
comparisons to other bug-tracking systems. However, here are some
primary reasons people cite for moving to Bugzilla:
<ol>
Price. However, don't let price be the selling point of Bugzilla
-- it survives on its own merits.</li>
</ol>
-<b><i>Q</i></b>: <i>How do I change my username in Bugzilla?</i>
-<br><b><i>A</i></b>: If you are the administrator, open up editusers.cgi
+<b><i>Q:</i></b> <i>How do I change my username in Bugzilla?</i>
+<br><b><i>A:</i></b> If you are the administrator, open up editusers.cgi
and change the login name. Simple!
-<p><i><b>Q</b>: Why doesn't Bugzilla offer this or that feature or compatability
+<p><i><b>Q:</b> Why doesn't Bugzilla offer this or that feature or compatability
with <insert cool tracking software here>?</i>
-<br><b><i>A</i></b>: Terry writes,
+<br><b><i>A:</i></b> Terry writes,
<blockquote>I wrote Bugzilla primarily for mozilla.org's use. It is a secondary
concern (but one still important to me) that it be of use to other folks,
too. So, rather than spend a lot of time making everything thoroughly portable
It is widely considered the most complete and popular open-source bug database
in existence. <a href="http://www.mozilla.org/bugs/source.html">Download
a copy today!</a>
-<p><b><i>Q</i></b>: <i>Why MySQL? I'm interested in seeing this run on
+<p><b><i>Q:</i></b> <i>Why MySQL? I'm interested in seeing this run on
(insert "real" RDBMS name here)...</i>
-<br><b><i>A</i></b>: Terry answers,
+<br><b><i>A:</i></b> Terry answers,
<blockquote>You're not the only one. But *I* am not very interested. I'm
not 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
changes real soon that will bring some more portability to Bugzilla.
However, they are in severe need of help. Please contact <a href="mailto:dkl@redhat.com">Dave
Lawrence</a> if you are interested in helping this effort.
-<p><b><i>Q</i></b>: <i>Why do the scripts say "/usr/bonsaitools/bin/perl"
+<p><b><i>Q:</i></b> <i>Why do the scripts say "/usr/bonsaitools/bin/perl"
instead of "/usr/bin/perl" or something else?</i>
-<br><b><i>A</i></b>: Mozilla.org uses /usr/bonsaitools/bin/perl. The prime
+<br><b><i>A:</i></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.
Terry says:
<a NAME="RHBZ"></a>Red Hat Bugzilla</h3>
</blockquote>
-<p><br><b><i>Q</i></b>: <i>What about Red Hat Bugzilla?</i>
-<br><b><i>A
</i></b>: <a href="http://www.redhat.com/">Red Hat</a> has a
+<p><br><b><i>Q:</i></b> <i>What about Red Hat Bugzilla?</i>
+<br><b><i>A
:</i></b> <a href="http://www.redhat.com/">Red Hat</a> has a
(arguably more user-friendly/customizable/scalable buzzword here) version
of Bugzilla available. Check it out at <a href="http://bugzilla.redhat.com/">http://bugzilla.redhat.com
</a>and
Vance</a>. Maintenance of Fenris has since been handed off to <a href="mailto:raistlin@lokigames.com">Raphael
Barrerro</a> <raistlin@lokigames.com>.
<p><i><b>Q: </b>What about Loki Bugzilla?</i>
-<br><b><i>A</i></b>: Loki Games has a customized version of Bugzilla
+<br><b><i>A:</i></b> Loki Games has a customized version of Bugzilla
available at <a href="http://fenris.lokigames.com/">http://fenris.lokigames.com</a>.
From that page,
<blockquote>You may have noticed that Fenris is a fork from Bugzilla--
and reboot."</center>
<hr WIDTH="100%">
-<br><b><i>Q</b>: How do I download and install Bugzilla?</i>
-<br><b><i>A</i></b>: The README included with Bugzilla documents the installation
+<br><b><i>Q:</b> How do I download and install Bugzilla?</i>
+<br><b><i>A:</i></b> The README included with Bugzilla documents the installation
procedures much more thoroughly than I can do here. You can always find
a current copy of the README in the distribution tarballs available at
<a href="http://www.mozilla.org/projects/bugzilla/">http://www.mozilla.org/projects/bugzilla/
</a>.
This will eventually be documented in "The Bugzilla Installation Guide".
-<p><b><i>Q</i></b>: <i>How do I install Bugzilla on Windows NT?</i>
-<br><b><i>A</i></b>: That question is complex enough it deserves
+<p><b><i>Q:</i></b> <i>How do I install Bugzilla on Windows NT?</i>
+<br><b><i>A:</i></b> That question is complex enough it deserves
<a href="#BZNT">its
own section</a>, below.
<p><i><b>Q: </b>Is there an easy way to change the Bugzilla cookie
name?</i>
-<br><b><i>A</i></b>: At present, no.
+<br><b><i>A:</i></b> At present, no.
+
+<p><i><b>Q: </b>I want to set up a test installation to try out new
+changes. How do I copy over data from my real database?</i>
+<br><b><i>A:</i></b>
+
+Copying the mysql files directly from one machine to another is likely
+to confuse mysql. Its recommended to create a dump of the database
+and to populate the new database from the dump.
+<OL>
+<LI>
+Create a dump of the original database.
+<BLOCKQUOTE><CODE>
+%mysqldump bugs > ~/bugs.dump
+</CODE></BLOCKQUOTE>
+
+<LI>
+Copy the dump file to the new machine.
+
+<LI>
+Blow away the contents of the current bugzilla database
+on the test machine.
+<BLOCKQUOTE><CODE>
+%mysql<BR>
+mysql> drop database bugs;<BR>
+mysql> create database bugs;<BR>
+</CODE></BLOCKQUOTE>
+
+<LI>
+Import the bug database
+<BLOCKQUOTE><CODE>
+%mysql bugs < bugs.dump
+</CODE></BLOCKQUOTE>
+
+</OL>
+
+
<p>
<hr WIDTH="100%">
<center>
<h3>
<a NAME="BZSECURITY"></a>SECURITY</h3>
</blockquote>
-<b><i>Q</i></b>: <i>How do I completely disable MySQL security if
+<b><i>Q:</i></b> <i>How do I completely disable MySQL security if
it's giving me problems (I've followed the instructions in the README!)?</i>
<br><b><i>A:</i></b> Run mysql like this: "mysqld --skip-grant-tables".
Please remember this makes mysql as secure as taping a $100 to the floor
put Bugzilla up for general consumption, you REALLY need to become familiar
with <a href="http://www.mysql.com/Manual_chapter/manual_Privilege_system.html#Privilege_system">MySQL
security</a>.
-<p><b><i>Q</i></b>: <i>Are there any security problems with Bugzilla?</i>
-<br><b><i>A</i></b>: Prior to 2.10, yes. For 2.10 and later, probably,
+<p><b><i>Q:</i></b> <i>Are there any security problems with Bugzilla?</i>
+<br><b><i>A:</i></b> Prior to 2.10, yes. For 2.10 and later, probably,
but we haven't discovered them yet.. You should upgrade to 2.10 and use
the following instructions from Chris Yeh's security advisory of 5/10/2000
if you are running a previous version of bugzilla. Chances are good a lot
<br><tt><font size=-1><wait></font></tt>
<br><tt><font size=-1>apachectl start</font></tt>
</pre>
-<p><i><b>Q</b>: I've implemented the security fixes mentioned in Chris
+<p><i><b>Q:</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.</i>
-<br><b><i>A</i></b>: Mozilla.org had a problem getting enough file descriptors
+<br><b><i>A:</i></b> Mozilla.org had a problem getting enough file descriptors
once they stopped running mysql as root; they have many tables in their
database and had "shadowdb" turned on, which doubles the number of tables.
Terry mentioned in IRC: "I added the line "ulimit -n unlimited" to the
<a NAME="BZEMAIL"></a>EMAIL</h3>
</blockquote>
-<p><br><i><b>Q</b>: I have a user who doesn't want to receive any more
+<p><br><i><b>Q:</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?</i>
-<br><b><i>A</i></b>: Easy. Add his/her login name to "bugzilla_home/data/nomail".
+<br><b><i>A:</i></b> Easy. Add his/her login name to "bugzilla_home/data/nomail".
One entry per line. It must match the login name exactly.
<br><b>UPDATE</b>: I'm not sure this works as advertised...
Anyone know of any bugs with this solution?
-<p><i><b>Q</b>: I'm evaluating/testing Bugzilla, and don't want it to send
+<p><i><b>Q:</b> I'm evaluating/testing Bugzilla, and don't want it to send
email to anyone but me. How do I do it?</i>
-<br><b><i>A</i></b>: According to Terry, the *correct* way to do this is,
+<br><b><i>A:</i></b> According to Terry, the *correct* way to do this is,
in editparams.cgi: "Go tweak the param for the mail text, replacing "To:"
with "X-Real-To:", and replacing "Cc:" with "X-Real-CC", and add a "To:
(myemailaddress)". This param file can also be manually edited bugzilla_home/data/params
(but is not recommended).
-<p><b><i>Q</i></b>: <i>I want whineatnews.pl to whine at something more,
+<p><b><i>Q:</i></b> <i>I want whineatnews.pl to whine at something more,
or other than, only new bugs. How do I do it?</i>
-<br><b><i>A</i></b>: Try Klaas Freitag's excellent patch for "whineatassigned"
+<br><b><i>A:</i></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">http://bugzilla.mozilla.org/show_bug.cgi?id=6679</a>.
Realize that as Bugzilla progresses, this patch may go out of date. At
present, I know of no plans to integrate this functionality into the core
Bugzilla distribution.
-<p><b><i>Q</i></b>: <i>I don't like/want to use Procmail to handle email
+<p><b><i>Q:</i></b> <i>I don't like/want to use Procmail to handle email
to bugzilla. What else can I use?</i>
-<br><b><i>A</i></b>: Bugzilla can work with alternate MTA's/filters,
+<br><b><i>A:</i></b> Bugzilla can work with alternate MTA's/filters,
but there is no documentation how.
-<p><b><i>Q</i></b>: <i>How do I set up the email interface to submit/change
+<p><b><i>Q:</i></b> <i>How do I set up the email interface to submit/change
bugs via email?</i>
-<br><b><i>A</i></b>: Download the tarball or CVS and extract it (if applicable).
+<br><b><i>A:</i></b> Download the tarball or CVS and extract it (if applicable).
CD to the (bugzilla_home)/contrib directory, and read the README contained
therein. Seth will be pulling his changes (the bugzilla email submission
stuff) into the main tree sometime as soon as he gets the OK from the powers-that-be.
</ol>
If you've followed the README, you should be good to go; send an email
to "bugs@my.host.name" and watch it work.
-<p><b><i>Q</i></b>: <i>Email takes FOREVER to reach me from bugzilla --
+<p><b><i>Q:</i></b> <i>Email takes FOREVER to reach me from bugzilla --
it's extremely slow. What gives?</i>
-<br><b><i>A</i></b>: If you are using an alternate Mail Transport Agent
+<br><b><i>A:</i></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"
more than a few hundred email messages a day, people may experience nasty
slowdowns when submitting changes to bugs because Sendmail insists on delivering
it *that instant*.
-<p><b><i>Q</i></b>: <i>Email never reaches me from bugzilla changes! What
+<p><b><i>Q:</i></b> <i>Email never reaches me from bugzilla changes! What
gives?</i>
-<br><b><i>A</i></b>: Chances are really good Bugzilla expects "sendmail"
+<br><b><i>A:</i></b> Chances are really good Bugzilla expects "sendmail"
to live somewhere else than you have it installed. Make sure your "sendmail"
lives in, or has a symlink to, "/usr/lib/sendmail".
<br>
<h3>
<a NAME="BZDATABASE"></a>DATABASE</h3>
</blockquote>
-<b><i>Q</i></b>: <i>I've heard Bugzilla can be used with Oracle?</i>
-<br><b><i>A
</i></b>: <a href="http://bugzilla.redhat.com/">Red Hat Bugzilla</a>
+<b><i>Q:</i></b> <i>I've heard Bugzilla can be used with Oracle?</i>
+<br><b><i>A
:</i></b> <a href="http://bugzilla.redhat.com/">Red Hat Bugzilla</a>
works with Oracle. The current mozilla.org version takes some work,
though.
<p><b><i>Q:</i></b> <i>Bugs are missing from queries, but exist in the
database (and I can pull them up by specifying the bug ID). What's wrong?</i>
-<br><b><i>A</i></b>: You've almost certainly enabled the "shadow database",
+<br><b><i>A:</i></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
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><b>Q</b>: <i>I think my database might be corrupted, or contain invalid
+<p><b>Q:</b> <i>I think my database might be corrupted, or contain invalid
entries. What do I do?</i>
<br>A: 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
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><b><i>Q</i></b>: <i>I want to manually edit some entries in my database.
+<p><b><i>Q:</i></b> <i>I want to manually edit some entries in my database.
How?</i>
-<br><b>A</b>: There is no facility in Bugzilla itself to do this. It's
+<br><b>A:</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
to do all my database administration. You have to compile a PHP module
with MySQL support to make it work, but it's very clean and easy to use.
There are other utilities that work, as well, but I am lacking URL's.
-<p><b>Q</b>: <i>MySQL GPL edition doesn't seem to work...</i>
-<br><b><i>A</i></b>: Right! It doesn't! It's too old. Download the latest
+<p><b>Q:</b> <i>MySQL GPL edition doesn't seem to work...</i>
+<br><b><i>A:</i></b> Right! It doesn't! It's too old. Download the latest
tarball or rpm from <a href="http://www.mysql.com/">www.mysql.com</a> if
you want this to work.
-<p><b><i>Q</i></b>: <i>I think I've set up MySQL permissions correctly,
+<p><b><i>Q:</i></b> <i>I think I've set up MySQL permissions correctly,
but bugzilla still can't connect.</i>
-<br><b><i>A</i></b>: Try running MySQL from its binary: "mysqld --skip-grant-tables".
+<br><b><i>A:</i></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><b><i>Q</i></b>: <i>How do I synchronize bug information among multiple
+<p><b><i>Q:</i></b> <i>How do I synchronize bug information among multiple
different Bugzilla databases?</i>
-<br><b><i>A</i></b>: Currently, there is no way to do this. However, a
+<br><b><i>A:</i></b> Currently, there is no way to do this. However, a
discussion about this has raged on and off in the newsgroup -- feel free
to whip something up, put it out there, and see how it's received. We're
at the point where most folks are sick of discussion. If you can create
<br>These are hints straight out of the newsgroup discussions. I
can't offer much more editing or insight, since I don't manage Bugzilla
on any NT boxes.
-<p><b><i>Q</i></b>: <i>What is the easiest way to run Bugzilla on NT?</i>
-<br><b><i>A</i></b>: Remove NT. Install Linux. Slap a label on the box
+<p><b><i>Q:</i></b> <i>What is the easiest way to run Bugzilla on NT?</i>
+<br><b><i>A:</i></b> Remove NT. Install Linux. Slap a label on the box
that says "Windows NT." The boss will never know the difference, except
perhaps wonder why the machine isn't crashing anymore.
-<p><b><i>Q</i></b>: <i>CGI's are failing with a "something.cgi is not a
+<p><b><i>Q:</i></b> <i>CGI's are failing with a "something.cgi is not a
valid Windows NT application" error. Why?</i>
<br><b><i>A:</i></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
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><b><i>Q</i></b>: <i>Can I have some general instructions on how to make
+<p><b><i>Q:</i></b> <i>Can I have some general instructions on how to make
this work?</i>
-<br><b><i>A
</i></b>: Sure. Your Mileage May Vary. Contact <a href="mailto:andrew_lahser@merck.com">Andrew
+<br><b><i>A
:</i></b> Sure. Your Mileage May Vary. Contact <a href="mailto:andrew_lahser@merck.com">Andrew
Lahser </a>for the patches mentioned.
<ol>
<li>
a patch for submission to Bugzilla. If you would like a zip file, let me
know.</li>
</ol>
-<b><i>Q</i></b>: <i>Hmm, couldn't figure it out from the general instructions
+<b><i>Q:</i></b> <i>Hmm, couldn't figure it out from the general instructions
above. How about step-by-step?</i>
-<br><b><i>A</i></b>: Sure! Here ya go!
+<br><b><i>A:</i></b> Sure! Here ya go!
<ol>
<li>
Install IIS 4.0 from the NT Option Pack #4.</li>
not sure about this one, but the read() under NT wasn't counting the EOLs
without the binary read."</li>
</ol>
-<b><i>Q</i></b>: <i>I'm having trouble with the perl modules for NT not
+<b><i>Q:</i></b> <i>I'm having trouble with the perl modules for NT not
being able to talk to to the database...</i>
<br><b><i>A:</i></b> Your modules may be outdated or inaccurate...
<ol>
<center>or "Keyboard: Device used for entering errors into computer"</center>
<hr WIDTH="100%">
-<p><b><i>Q</i></b>: <i>How do I use "new email tech"?</i>
-<br><b><i>A</i></b>: First, go to editparams.cgi and make sure the "newemailtech"
+<p><b><i>Q:</i></b> <i>How do I use "new email tech"?</i>
+<br><b><i>A:</i></b> First, go to editparams.cgi and make sure the "newemailtech"
option is set to "on", then set the "new email tech" option in your personal
user prefs "on".
-<p><b>Q</b>: <i>How do I make "new email tech" the default for my entire
+<p><b>Q:</b> <i>How do I make "new email tech" the default for my entire
site?</i>
-<br><b><i>A</i></b>: You need to alter the user preferences table using
+<br><b><i>A:</i></b> You need to alter the user preferences table using
one of the tools mentioned in the <a href="#BZDATABASE">DATABASE section</a>.
Change the default value for "newemailtech" to "1", and change any user
values you think apply.
-<p><b><i>Q</i></b>: <i>I'm confused by the behavior of the "accept" button
+<p><b><i>Q:</i></b> <i>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?</i>
-<br><b><i>A</i></b>: Right now, how this should behave is the subject of
+<br><b><i>A:</i></b> Right now, how this should behave is the subject of
considerable discussion on the mailing list and in the bug database. There
is a <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=25273">patch
</a>for
I'm working on a real patch for this now that allows you to select which
behavior you want vi editparams.cgi!
<p><b>Q: </b><i>How do I enable voting?</i>
-<br><b><i>A</i></b>: Make sure you're using at least version 2.10.
+<br><b><i>A:</i></b> Make sure you're using at least version 2.10.
It's available via editparams.cgi.
<p><i><b>Q: </b>I can't upload anything into the database via the
"Create Attachment" link. What am I doing wrong?</i>
-<br><b><i>A</i></b>: The most likely cause is a very old browser
+<br><b><i>A:</i></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><i><b>Q:</b> Email submissions to Bugzilla that have attachments
<center>or "These are all 'known bugs'. Whats the frickin' problem?"</center>
<hr WIDTH="100%">
-<p><b><i>Q</i></b>: <i>What bugs currently exist in bugzilla?</i>
-<br><b><i>A</i></b>: The answer is too long (and easily outdated)
+<p><b><i>Q:</i></b> <i>What bugs currently exist in bugzilla?</i>
+<br><b><i>A:</i></b> The answer is too long (and easily outdated)
to keep in this FAQ. However, bugzilla is made for this, so just
try <a href="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Webtools&component=Bugzilla&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_id">this
link</a>.
-<p><b><i>Q</i></b>: <i>Groups don't quite work right yet...</i>
-<br><b><i>A</i></b>: Correct. That's a current area of hacking.
+<p><b><i>Q:</i></b> <i>Groups don't quite work right yet...</i>
+<br><b><i>A:</i></b> Correct. That's a current area of hacking.
You may want to check out Loki's version of Bugzilla for some patches that
support the group functionality you need.
-<p><i><b>Q</b>: Why can't I set "target milestone" to something other
+<p><i><b>Q:</b> Why can't I set "target milestone" to something other
than a number?</i>
-<br><b><i>A</i></b>: The concept of a target milestone was initially
+<br><b><i>A:</i></b> The concept of a target milestone was initially
that each group would have their own definition for what each target milestone
number is, but share a common pool of numbers. Unfortunately, this
concept has proven confusing for new and experienced users alike.
my hard drive?"</center>
<hr WIDTH="100%">
-<p><b><i>Q</i></b>: <i>What's the best way to submit patches? What
+<p><b><i>Q:</i></b> <i>What's the best way to submit patches? What
guidelines should I follow.</i>
<br><b><i>A:</i></b> Tara summed this FAQ up nicely:
<blockquote>"Well, I guess I'd better answer this, as I'm the one who's
etc. That way I think all bases are covered. Speaking for myself
in trying to be a good module owner, getting a new bug makes sure I
<br>don't lose track of your patch, so this makes it easier for me."</blockquote>
-<i><b>Q</b>:</i> <i>What does the above mean for me when I want to
+<i><b>Q:</b></i> <i>What does the above mean for me when I want to
submit a bug?</i>
-<br><b><i>A</i></b>: Follow this procedure:
+<br><b><i>A:</i></b> Follow this procedure:
<ol>
<li>
<a href="http://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools">Enter
<h3>
<a NAME="BZAPI"></a>API</h3>
</blockquote>
-<b><i>Q</i></b>: <i>I want to add a new form or module to Bugzilla.
+<b><i>Q:</i></b> <i>I want to add a new form or module to Bugzilla.
Where can I find API documention?</i>
<br><b><i>A:</i></b> Right now, there really is none. I plan
on writing copious documentation for what each file and module does, as
well how to program new .cgi's to use the functionality and present alternate
interfaces. Right now, use the source.
-<p><b><i>Q</i></b>: What are the most-needed features?
-<br><b><i>A</i></b>: Check out the Bugzilla Development Roadmap at
+<p><b><i>Q:</i></b> What are the most-needed features?
+<br><b><i>A:</i></b> Check out the Bugzilla Development Roadmap at
<a href="http://www.mozilla.org/projects/bugzilla/roadmap.html">http://www.mozilla.org/projects/bugzilla/roadmap.html</a>
<br>
<p>
to another format (particulary PDF). One must be able to maintain
the FAQ as a single, printable document; if you know of a good system that
will fit the bill, let me know.
-<p><b><i>Q</i></b>: <i>Who are you?</i>
-<br><b><i>A</i></b>: I'm Matthew P. Barnson, manager of Systems Administration
+<p><b><i>Q:</i></b> <i>Who are you?</i>
+<br><b><i>A:</i></b> I'm Matthew P. Barnson, manager of Systems Administration
for <a href="http://www.excitestores.com">Excite Business Applications
</a>and
part-time Bugzilla hacker.
-<p><b><i>Q</i></b>: <i>Why are you doing this?</i>
-<br><b><i>A</i></b>: I have nothing better to do with my time!
+<p><b><i>Q:</i></b> <i>Why are you doing this?</i>
+<br><b><i>A:</i></b> I have nothing better to do with my time!
<br> Seriously, I run a fairly large private Bugzilla database.
I felt the need for some documentation to help other SysAdmins run this
thing. There was nothing out there like it, so I decided to improve
rewrite than they are more hacks to support more features. Since
I'm not qualified to write more than trivial hacks for Bugzilla if I were
to code, I figured doing some documentation would be A Good Thing.
-<p><b><i>Q
</i></b>: <i>How are you affiliated with <a href="http://www.mozilla.org">Mozilla.org</a>?</i>
+<p><b><i>Q
:</i></b> <i>How are you affiliated with <a href="http://www.mozilla.org">Mozilla.org</a>?</i>
<br><b><i>A: </i></b> I'm not, except I've been appointed the "Docs
Knight" for Bugzilla, and contribute documentation to other webtools.
-<p><b><i>Q</i></b>: <i>Where do those lame quotes in each section
+<p><b><i>Q:</i></b> <i>Where do those lame quotes in each section
heading come from?</i>
-<br><b><i>A
</i></b>: Check out <a href="http://bugzilla.mozilla.org/data/comments">http://bugzilla.mozilla.org/data/comments</a>.
+<br><b><i>A
:</i></b> Check out <a href="http://bugzilla.mozilla.org/data/comments">http://bugzilla.mozilla.org/data/comments</a>.
These are random quips added by people who use bugzilla. I find them
endlessly entertaining.
<p><i><b>Q: </b> What other documentation is available?</i>
projects / thirdparty / bugzilla.git / commitdiff
