Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site tikal.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tikal!mikki
From: mikki@tikal.UUCP (Mikki Leach)
Newsgroups: net.database,net.misc,net.unix,net.wanted
Subject: Trouble Reporting Systems
Message-ID: <297@tikal.UUCP>
Date: Tue, 17-Dec-85 12:19:53 EST
Article-I.D.: tikal.297
Posted: Tue Dec 17 12:19:53 1985
Date-Received: Thu, 19-Dec-85 04:33:25 EST
Reply-To: mikki@tikal.UUCP (Mikki Leach)
Followup-To: net.database
Organization: Teltone Corp., Kirkland, WA
Lines: 31
Xref: watmath net.database:154 net.misc:9007 net.unix:6661 net.wanted:7786


I am looking for information on various "trouble reporting" systems.  
By "trouble reporting" I am refering to a system by which problems found
with the project--software, hardware, or documentation--can be tracked. 
Anybody should be able to enter a problem such as the software engineer,
test engineer, customer, or internal users. I am working on a project at 
Teltone Corp, that currently has a manual trouble reporting system. We are 
looking to convert this manual process to a database system with interfaces. 
One thought is to include in this system the ability to not only track 
troubles but also new work items, changes requests to change software on a 
current revision, and the tracking of both unit and integration testing.

What I am interested in finding out is how other research and development
companies handle this kind of problem, what software is used (software
developed in house or purchased), and how does it work.

We would like this system to go onto a Pyramid machine running UN*X, 4.2 bsd
and System V.

Any response would be appreciated.

Thanks
Mikki Leach

Net address:   ...!uw-beaver!tikal!mikki
               ...!fluke!tikal!mikki
Company address: Teltone Corp.
                 Mikki Leach
                 PO Box 657
                 Kirkland, WA  98033
Company phone:  (206)827-9626 ext. 445