summaryrefslogtreecommitdiffstats
path: root/docs/html/why.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2004-01-16 07:34:12 +0100
committergerv%gerv.net <>2004-01-16 07:34:12 +0100
commit4bbb07e8048ef859cfc29c6b9d221840f2c6aed1 (patch)
tree69ebbdef36708c17345d3220223190a3ce0b682e /docs/html/why.html
parent85e651ef9836d43613c3bb55f7c1c3ff150f76d0 (diff)
downloadbugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.gz
bugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.xz
Phase 1 of a big documentation update before 2.17.6.
Diffstat (limited to 'docs/html/why.html')
-rw-r--r--docs/html/why.html113
1 files changed, 66 insertions, 47 deletions
diff --git a/docs/html/why.html b/docs/html/why.html
index d1e3b813e..6c46ddf44 100644
--- a/docs/html/why.html
+++ b/docs/html/why.html
@@ -1,19 +1,21 @@
<HTML
><HEAD
><TITLE
->Why Should We Use Bugzilla?</TITLE
+>Why use Bugzilla?</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5 Development Release"
+TITLE="The Bugzilla Guide - 2.17.5
+ Development Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="PREVIOUS"
-TITLE="What is Bugzilla?"
-HREF="whatis.html"><LINK
+TITLE="Why use a bug-tracking system?"
+HREF="why.html"><LINK
REL="NEXT"
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
@@ -36,7 +38,8 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
->The Bugzilla Guide - 2.17.5 Development Release</TH
+>The Bugzilla Guide - 2.17.5
+ Development Release</TH
></TR
><TR
><TD
@@ -44,7 +47,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="whatis.html"
+HREF="why.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -74,32 +77,64 @@ CLASS="section"
><A
NAME="why"
></A
->2.2. Why Should We Use Bugzilla?</H1
+>2.3. Why use Bugzilla?</H1
><P
->For many years, defect-tracking software has remained principally
- the domain of large software development houses. Even then, most shops
- never bothered with bug-tracking software, and instead simply relied on
- shared lists and email to monitor the status of defects. This procedure
- is error-prone and tends to cause those bugs judged least significant by
- developers to be dropped or ignored.</P
+>Bugzilla boasts many advanced features. These include:
+ <P
+></P
+><UL
+><LI
><P
->These days, many companies are finding that integrated
- defect-tracking systems reduce downtime, increase productivity, and raise
- customer satisfaction with their systems. Along with full disclosure, an
- open bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout the
- data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support
- accountability, telephone support knowledge bases, and a common,
- well-understood system for accounting for unusual system or software
- issues.</P
+>Powerful searching</P
+></LI
+><LI
><P
->But why should
- <EM
->you</EM
+>User-configurable email notifications of bug changes</P
+></LI
+><LI
+><P
+>Full change history</P
+></LI
+><LI
+><P
+>Inter-bug dependency tracking and graphing</P
+></LI
+><LI
+><P
+>Excellent attachment management</P
+></LI
+><LI
+><P
+>Integrated, product-based, granular security schema</P
+></LI
+><LI
+><P
+>Fully security-audited, and runs under Perl's taint mode</P
+></LI
+><LI
+><P
+>A robust, stable RDBMS back-end</P
+></LI
+><LI
+><P
+>Web, XML, email and console interfaces</P
+></LI
+><LI
+><P
+>Completely customisable and/or localisable web user
+ interface</P
+></LI
+><LI
+><P
+>Extensive configurability</P
+></LI
+><LI
+><P
+>Smooth upgrade pathway between versions</P
+></LI
+></UL
>
-
- use Bugzilla?</P
+ </P
><P
>Bugzilla is very adaptable to various situations. Known uses
currently include IT support queues, Systems Administration deployment
@@ -124,22 +159,6 @@ TARGET="_top"
>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</P
-><P
->Bugzilla can dramatically increase the productivity and
- accountability of individual employees by providing a documented workflow
- and positive feedback for good performance. How many times do you wake up
- in the morning, remembering that you were supposed to do
- <EM
->something</EM
->
- today, but you just can't quite remember? Put it in Bugzilla, and you
- have a record of it from which you can extrapolate milestones, predict
- product versions for integration, and follow the discussion trail
- that led to critical decisions.</P
-><P
->Ultimately, Bugzilla puts the power in your hands to improve your
- value to your employer or business while providing a usable framework for
- your natural attention to detail and knowledge store to flourish.</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -157,7 +176,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="whatis.html"
+HREF="why.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -185,7 +204,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->What is Bugzilla?</TD
+>Why use a bug-tracking system?</TD
><TD
WIDTH="34%"
ALIGN="center"