diff options
Diffstat (limited to 'docs/html/why-tracking.html')
| -rw-r--r-- | docs/html/why-tracking.html | 24 |
1 files changed, 8 insertions, 16 deletions
diff --git a/docs/html/why-tracking.html b/docs/html/why-tracking.html index bb22e0020..e56dca9f3 100644 --- a/docs/html/why-tracking.html +++ b/docs/html/why-tracking.html @@ -79,23 +79,15 @@ NAME="why-tracking" ></A >2.2. Why use a bug-tracking system?</H1 ><P ->For many years, defect-tracking software was principally - the domain of large software development houses. Most smaller shops - simply relied on - shared lists and email to monitor the status of defects. This procedure - was error-prone and tended to cause those bugs judged least significant by - developers to be dropped or ignored.</P +>Those who do not use a bug-tracking system tend to rely on + shared lists, email, spreadsheets and/or Post-It notes to monitor the + status of defects. This procedure + is usually error-prone and tends to cause those bugs judged least + significant by developers to be dropped or ignored.</P ><P ->Integrated - defect-tracking systems reduce downtime, increase productivity, and raise - customer satisfaction with their systems. Along with full disclosure, an - open bug-tracker allows you to keep in touch with your 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 method for accounting for unusual system or software - issues.</P +>Integrated defect-tracking systems make sure that nothing gets + swept under the carpet; they provide a method of creating, storing, + arranging and processing defect reports and enhancement requests.</P ></DIV ><DIV CLASS="NAVFOOTER" |