Usability braindump needs to be summarized into a report

I did a usability testing session with jbailey earlier today

I did a usability testing session with jbailey earlier today. It needs to be summarized into a report ASAP. Here, for the record, is the brain dump:

Notes from user testing session with jbailey:

Date: July 8, 13:40

Test conducted by: Brad Bollenbach

TASK: Logging In

  - thought email was convenient
  - guessed his normal ubuntu password
  - worked first time

says product is something he installed manually

package is something he installed with something else

"oh that thing's a space shuttle in the corner"

TASK: FILING AN UBUNTU BUG

used the generic form (where ubuntu is a "field")

notes Ubuntu is not in the default list

blank box for select distribution

do i type ubuntu or breezy?

says title of window looks wiki-style

great it knows glibc

would have expected (list) gives a list

does the dot mean required?

points out that there's no Cc box

bug page font is small, enlarges it

"oh god, this didn't send the bug upstream did it?"

starts looking at the "also occurrs in"....

add distro release task

didn't know what his options were at first

tried to add two different tasks on the same add task page

made an input error (required input missing) on the binary package
field

that doesn't make sense that the bug page lists:

  Ubuntu glibc
  Breezy Badger glibc

laughs at "infestation"

asks: "how do i take ownership of this bug"

wonders how bug nicknames avoid collisions, types "langpack" to see
what happens

maybe he takes ownership if subscribes to the bug
  - default shown was "watch"
  - he says "i don't feel like watching" i want to take ownership of
    it

wonders how he gets back to the bug page from the bug edit page

finally clicks on the task on the bug page, "Oh! there's the
assignee!"

  - notes he can't just take it

searches for assignee, notes he has two accounts on the
system...sarcastically says "oh, that's convenient"

fills out explanation of status with "Taking my own bug"

says the page layout changes when he assigns the bug

has a revelation: "Oh, i see, it can be assigned to multiple people,
depending on what it's associated with!"

"so, can i take ownership of it in both places?"

notes he has it reported generically against Ubuntu glibc and against
breezy, but doesn't want to fix it in hoary, so decides he wants to
"take off" the Ubuntu glibc task. wonders how he does that.

tried clicking save changes on the read only form

assumes that the correct place the task should be filed against is
breezy, rather than generically against Ubuntu

looking at the task page, has no idea how to get rid of the Ubuntu
glibc task

repeatedly tries the Save Changes button on the task view page because
he can't see any other thing to do, but it doesn't help

tries clicking in the breadcrumbs to get back to "bug 1311 depth", but
it doesn't go back to where

"oh i get it, i had to go back out and then come back in"
  - clicked on +bugs in the breadcrumbs and clicked on the bug id
  - this is the page he wanted to get to

also assigns the breezy badger task to himself
  this time decides to leave EoS blank. "it'll be pretty obvious why
  i'm doing it."

back to the bug listing, clicked on the assigned to me filter:
  'oh and now i have one assigned to me. nice.'

says "I guess it was a mistake to file it against the generic Ubuntu",
thinks he should have filed it against breezy specifically

"oh neat, you can followup on comments. i wonder how that looks once
it's working..."

trying to get rid of Ubuntu task:
  - oops, i accidentally gave away the word task in asking him a small question to ensure i was clear on what he was trying to do while i was recorind it
  - he didn't see that word, had no idea that was a task
  - tried edit bug details
  - "i have no idea how to proceed" (to "get rid of" the Ubuntu task)
  - ...but, oh, finds out "maybe i can reject it?"
  - says he doesn't want to reject it, wants to delete it because it
    was a mistake

goes back to 1311 and says "did it go away?"

types 1311 in the searchtext box to jump to the bug

"oh, status rejected, so that wasn't how to get rid of it"

points out that bug statistics must be wrong, because assigned to me
says (0) even though he has a task assigned to him
  (editor's note) the task is actually assigned to the specific distro
  release

clicked on "Welcome, Jeff Bailey"
  - say his person screen
  - saw bugs assigned on the left
  - and then *does* see that bug that was assigned to him

got a 404 clicking on "bugs" in the breadcrumbs (i.e. /malone/bugs)

looking at the bug page again, can't remember how he got to that
+assignedbugs listing anymore

says he wants a "nice little X" to the left of the sp name in the task
row to make the task "go away"

still wandering around trying to make that task go away, goes to the
bug activity page, chuckles at the "XXX: not yet implemented" notes

now i give a hint about how to make a task "go away" because he says
he'd have given up by now in real life
  - explain that "reject" does mean go away

i also note that he didn't change the status to "Accepted" when he
took the bug

TASK: find all the upstream baz bugs that have the word "changeset" in
them

clicked on the "malone" breadcrumb from the bug page because he
figures he has to go back to the "start"

tries "View Distribution Bugs"
  - nope, that's not it

then tries "View Assigned Bugs"
  - tries searching for bugs assigned to baz
  - oops, nope, that's not it

tries "File a bug on a Package" because it said "if you're not sure,
start here"

goes back to the distribution listing, because he figures he needs to
get to the list of bugs and then "tweak it from there"

drills down to /malone/distros/ubuntu
  - points out it was slow
  - first tries to search for "baz"
    - 4 results
  - then tries to search for "baz changeset"
    - finds no bugs

Ooops...realizes that the distribution screen isn't where he should be
  - reiterates that he was trying to find a bug on upstream bazaar
    though

tries to manually type /malone/upstream to see what happens because
there's nothing else obvious to him on the front page telling him what
he should do

goes back to the front page
  - "oh, but a product is something i tried to install manually"
  - clicks on "File a bug on a Product"
  - drills down to baz's search listing
  - searches for the word changeset, whee

finds he doesn't pay attention to the URL, so generally that isn't
used much to guide him

refers to the "breadcrumbs" the "status bar"

TASK: figure out what bugs you want to work on

  - explains to me his bugzilla workflow
  - has a canned search called ""

random interesting note: as he's explaining how he uses bugzilla to
me, he notes he never reads bugmail, because there's just too much to
read. shows me another RT example, of how nice and scannable the
information about incoming support requests is to him, and is much
more useful to him that all the bugmail "crap" in his Inbox.

  - goes to his person page (clicked on Welcome, Jeff Bailey)
  - clicks "Bugs Assigned"
  - "oooh" (notes the packages link on the person page)
  - tries edit details to add some packages he maintains
  - "I just added my IRC name (page reloads) oh! and it didn't stay!"
  - notes there's only one bug assigned to him right now
    - notes that the row is hugely tall and would be unscalable for
      the 90-some bugs that come back from the canned search he uses
      in bugzilla
  - finds it interesting that upstream/package is blank and is fairly
    certain it ought not to be

TASK: file a bug about IRC Nickname not saving

- clicks back on "Launchpad" in the breadcrumbs

- quickly figures out it's probably the product link (file a bug on a product)

- searches for "Malone"

- Malone and Launchpad returned. clicks on "Launchpad" to see the lp bugs

- searches for "irc"

- finds one bug (663), reads it to figure out if it's his bug
  - is initially confused by the rev. chronological comment ordering
  - notes the duplication of the initial comment

- clicks on "bugs" from that bug page, 404!

- goes back to the page and uses the "Back" button instead

- back on the lp bugs page, quickly sees the filebug link and clicks
  it

- quickly fills out bug information and lands on the page of the bug
  he just filed

- stares at the page for a bit

- asks "i wonder how i can see the list of the bugs i filed"
  - clicked again on "Welcome, Jeff Bailey" and found the "Bugs Reported" link
  - "oh, that's handy"
  - notes that 1311 is listed twice
  - tries clicking many times on a row in that listing, nothing
    happens. "is it slow?"
  - notes he has to be right on top of text to click it

TASK: merging duplicate accounts

- starts at his jeff bailey page because "everything else have been from there"

- clicks on the email addresses link

- sees the list of "These addresses may also be yours", confirms that

- add a new address: <email address hidden>, clicks Add
  - "the email address...was already registered..."
  - clicks on the "Merge Accounts" link to sort it out
  - reads the whole first paragraph on the "Request Merge of User
    Accounts" screen
  - says "oh, i guess it needs to be done by hand"
  - clicks (list) because he knows theres "no point" typing anything
    in the box first
  - tried the email address he would use to login
    - found nothing
    - didn't actually *say* it found nothing
  - then tried "jeff bailey"
    - found "all three" (salgado gave him a hint on IRC :)
  - wants to merge <email address hidden>
  - clicks it and "Submit"
  - gets screen saying you have to prove that you have access to all these emails
    - "oh god, are you kidding!?"
    - "okay...i wonder what it does for accounts i no longer have access"

(a brief workrave moment passes)

"so the emails should have come through by now"

sees the email "Launchpad: Validate your email address"
  - notes it would be nice to reply to this email to do the
    confirmation
  - clicks on the URL
  - brings up the +validateemail
  - says "type in your password"
  - said "this is already taken, if you want to merge the accounts,
    you can click on the 'Merge Accounts' link
  - went to click the URL in the email again when i asked him to
    confirm exactly what he did, but, POOF, it's now a 404

points at all the "spew" in his Inbox from "every time i touch
1311". it sent him 8 messages from the changes he made on 1311.

now merging <email address hidden>
- clicks on email link
- brings up merge page
- fills in password and Submits
- this time it work

oops, realizes now that that FIRST email he was working with was
actually a different email to VALIDATE one of his email addresses

while merging, notes that he's "not sure which jeff bailey i'm logged
into now"

merges <email address hidden>
  - clicks Submit once...takes too long
  - clicks Stop and then Submits again
  - System Error
  - looks at the page (presumably reading it)
  - clicks on the link from the System Error page to report the bug

has now arrived at a situation where, when he clicks "Welcome, Jeff
Bailey"