Launchpad bug statuses

[kit BLAKE]

2007/10/3, Mackenzie Morgan <macoafi at gmail.com>:
>
>
> On 10/3/07, Christian Robottom Reis <kiko at async.com.br> wrote:
> > I question whether any bug status will ever be self-explanatory. The
> > fact that they need to be short means that there will always be some
> > ambiguity in them, and the best we can do is document, teach and guide
> > people into doing the right thing.

Indeed.

> > I have been toying for a long time with the idea that a status dropdown
> > is actually not the best way to guide people to using statuses properly.
> > I just haven't summoned up the guts to try and push this through while
> > getting flamed to death <wink>.
> > --
> > Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125
>
> Perhaps a series of radio buttons with sentences next to them so that
> whoever is triaging understands what each button means.  The status they
> output would be the one or two word statuses that the developers are used
> to, but the users would be picking the right status to begin with.

Note that any html element can have a title attribute which appears in
FF as a tooltip. So hovering over the label for a radio button would
display a brief description.


-- 
Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051
Hoevestraat 10 · 3033 GC · Rotterdam + The Netherlands
OpenPGP 0xE67AD0F2 · Contact = http://xri.net/=kitblake