Last modified: 2014-01-13 01:59:23 UTC
This is probably not intended to be used but it is publically accessible, hence filing a ticket. https://bugzilla.wikimedia.org/enter_bug.cgi?product=Tools&format=guided says "This is a template used on mozilla.org. This template, and the comment-guided.txt.tmpl template that formats the data submitted via the form in this template, are included as a demo of what it's possible to do with custom templates in general, and custom bug entry templates in particular. As much of the text will not apply, you should alter it if you want to use this form on your Bugzilla installation." It also mentions the "Talkback Crash ID" of Mozilla and the severity list is the default one too (missing "blocker").
(In reply to comment #0) > This is probably not intended to be used but it is publically accessible, hence > filing a ticket. Mozilla has done a lot to adapt Bugzilla to their uses. And it isn't all documented very well. Thanks for pointing this out. It looks like it could be very useful.
Code: https://bzr.mozilla.org/bmo/4.0/files/head:/extensions/GuidedBugEntry/ Also see https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=moz-project-review which went live recently as per https://bugzilla.mozilla.org/show_bug.cgi?id=787478
A different approach is taken by LibreOffice to make it easier to report helpful bugs: They have a bug submission assistant at https://www.libreoffice.org/get-help/bug/ and described on https://wiki.documentfoundation.org/QA/BSA
https://bugzilla.mozilla.org/enter_bug.cgi looks lovely but after looking at the (rather Mozilla-centric) code I don't see me spending that much time to make it work for us (yet). So a small first step to try here is to make the "normal" guided entry form in Wikimedia Bugzilla suck less (and look slightly better).
Created attachment 12534 [details] Work in progress on /template/en/custom/bug/create/create-guided.html.tmpl
Change 74360 had a related patch set uploaded by Aklapper: Configure Bugzilla's Guided Bug Entry Form https://gerrit.wikimedia.org/r/74360
After attending a talk "Supporting end user reporting of human-computer interaction issues in Open Source Software projects" by Fabiana Simões last week I'd like to rework this patch, to simplify language and cover the questions • what were you trying to do? • why did you want to do it? (optional; helpful for UX requests in order to understand the intention) • what did you do? • what happened? • what were your expectations? • what are you running?
Test instance available at http://boogs.wmflabs.org/enter_bug.cgi?product=Wikimedia&format=guided - log in as horst_horstmann@gmx.net, use the part in front of @ as pass, and file a ticket. The guided form will ask you seven questions, and four more if you have time. It will create a new, and better structured bug report. Privacy warning: Note that the email functionality of boogs.wmflabs.org actually works, so I will receive the data that you entered. Compared to the previous patch, I changed sections to incorporate the recommended questions towards reporters which are shown on slide 48 of http://www.superlectures.com/guadec2013/how-to-not-report-your-ux-bug and tried to simplify language, keeping many reporters in mind who do not have English as their mother tongue. The patch also points for MediaWiki and Wikimedia to the corresponding helpdesk support pages on the corresponding wikis. I still need to turn the two files into a proper patch for Gerrit, that's left for tomorrow. And the CSS could use some polish, I dusted the ugly upstream code, but only basically.
(In reply to comment #8) > Test instance available at > http://boogs.wmflabs.org/enter_bug.cgi?product=Wikimedia&format=guided - log > in as horst_horstmann@gmx.net, use the part in front of @ as pass, and file a > ticket. > The guided form will ask you seven questions, and four more if you have time. > It will create a new, and better structured bug report. This is really awesome. Thank you! I think it's much better as a structured way of getting the questions we invariable ask answered before the bug is filed.
https://gerrit.wikimedia.org/r/#/c/74360/2
Feedback on design list: * Severity dropdown: copyedit needed: "An average a bug that [...]" * Please add a warning that "your email address will be publicly displayed" * Search text too verbose; shorten to "Search to see if your issue has already been reported." * swap Summary and Component areas * URL usually have helpful information in it, if so perhaps we could move that field up below results/expected results * Can we make reproducibility an optional step and just add the control under the "steps to reproduce" not in a new section just below the text field? Feedback by L10N eng and design: * Ask for a screenshot. * Investigate how much work it is to allow adding an attachment directly in this form
Patchset 4 is available on https://gerrit.wikimedia.org/r/#/c/74360/4 which includes the feedback given: (In reply to comment #11) > * Severity dropdown: copyedit needed: "An average a bug that [...]" Done. > * Please add a warning that "your email address will be publicly displayed" Rethinking this, it's not needed, as users already got warned when registering an account in Bugzilla. > * Search text too verbose; shorten to > "Search to see if your issue has already been reported." Done. > * swap Summary and Component areas Done > * URL usually have helpful information in it, if so perhaps we could > move that field up below results/expected results Done > * Can we make reproducibility an optional step and just add the control > under the "steps to reproduce" not in a new section just below the text > field? Done. > Feedback by L10N eng and design: > * Ask for a screenshot. Done as part of the Other information / "Add an Attachment" section.
Change 74360 merged by Dzahn: Configure Bugzilla's Guided Bug Entry Form https://gerrit.wikimedia.org/r/74360
Deployed. Some followup stuff (move CSS into separate file, cleanup stuff like <span>Severity</span> by using variables instead, search results look crappy) can be done in a separate ticket. Thanks everybody!
