Hi Jared,
thanks for the feedback!
-------- Original Message --------
Subject: Re: [Design] Bugzilla Guided Bug Entry Form
Date: Wed, 25 Sep 2013 13:34:57 -0400
From: Jared Zimmerman <jared.zimmerman(a)wikimedia.org>
Andre, how much control over this do we have?
The upstream code is pretty low quality, and I won't become a great Perl
hacker over night, so the answer is "It depends". :-/
There are a bunch of things that
bugzilla.mozilla.org have which make
the experience for the guided bug entry form way nicer[1], but I have
not succeeded yet in convincing Mozilla devs to upstream their changes
to Bugzilla.
a few notes:
Step 1 of 3: Find out if your issue has already been reported, Please
search if your bug or feature request has been already reported by
entering some search words in this box that have to do with your issue,
for example upload error or search empty. Then press the Search button.
The results will appear in the box below.
This is pretty verbose, and feels very repetitive, can we just say:
"Search to see if your issue has already been reported."
__________ [ Search Issues ]
for the search results can we refactor them a bit
Summary / Product / Component / last updated / Assigned to / [This is my
issue]
The displayed columns and their order seem to be based on the user's
global preferences on columns displayed in Bugzilla search results, so
for a new user they'd pick up the defaults.
Question is if we want to change the defaults.
[This is my issue] would prompt the user to add the
bug to their watch
bugs list if they have an account,
Interesting,
bugzilla.mozilla.org has this feature already "Follow bug"
button for open tickets next to each search result. I guess that's in
their custom "GuidedBug" extension that they use. Upstream ticket is
https://bugzilla.mozilla.org/show_bug.cgi?id=616490
or prompt them to create an account otherwise.
You will already need an account to reach this bug entry form.
Can we have the search step on its own page, e.g.
force users to search
before you can manually add their own? The option to add your own could
show up after you've done a search.
[ My issue is new ]
I assume there will be other components in the list, only one is showing
now, why is it duplicated in the box and to the right of the box?
That's only the test instance. The text on the right will show the
component description, like on
https://bugzilla.wikimedia.org/describecomponents.cgi?product=MediaWiki
Can we swap Summary and Component areas?
Yes! Added to my to-do list.
Having images is VERY helpful esp. if it is a design
issue, Can we add
an image upload step after summary step, and allow multiple images?
I am fine with adding a "Consider adding a screenshot" explanation for
the time being (L10N Eng also asked for this).
I'm not sure how much work it is to allow adding an attachment directly
in this form; I'll investigate.
I'll leave support for uploading several attachments at once to upstream
developers -
https://bugzilla.mozilla.org/show_bug.cgi?id=278469
is URL usually have helpful information in it, if so
perhaps we could
move that field up below results/expected results
Will do.
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?
Currently "Reproducibility" is optional and under the "Click here to
show four more optional questions" on
http://boogs.wmflabs.org/enter_bug.cgi?product=MediaWiki&format=guided
Wrap the remaining questions in a collapsed section
called "Advanced",
Additional notes, browser, OS(?), mediawiki version(?), etc.
To clarify: By remaining you also mean "Results" and "Expectations"?
Overall this is a great improvement. If you're up
for making some
changes and iterating on it later when the design team or I have some
free cycles that would be great.
Alright. Again thanks a lot for the very helpful and quick ideas!
andre
[1] see
https://bugzilla.mozilla.org/enter_bug.cgi
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/