Very hard to modify bug status fields

[Jeff Waugh]

The only way I can see to get to the bug status fields is by clicking the title of the bug in the bar at the top of the bug page. It took me a long time to figure that out - 3 minutes - which is probably longer than a casual user would bother looking.

How about putting bug status fields behind a disclosure triangle at the top of the bug page? I totally understand not showing them by default, but atm, they're very hard to find.

[Matthew Paul Thomas (mpt)]

Jeff, I'm really sorry that Malone makes this question even necessary, but: when you say "the bug page", what URL are you referring to? Currently on a page like <https://launchpad.net/products/malone/+bug/2598>, the title of the bug isn't shown in any "bar at the top of the bug page" except for the browser window's title bar (bug 2608).

[Jeff Waugh (jdub)]

<quote who="Matthew Paul Thomas">

> when you say "the bug page", what URL are you referring to? Currently
> on a page like <https://launchpad.net/products/malone/+bug/2598>, the
> title of the bug isn't shown in any "bar at the top of the bug page"
> except for the browser window's title bar (bug 2608).

Sorry - the link in the 'fix requested for' column, which ends up being even
more obscure than my brain allowed.

[Christian Reis (kiko)]

We should just use the word "task" and educate the users, in my opinion. I think we've experimented enough with using "status" "fix requested for" and "target bug to" here, and none of the results have made me more confident that that is the right thing.

Use task and bug, provide a page we can point users when they are confused, and end the confusion.

[Jeff Waugh (jdub)]

How will this help me find the status fields? If a disclosure triangle is
not desireable for whatever reason (it works well for comments down the
bottom), even an obvious link in the task list for "modify status" would
help.

(I understand that lack of context may get in the way - but in many cases,
users will get to those bug pages via a particular context.)

[Christian Reis (kiko)]

Sorry, I was referring to a separate problem (the one you pointed out in the last sentence of your comment).

We want to allow viewing and modifying the current context's status, but the URLs have just changed, and Mark is very uncomfortable with the idea, so we need to bide our time until it's ripe for changing.

[Jeff Waugh (jdub)]

Okay, thanks... and thanks for the email interface too. :-)