Issue 52092 - Getting to issue tracker and being useful once you're there
Summary: Getting to issue tracker and being useful once you're there
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-07-18 00:17 UTC by jeidsath
Modified: 2013-02-07 22:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description jeidsath 2005-07-18 00:17:21 UTC
It is not obvious how to navigate to issue tracker for someone seeking to file a
bug report.  Once there, the query interface is terribly unintuitive, assuming
that a user can even find it.  The keyword search is at the bottom of the page
instead of the top, and does not give any results for any query that I could
think of.  Summary search worked like keyword search ought to have.

When submitting bug reports, subcomponents should not be a required field unless
someone can figure out how to make it obvious to users where a bug should be

The "issue type" should not be a bunch of words all meaning the same thing. 
Fixing a DEFECT is an ENHANCEMENT to some FEATURE or other which will be a TASK
for whoever is writing the PATCH.

Ideally, here is how things should be:

Big link to "bug reports" or something similar on either the main page or the
support page.

Big link from the "bug reports" page to a "search bug reports" page.  Even
better, put the search form on the main bug reports page.

Put the keyword search at the top of the bug report search page, and put a
submit button right next to it.  Fix the keyword search so that it actually
covers every important field and actually comes up with results.

Either remove the subcomponent selection box on new issues or place a button
"spin the wheel" next to it so that the system can make a completely random
selection and save the user from doing the same thing.

Replace "issue type" with something useful, or just file everything under
PROBLEM.  I'd suggest categories like "broken feature," "bad user interface
design," and "feature request."  

Finally, it would be nice if issue tracker was more friendly to UI enhancement
requests.  This is the opinion of one person, but that is the one place where OO
needs the most work.