RE: Bug tracking systems as information repositories

Subject: RE: Bug tracking systems as information repositories
From: Darren Barefoot <dbarefoot -at- mpsbc -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 14 Sep 1999 16:28:03 -0700

Good afternoon,

We use the very effective and customizable Pivotal Relationships
(www.pivotal.com). This allows any documentation defects or requests to
reflect the process that software bugs undergo. It's got an extremely
flexible database management system, and I can always find what I'm looking
for via search fields or customized queries with ease. Once we got everyone
on board, it has definitely sped up the information gathering and
redistributing process. For example, it's much easier to generate release
notes for releases of our products--we just query the database for the
recently fixed issues and voila.

It definitely requires somebody with some database savvy, though, to
administrate. Hope that helps. Thanks. DB.

-----Original Message-----
From: jane [mailto:judydh -at- total -dot- net]
Sent: Tuesday, September 14, 1999 12:25 PM
To: TECHWR-L
Subject: Bug tracking systems as information repositories


(snip)

Do TWs use the bug tracking system as a source for troubleshooting or other
background knowledge? What kinds of software/databases do you use? Do you
think it saves the company time and money to use it as an information
repository? What is the simplest method and architecture to use a database
for this? Have you needed the services of a DBAdmin before?

TIA,

Jane




Previous by Author: [techwr-l] FW: Rejected posting to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Next by Author: How do users use help?
Previous by Thread: Bug tracking systems as information repositories
Next by Thread: FrontPage 98 styles misery


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads