Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!sequent!ccssrv!ccsrd3!chris
From: chris@ccsrd3.UUCP (Chris Andersen ("The Dangerous Guy"))
Newsgroups: comp.software-eng
Subject: Problem Tracking Systems
Message-ID: <810@ccsrd3.UUCP>
Date: 9 Nov 89 23:20:23 GMT
Reply-To: chris@ccssrv.UUCP (Chris Andersen ("The Dangerous Guy"))
Organization: The Danger Patrol
Lines: 19

We are currently looking into automating our Problem Tracking System and
could use any venerable wisdom that might be out there.  I know from past
experience that this can quickly blow up into a MAJOR project, even for
a small company, and I would like to hear what other peoples experiences
with this have been.

What is the best way to automate the process of bug/problem tracking
in a software project?  Across several projects?  What, in your experience,
are the benefits and pitfalls of this kind of automation?  Is there any
public domain software for doing this?  Any commercially available software?
If there is, which ones work the best?

Any suggestions would be mucho appreciated.

Thanks.
-- 
Chris Andersen (..!{sun,tektronix}!sequent!ccssrv!chris)
Home: (503) 620-4176	Work: (503) 641-8128
"Join the Danger Patrol!"