Description of problem:

for each package you are likely to want to file various logfiles and such 
to be submitted to en-clue the debugging crew.

when filing a new bug you browse the list of packages and select the package that you are filing the bug against.

once you select the package from the list the 'component description' list box to the right gives a brief description of the package.  

however, this 'component description' list box could also show 
a LIST of HYPERLINKS of the types of log files and such 
that you might want to submit along with the bug report.

each of these hyperlinks in the list of suggested log files 
in the 'component description' list box 
would point to an appropriate help file that describes 
what use the log file has, why we want the file submitted, 
how to get the file, and how to prepare it before submitting.

each package would need to supply a list of files 
that they would like to be submitted when someone 
files a bug report against the package.

though i can never seem to find it when i need it, 
often much of the information seems to exists in various 
wiki pages so hopefully wouldnt be too much work.  

adding links to the information would help to improve the quality/speed of bug reports by reminding the coffee deprived reporter what to file and where each lives and how to preprocess the file before submitting.

Version-Release number of selected component (if applicable):

  rawhide

How reproducible:

  always

Steps to Reproduce:
1. go to file bug report
2. randomly forget which of various log files should be added to a particulat type of report
3. appropriate files are sometimes not included
  
Actual results:

  sometimes include wrong files, sometimes wanted files are not included.  
  delay in resolving bug due to insufficient information.  
  extra storage of unnecessary information

Expected results:

  desired files are included with bug report 
  allowing efficient de-bugifying 

Additional info:

A)  the per-package list of desired files shouldnt be too hard to get done soon.
 
  the help file linking might take a while.

  presumably the hyperlinking wouldnt happen all at once 
  but it would be a good thing to start along the path toward.

B)  reads different but a related bug seems to be 
    the 'suggest the next step' bug
    "Bug 406601 - 4.13: More documentation on show bug page"
    ( https://bugzilla.redhat.com/show_bug.cgi?id=406601 )

    "Description:
    Add an area at end of comments list, before 
    the Additional Components text field, 
    giving hints about what to do next, 
    based on who's viewing the bug.  
    (see gnome bugzilla, and possibly upstream)."