Software Bug Databases

[Ben]

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!