Software Bug Databases

[Ben <baj357 -at- gmail -dot- com>]

I'm hoping to gain some insight to hopefully my common issue as a tech writer for software. At my company, the software bug database is also used to submit related doc bugs. The submitted information about the bug is mainly related to the software and, as a result, requires quite a bit of investigation to find the doc impact--if any. The bug basically states doc impact, doc deliverable, and related product. Currently, writers read the software bug and investigate the suggested doc impact. A submitter can suggest a doc impact even if they are just guessing at it. And it's up to the writers to figure it out.
   
  Have any of you found a more efficient process? So far, suggested doc-specific fields in the bug submission form have fallen on deaf ears. And I don't expect submitters (developers, engineers, etc.) to elaborate on the doc impact, at least not within the bug database. Am I asking for too much? Thanks!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.