Summary

Dan and Diogo conducted interviews with some users to gather feedback about the custom bug listing feature.

The general feedback was good. People appreciated the new feature and thinks it looks beautiful and that the design works for them.

A point we didn't consider is that a lot of people use greasemonkey scripts to change how LP looks/behave. This change is very likely to break those scripts, so we could make an announcement about and request people to update their greasemonkey scripts.

Common patterns:

• have a way to sort by multiple attributes (sort by importance and status);
• assignee in the default visibility
• be able to sort by any of the attributes (assignee, tags, etc)
• icons have no immediate meaning

Individual interview notes

Chris Gregan - OEM QA Manager

• initial setup, add correct user to qastaging ~custom-buglisting-demo team and ~launchpad-beta-testers on production
• "looks pretty good"
• Is the default option good enough?
  • he'd add age and assignee in the default
  • assignee seems more important to add to the default set
• thickness of line could be a pixel thicker in the bug listing, specially in between bug listing rows.
  • some way to differentiate the header from the bug listing row
  • maybe put some subtle shade on each row
• does it address your needs in terms of workflow, visible information, sorting? "it's doing exactly what I need!"
• wrap around point for bug title could make better use of real estate
• sort by two different items (status and importance) is something that he'd like to have

James Ferguson - Commercial Engineering

• used greasemonky scripts and now LP provides the functionality
• bug tags are kinda difficult to see because they are not in columns, not much about color, but it was easier to scan when they are columns
• requested multiple sort (importance and status example)
• default is fine and he can change the attribute if needs to
• reset to default not working for chromium
• would like to have an option to have old bug listing (column rather than list)
• maybe collapse the portlet to allow for more screen space
• be able to filter information from the list without going to advanced search (for example, exclude all fix released bugs)
• sort by bug tags, assignee
• we're going to break a lot of people's greasemonkey. we need to announce that to them before release
• custom bug listing for specific pages rather than a global config
• customize bug listing behaviour through the URL
• said the feature development is going in the right direction

Ursula Junque - Ubuntu Defect Analyst

• her team don't use LP bug pages, they use custom reports

  • http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html

  • http://reports.qa.ubuntu.com/reports/ubuntu-server/triage-report.html

• advanced search return results without the sort widget (http://goo.gl/aoGoY)

• visible information has a {display_name} as one of the options
• apparently they wanted to use their custom lists, but once we found a page using the custom bug listing ursula really liked it (see goo.gl page above)
• sort widget should have option to order by any of the attributes
• assignee should be part of the initial default
• reset to default is not working on firefox as well
• really liked the new bug listing. "better than I thought"
• portlet on the right side is important
• information on portlet should display info about the search results

• bug heat seems to broken, the icon displayed doesn't show up any flames for a bug with lot of heat (877852)

• number of affected people as one of the visible information option
• title was a bit hard to read when you select all information to be displayed
• ascending/descending order was a bit confusing

Tom Ellis - Premium Service Engineer

• The search bar: 'Search bugs in launchpad itself' - This takes up a lot of unnecessary screen space
• Expected to see things more like a table
• He felt that he could still fit in loads of bugs on one page - one line with everything on would be too messy
• Doesn't care about bug heat or tags
• He thought the position and colour of the cog was fine - used to using this kind of symbol to change settings
• Next/previous - greyed out, slightly colour blind, did not see this
• Would like to see a column field that explains icons in the far left-hand side
• Colours of the status is cool
• Would expect it to use a bit less space in general, but not really important

Ezio - Support team lead

• Uses bugs sometimes, rarely (so an occasional user)
• Some icons dont have immeadiate meaning - the hover over is good - happy with this
• He likes the fact that they're in line - visually more interesting to have a table/column to sort - it's perfectly functional as it is
• Doesn't think that it's too spaced out - it's just right, density is just right
• He resized the page - works well when text is smaller
• Make it clearer how many pages there are - the back/forward isn't clear enough
• Bug titles presentation - they really stand out which is good