Custom Bug Listings - UDS-P Session notes

• Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/other-p-uds-custom-bug-listing-acceptance-testing

• 25 people, most of whom were vocal, so a good amount of feedback
• There was general consensus on the points below, but as with every group discussion, it’s impossible to know if everyone’s true feelings would have been the same if we’d done 25 1-to-1 sessions
• However, all the points covered look like genuine usability issues rather than a vocal individual’s ‘pet hate’

Visual elements – spacing, colours/text formatting

• Too much white space in general, between information being displayed
• Information could be brought closer together, better use of space
• The 'importance' is highlighted, making it look like the most important aspect. 'Status' is often more important and should be visually more prominent than 'Importance.'

• The group felt that 'Status' was hard to see (887576)

• fix released and fix committed has green text and look like ajax action (887575)

• Bug number text - make darker - hard to see (currently greyish/soft)
• ? Importance colours - the copy within these isn't clear
• Icons on 2nd line so they're closer to the bug text
• Heat could go on to the 2nd line too
• ? Put targets together

• needs a spinner to show something is going on when you reorder the listing (85272)

Sorting options

• Sort by options - everyone liked the current options. We asked if they'd be likely to use all of them, or if there were any they'd never use.
• The group said that all of them could be useful. A more structured card sorting exercise would be useful here, to discuss options and default settings.
• The arrows – These need quite a bit of work - the arrow symbol isn't visually strong enough and default settings are unclear

• Default seems to be on 'highest --> lowest', this works well for bug heat, but need to look at the other options without making it too confusing.

• Could be added as an extension of the card sorting - what do people find most intuitive?

• Maybe some kind of additional info in the form of copy, to make it clearer what the default/switch options are - eg: hottest / coldest bugs, showing ‘A-Z’ or ‘Z-A’, ‘newest’ or ‘oldest.’
• The group wanted to see sort by 'Age.' A number of the group wanted to see sort by 'Tags' as well - not sure if this is too tricky?
• Is it possible to order by location?

Miscellaneous

• advanced search show sort widget at top of the page (887646)

• person's bug page (e.g. https://bugs.staging.launchpad.net/~ubuntu-server) don't show the sort widget (887232)

• when search results return just one result the bug heat column is in the wrong place. (887571)

• https://staging.launchpad.net/~ubuntu-server/+packagebugs returns an UFD (887214)

• zoomed text doesn't display so well, overlaps with right side portlets
• accessibility consideration (how screen readers display info, how will blind users know where they're at?)
• allow people to have the old columns layout or the new columns layout
• icons (blueprint, patch, heat, etc) are floating on ubuntu page

• Showing the package or project in a bug listing for that package/project only is unnecessary since you'll know which context you're in (e.g. https://qastaging.launchpad.net/launchpad/+bugs). This came up as well during the mock up testing.