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. > 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. > 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 :-) > Things which do *not* need to be shown for the "simple user" : > - on the main page : > - software components But that is one of the most important things (and quite easy to determine for the user) > - by project > - by language > - by code module agreed. > - 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. > - initial state this would be easy (unconfirmed). > - assigned to this as well (empty) > - platform for this you would need to get a list of valid platforms again and choose one. While you could try to guess it from the browser, this is a hack and often enough simply wrong. Having the correct platform set in an issue is important for QA. > - priority could be possible. > - cc: Hmm. :-/ Not sure about that. > Opinions ? The enter issue page is again not easily modifyable. If it was, I would like to split it up into several pages. ciao Christian -- NP: Downset - Downset Join #qa.OpenOffice.org on irc.freenode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
