✂️ UX Paper Cuts 18.4 → AI

During 18.4, the Paper Cuts team will collaborate with teams working on Duo features.

Potential issues

(Issues labeled with UX Paper Cuts and candidate18.4)

display: table
query: group = "gitlab-org" and label = ~"UX Paper Cuts" AND label = ~"candidate::18.4"
fields: title, createdAt, milestone, assignee, status
title: Potential 18.4 Paper Cuts issues

Potential work not associated with existing issues

• Expose a message when the context window is filled (when I last tested it failed silently and required I open language server logs to diagnose problem).
• Remove the feedback link for every Duo response and replace it with a thumbs/up down only at the end. Figma example.
• Have Duo actions use a more muted style. The wrench icon in particular is high contrast. The icon and action phrase also defaults to suggesting work is being done (ie. wrench plus Get phrase) when it might be more intuitive about what's happening if it said Read file and used an eye icon instead of a wrench. Figma example
• Cleanup the way we communicate "Duo is working". Currently we end up with three moving elements (text streaming, Duo progress indicator, placeholder text switches). The Duo is generating an answer indicator is redundant imo. I think we could just use something like a shimmer animation on whatever action Duo is currently running. Problem example and potential solution example.
• (NOTE I don't think we have checkpoint functionality yet so might be irrelevant) Visually set apart checkpoint locations so users can quickly find them. Also adding a stepper ability to jump between checkpoints would be useful. Figma example
• Putting more design thought into how users view a diff and approve/reject/edit Duo generated code would be helpful. This is a key part of the product and we're getting some early feedback that it's not hitting the mark. @viktomas probably the person to talk to around VS Code API limitations we ran into.
• UX work dedicated to thinking about the Duo Settings for enabling access to Duo. As we move to a different billing approach, and the addition of Core, questions are arising about how to address granular yes/no Duo access for end users. Right now, a customer has to disable Core if they want specific users to NOT have Duo access and then rely on the old Pro/Enterprise seat assignments. What if we enabled direct control of yes/no Duo access at the Seat Assignment level for Premium/Ultimate, and then more granular controls for Pro/Enterprise as a jump off from there? Can we streamline all the users access and controls?

Following this feedback issue could also be useful for identifying work ideas: #556038