On Fri April 7 2006 16:54, Christian Lohmaier wrote: > Hi *. > > On Thu, Apr 06, 2006 at 11:52:54PM +0100, CPHennessy wrote: > > I've just had to entry a bug report and it is quite an unpleasant > > experience : > > http://qa.openoffice.org/issue_handling/submission_gateway.html > > > > There are too many choices for and this only scares way many potential > > bug reporters (Obviously if we do not want those reports... ) > > I agree that there are way to many, furthermore: The by-language option > should be removed (or only list those projects that are really willing > to accept problem reports in their native language and to translate and > file the issue again in the "real" component. > > > Assuming we do want those reports, I think that some changes need to be > > made to the above page. What I suggest is to provide a javascript > > interface where the user is brought thru a number of obvious steps : > > No, no javascript for IssueZilla. It works without and should be usable > without as well with the presubmission-page as well. the reason that I mentioned javascript was that to help improve the user experience. But if it can be done in other ways - then that is better.
> > 1) choose from : installation, writer, calc, impress, database, printing, > > upgrading, other (e.g. web, other langs, ... ? ) > > > > 2) choose version ( latest version being the default - with links to > > download it). > > maintaining that in javascript would be a nightmare anyway. Not necessarily. You could have a script which checks out the file from CVS and updates it if a new release is available, and checks the code back in. > > 3) choose OS > > 4) issue type should only be a choice between "bug" or "new feature" > > 5) OS ( set by default from what the browser sends) > > 6) Summary > > 7) Description > > 8) "Submit issue" > > I'd like to have it like in Gnome's bugzilla. It has both the > traditional way, as a simple interface that is divided into individual > steps. > http://bugzilla.gnome.org/simple-bug-guide.cgi > (you need to have an account to use it) > > It basically asks the questions/infos step-by-step, it doesn't only > preselect a module. But since we cannot modify IZ, nor is there an > obvious way to wrap it, we're stuck with the "dumb" interface. > (I would even use javascript for that :-) > > > - on the "Enter issue" page > > - subcomponent > > would require a way to get a list of valid subcomponents and to choose a > default. While the first part is already not possible, the second one is > even more difficult. Given that there are efforts to add more > subcomponents to ease dispatching of issues to the right developer, > hiding this field would be a step in the opposite direction. Maybe adding a new subcomponent "unknown" is not unreasonable. [snip] > > - cc: > > Hmm. :-/ Not sure about that. But do not forget there is always the possibility for users to see the "advanced page" i.e. the one we currently have. CPH --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
