To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=74356 Issue #|74356 Summary|Poor usability of website when reporting bugs Component|www Version|current Platform|PC URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|openoffice.org website general issues Assigned to|[EMAIL PROTECTED] Reported by|jdpipe
------- Additional comments from [EMAIL PROTECTED] Fri Feb 9 00:17:56 +0000 2007 ------- This is about website usability. I find the location of your bug tracker within the OpenOffice.org website *very obtuse*. Can I suggest you do a quick five-person poll a la Nielson to observe how hard people find it to locate the bug tracker? I think that you will find that people not experienced with the Open Office website will have quite some difficulty locating where to go. Emphasis should be on making a simple, intuitive bug search and reporting tool, rather than burying links and passing people through hoops. Obviously you want to reduce duplicate reports. Having a confusing system *reduces* the chance that people will be able determine whether or not they are reporting a duplicate. FWIW I think that the GNOME website is the model for user-friendly bug reporting: gnome.org --> support --> report a bug --> simple bug assistant cf openoffice.org: openoffice.org --> support --> ???? openoffice.org --> contributing --> quality assurance (QA) --> QA website --> report bugs --> how to start --> ??????? openoffice.org --> contributing --> quality assurance (QA) --> QA website --> report bugs --> issuetracker Is it 'report bugs' or 'report issues', or is it 'quality assurance' (or is it QA?). And why would I care about all that guff on the 'how to start' page? And why do you assume on the 'support' page that I can't possibly be seeking support for a bug that I've found? A user should NOT have to go through a QA website to report a bug! QA is a back office activity, not a front-desk thing! The bug reporting page should focus 100% on the person reporting the bug, not on the team that manages the bugs. Finally, perhaps there is some philosophy or other behind the 'issue' versus 'bug' choice of terms (ie QA people know that reported bugs are often not bugs but just silly users like me) but how about calling a spade a spade, eh? And the user point of view is that they are experiencing a bug -- so they will be looking to *report a bug*, not *be a person with an issue*. And the user is always right, isn't he? :-) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
