diff options
| author | gerv%gerv.net <> | 2002-07-28 07:00:17 +0200 |
|---|---|---|
| committer | gerv%gerv.net <> | 2002-07-28 07:00:17 +0200 |
| commit | d8caf6045d10344c431918128e3803ca497565f3 (patch) | |
| tree | 1b2fbc50e442b6413a4ef0949e8ff7eed1df1361 /docs/html/why.html | |
| parent | a9bb18746686c1bf5497e27f7ac2e12d0e3fc31a (diff) | |
| download | bugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.gz bugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.xz | |
Merging new docs from 2.16 branch.
Diffstat (limited to 'docs/html/why.html')
| -rw-r--r-- | docs/html/why.html | 147 |
1 files changed, 66 insertions, 81 deletions
diff --git a/docs/html/why.html b/docs/html/why.html index 403ad58c6..1baa4042e 100644 --- a/docs/html/why.html +++ b/docs/html/why.html @@ -10,14 +10,14 @@ REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html"><LINK REL="UP" -TITLE="Using Bugzilla" -HREF="using.html"><LINK +TITLE="Introduction" +HREF="introduction.html"><LINK REL="PREVIOUS" TITLE="What is Bugzilla?" HREF="whatis.html"><LINK REL="NEXT" -TITLE="How do I use Bugzilla?" -HREF="how.html"></HEAD +TITLE="Using Bugzilla" +HREF="using.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -53,13 +53,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 2. Using Bugzilla</TD +>Chapter 2. Introduction</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="how.html" +HREF="using.html" ACCESSKEY="N" >Next</A ></TD @@ -74,86 +74,71 @@ CLASS="section" CLASS="section" ><A NAME="why">2.2. Why Should We Use Bugzilla?</H1 -><TABLE -BORDER="0" -WIDTH="100%" -CELLSPACING="0" -CELLPADDING="0" -CLASS="EPIGRAPH" -><TR -><TD -WIDTH="45%" -> </TD -><TD -WIDTH="45%" -ALIGN="LEFT" -VALIGN="TOP" -><I ><P -><I ->No, Who's on first...</I -></P -></I -></TD -></TR -></TABLE -><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 +>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 ><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 +>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 ><P -> But why should <EM +>But why should + <EM >you</EM -> use Bugzilla? - </P +> + + use Bugzilla?</P ><P -> Bugzilla is very adaptable to various situations. Known uses - currently include IT support queues, Systems Administration - deployment management, chip design and development problem - tracking (both pre-and-post fabrication), and software and - hardware bug tracking for luminaries such as Redhat, Loki - software, Linux-Mandrake, and VA Systems. Combined with systems - such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a - powerful, easy-to-use solution to configuration management and - replication problems - </P +>Bugzilla is very adaptable to various situations. Known uses + currently include IT support queues, Systems Administration deployment + management, chip design and development problem tracking (both + pre-and-post fabrication), and software and hardware bug tracking for + luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems. + Combined with systems such as + <A +HREF="http://www.cvshome.org" +TARGET="_top" +>CVS</A +>, + <A +HREF="http://www.mozilla.org/bonsai.html" +TARGET="_top" +>Bonsai</A +>, or + <A +HREF="http://www.perforce.com" +TARGET="_top" +>Perforce SCM</A +>, 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 +>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 by using Bugzilla's e-mail - integration features be able to follow the discussion trail that - led to critical decisions. - </P +> + 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 +>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" @@ -189,7 +174,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="how.html" +HREF="using.html" ACCESSKEY="N" >Next</A ></TD @@ -205,7 +190,7 @@ WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="using.html" +HREF="introduction.html" ACCESSKEY="U" >Up</A ></TD @@ -213,7 +198,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->How do I use Bugzilla?</TD +>Using Bugzilla</TD ></TR ></TABLE ></DIV |