| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | AE | AF | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | mil | Major Issue | Yellow means UX tasks to be prioritised | ||||||||||||||||||||||||||||||
3 | Priority | Size | Owner | Action | Device | Page | URL | Issue | Recommendation | Screenshot | KL Review 2018 | Follow up | |||||||||||||||||||||
7 | (M) | S | UX | Design - slideshare | All | Main Navigation | When cart is empty, the display of empty cart in dropdown could be improved as current display is confusing | Don't show buttons x 2. Disable or remove checkout buttons. Improve CTA messaging - encourage the user to add items / go shopping. | https://www.dropbox.com/s/kfhez3hgqkcmlbp/20161112%20Cart%20Dropdown%20Empty.jpg?dl=0 | Design required - in slideshare | Slideshare | ||||||||||||||||||||||
39 | M | S | UX | Slideshare | Mobile/Tablet | staging | User Details | staging2.openfood.com.au/account/edit | Invalid email message should be placed with field generating the error. | Some nicer language would be good too :) | https://www.dropbox.com/s/ngmrdf5qszglpxy/20161112%20Staging%20Edit%20User%20Email%20Invalid.png?dl=0 | minor - I actually think the error messages are fine and self-explanatory. Bigger issue is the lack of margins / spacing at sides of screen. Where the error messages are placed is a system-wide design decision, not just mobile? | https://github.com/openfoodfoundation/openfoodnetwork/issues/2429 | ||||||||||||||||||||
40 | M | S | UX | Slideshare | Mobile/Tablet | staging | User Details | staging2.openfood.com.au/account/edit | Password doesn't match error message should be placed with the fields generating the error. | Some nicer language would be good too :) | https://www.dropbox.com/s/1o5udeb4q4t2kcd/20161112%20Staging%20Edit%20Password%20Error.png?dl=0 | minor - I actually think the error messages are fine and self-explanatory. Bigger issue is the lack of margins / spacing at sides of screen | |||||||||||||||||||||
54 | M | M | YO | Mobile/Tablet | staging | Shops | staging2.openfoodnetwork.com.au/shops#/#mega-hub | When a shop is expanded, and a user clicks '+36 show more', the shop is collapsed and user is left at bottom of screen showing 'show closed shops' and 'show all on the map' | Ideally the page should return the user to the show/hide control for the shop just viewed. | https://www.dropbox.com/s/kfj7g5j2bx4u8hu/20161112%20Staging%20Shop%20List%20Collapsed.jpg?dl=0 | minor - I just checked a couple of instances and no one is exceeding no. of shops on this screen at the moment anyway | ||||||||||||||||||||||
67 | Must | Dev | 1295 | Mobile/Tablet | staging | Shopfront | openfoodnetwork.org.uk/tamar-valley-food-hub-wholesale/shop#/about | Shop sections are showing up empty in Mobile/Tablet - but render content in Desktop. Tested in uk. au and staging. staging .au shows the red border but no content. Some shops have the content show (openfoodnetwork.org.uk/stroudco/shop#/about) | If a shop section / tab is empty - do not show tab. Test this on an actual phone, don't emulate. | https://www.dropbox.com/s/f31t0gv6f2j3787/20161112%20Staging%20Shopfront%20Detail%20Tabs%20About.jpg?dl=0 | can't replicate this today - can't see the problem (5.7.18) | ||||||||||||||||||||||
69 | M | ^ | YO | Slideshare | Mobile/Tablet | Shopfront | openfoodnetwork.org.uk/stroudco/shop | The 'shop' section of the shopfront is not clearly presented. In some cases a User needs to scroll past 3 mobile screen heights to view shop items. | Shop' should be a section/tab in mobile view, and the default tab unless user is viewing shop through an 'about shop' funnel from elsewhere in the platform. This would also allow this shop 'message' to be highlighted onscreen in an appropriate fashion. | https://www.dropbox.com/s/1j25bhovsi4ztaa/20161112%20Shopfront%20Shop%20Message.jpg?dl=0 | Slideshare | ||||||||||||||||||||||
70 | M | L | YO | Slideshare | All | Shopfront | openfoodnetwork.org.uk/stroudco/shop | For single items - the item Name and Description is often repeated. In mobile this means the User is being made to read the same thing twice over and over. | ? Needs further investivation to see if shop inventory can be displayed in a better way. Acknowledge item 'groups' is what the current solution works best for. | https://www.dropbox.com/s/wy0qhg5om6l5t6j/20161112%20Shopfront%20Duplicate%20Title%20Description.jpg?dl=0 | |||||||||||||||||||||||
71 | M | ^ | YO | Slideshare | All | Shopfront | openfoodnetwork.org.uk/stroudco/shop | For shops with extensive inventory, the grey bars are difficult to scan (very heavy visually). | Sub-total row should be visually lighter. Unless there are multiples of the one item, the sub-total row isn't necessary. | https://www.dropbox.com/s/ihtxmarf7i0ovy2/20161112%20Shopfront%20Inventory%20UI.jpg?dl=0 | |||||||||||||||||||||||
82 | M | M | Slideshare | Mobile/Tablet | staging | Checkout | Steps' to complete checkout completion are not easily scanned/understood checkout process starts at the bottom of initial view (those pesky tab like items) and they are expand/collapse modules | For mobile view, have all steps expanded (unless sections are prepopulated) or improve presentation as it is confusing to have expand/collapse sections for a first time checkout process: https://www.dropbox.com/s/lzxol2lirc0qt7s/20161112%20Staging%20Checkout%20Guest%20Payment.png?dl=0 | https://www.dropbox.com/s/8juep4zbzz0uzbv/20161112%20Staging%20Checkout%20Default.png?dl=0 | ||||||||||||||||||||||||
84 | M | S | UX | Mobile/Tablet | staging | Checkout (not logged in / guest) | Options provided are 'login' and 'guest', there's no 'join' option (although this action can subsequently be done via the login tabbed modal | Is this for a specific reason? | https://www.dropbox.com/s/6alkukk4j7f1dhc/20161112%20Staging%20Checkout%20Not%20Logged%20in.png?dl=0 | i'm not familiar with join, but this seems lower priority than other issues | |||||||||||||||||||||||
85 | M | M | UX | All | staging | Checkout | Hide' control redundant in this view (first time checkout flow). | Remove to reduce vertical height / scrolling required (fix all the hide-shows on this form) | https://www.dropbox.com/s/y5hrpcbpgrkfbpo/20161112%20Staging%20Checkout%20Guest%20Details.png?dl=0 | not a big deal | |||||||||||||||||||||||
86 | M | ^ | Mobile/Tablet | staging | Checkout | Data inputs are shown twice to the user. | Show the collapsed view when the section is collapsed. Show only the editable fields in edit mode. Less visual load for the user. | https://www.dropbox.com/s/ob4ph5k8f0yqfkm/20161112%20Staging%20Checkout%20Details%20Submit.png?dl=0 | not a big deal | ||||||||||||||||||||||||
87 | M | ^ | Slideshare | All | staging | Checkout | The red X next to the section heading tells the user something is wrong - but not what (which in this case I think was that all fileds hadn't been filled). | Consider alternate presentations for required fields | https://www.dropbox.com/s/a34up7jt254mdwl/20161112%20Staging%20Checkout%20Details.png?dl=0 | this should be considered within a more general / system wide handling of incorrectly filled or default fields | |||||||||||||||||||||||
88 | M | S | All | staging | Checkout | For 'pickup points', it would be nice to include the specific location of the pickup point for the User | Need to check this information is also being included in the confirmation email | https://www.dropbox.com/s/ygp70khopqsvw4g/20161112%20Staging%20Checkout%20Pickup%20Point.jpg?dl=0 | Enterprise user can sort this out - not a ux issue | ||||||||||||||||||||||||
92 | M | UX | Slideshare | All | staging | Checkout | Using 'green' to indicate successful completion with a red button to proceed to next step = confusing | Fix all the colours. | https://www.dropbox.com/s/5q8mhrlkwm520dj/20161112%20Staging%20Checkout%20Shipping%20Info.png?dl=0 | maybe, bigger issue system wide | |||||||||||||||||||||||
93 | M | UX | Slideshare | All | staging | Checkout | Red error messages with red buttons as primary actions = confusing | ^ | https://www.dropbox.com/s/ehdmbuu9gb3qw2u/20161112%20Staging%20Checkout%20Shipping%20Address%20Error.png?dl=0 | ||||||||||||||||||||||||
94 | M | M | UX | All | staging | Checkout | User data is being stored from previous checkouts/orders (ie. billing address) and being used to pre-populate subsequent checkouts. | Provide access / edit ability to users - consider using 'my account' area | feature, not ux issue | ||||||||||||||||||||||||