Red Hat Bugzilla – Bug 506936
[RFE] Simplify the reporting form for the inexperienced reporter.
Last modified: 2009-12-04 17:01:59 EST
We ( Fedora-QA ) are going to be trying to improve reporting to ease everybody's life ( Reporters, Maintainers, Triagers ) One issue to address is that it has been mention various times in previous release cycles,through mailing list, forums on irc channels that inexperienced reporter(s) feel bugzilla is to complicated to work with and thus they tent to stay away from
We of course want to have as many reporting as possible at it can be a bit difficult increasing the number of reporters if the reporters stay away from bugzilla.
Now the task here is to find a way to present to different forms
One minimal form ( as few elements as possible ) for the inexperience once and a full blown form for the experienced once that might actually use all of the option that is on the current form.
I think it safe to say that this are the minimal elements that need to be present for the inexperience reporter the rest could either be hidden or made non editable.
Platform # If present selectable values should only be All,i386 and x86_64
Version # Selectable value should be restricted to supported releases + Rawhide
Security sensitive bug
For more info on QA improve reporting see here..
(In reply to comment #0)
> One minimal form ( as few elements as possible ) for the inexperience once and
> a full blown form for the experienced once that might actually use all of the
> option that is on the current form.
FYI, Bugzilla 3.4 will declare some of the fields of the bug entry form 'advanced'. Users will have a choice between a form which shows only the 'simple' fields and all of them (a cookie will remember your last selection).
See bug #376673 on bmo for details as well as http://lpsolit.wordpress.com/2009/05/24/simpler-form-to-file-bugs-in-bugzilla-3-4/
Excellent this addresses this issue perfectly
We could remove the OS element or lock it to Linux.
There is one thing lacking thou ( had not filed that RFE yet )
and that is to reduce the risk of duplicated reports we need to provide a predefined search of the component the reporter chooses in Bugzilla or an url https://admin.fedoraproject.org/pkgdb/packages/bugs/$component using the url only benefits the Fedora while the predefined search would server both Red Hat and Fedora which the reporter could just click ( Could be shown in the component description ) or even better would be if we could show the reporter the description field of the latest 5 or 10 reports against the component he's about to report against.
The search field is a bit to broad ( the simple one ) and the advanced one is to complicated for the inexperienced ones so they never bother to look to see if the issue their facing has already been reported.
Filed an upstream bug #499320 on bmo for the "Component Recent Report" element I mentioned earlier with an descriptive picture imagine that. ...
BTW do we have an running development version of Bugzilla somewhere to test
or does Red Hat handle all the bugzilla testing internally?
Moving to the Bugzilla product (the Fedora/bugzilla target is for the rpm of bugzilla as shipped in Fedora).
Red Hat's Bugzilla is planned to move to 3.4 not long after it's final release. The new 3.4 will have the much simplified bug entry form. To view a demonstration of the new form:
Already took a look at it ( see comment 1 from Emmanuel )
I also filed an upstream RFE Add an "Component Recent Reports" element to the reporters UI in the hope that it will reduce the risk of inexperienced reporters filing duplicated reports
Suggested new mockup on the new simplified report form
FYI, Bugzilla 3.4 was released on 28/7/2009 and 3.4.1 was released on 1/8/2009.
Doing some testing https://partner-bugzilla.redhat.com
Is it possible to remove the "OS element" or hardcode it to Linux it's not
like we are testing OS-X M$ Windows All or Other....
I would rather leave it there as we do have quite a few products that are not just Linux specific. For example we are moving more and more JBoss products over which run on multiple platforms such as Windows/OSX/etc.
I would not be opposed to having the default value be Linux to start which would catch most people.
actually after checking the code we already set the opsys to Linux by default unless the user manually changes it to something else. But I still want to leave it on the simple bug screen as we do have more and more users who are not always on Linux.