summaryrefslogtreecommitdiffstats
path: root/docs/html/why.html
blob: e6a254cee3142158f60a11cc4ace438f9d51b10b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
<HTML
><HEAD
><TITLE
>Why Should We Use Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 2.17.4 Development Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="PREVIOUS"
TITLE="What is Bugzilla?"
HREF="whatis.html"><LINK
REL="NEXT"
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide - 2.17.4 Development Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="whatis.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="using.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="why"
></A
>2.2. Why Should We 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
><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
>you</EM
>

    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, 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
>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"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="whatis.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>What is Bugzilla?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>