UX Scorecard: Obtain an overall understanding of job executors at a glance so that I can make effective decisions - Recommendations
- UX Scorecard Part 1: #1666 (closed)
✨ Recommendation issues or existing issues that cover recommendations
- Improve filtering by allowing to filter by more attributes - gitlab#339493 (closed)
- Improve the clarity and consistency of
types
of runners gitlab#233972 (closed) - Improve empty state of filter (something to use Pajamas for) gitlab#339494 (closed)
- Improve empty state of the runners table gitlab#339504 (closed)
- Make the runner view from Settings > CI/CD > Runners more consistent with Admin > Runners gitlab#339521 (closed)
- Add a way to determine how many versions your runner is behind and an action to update & Add inline docs around the current version of Runners to provide context around updating gitlab#339523 (closed)
- Allow for bulk actions (deletion) gitlab#339525 (closed)
- Consider consolidating the ways you can edit runners today (clicking on name vs clicking on pencil does the same thing) gitlab#299758 (closed)
- Provide a status breakdown of runners in view at a glance & Improve the consistency of statuses presented in the Admin view and Group/Project views gitlab#339527 (closed)
- Improve feedback on actions being taken (ex. confirmation after deletion) gitlab#339653 (closed)
- Update pagination to use pagination basic and add a total runners number gitlab#339655 (closed)
Experience Recommendations Checklist
Learn more about UX Scorecards
-
Add this issue to the stage group epic for the corresponding quarter's UX scorecards. -
Brainstorm opportunities to fix or improve areas of the experience. - Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first.
-
Create an issue for each recommendation. Alternatively, you can create a separate epic to hold all your recommendations. Add a UX scorecard-rec
label to every issue or epic for traceability. Link to the epic or issues here. -
Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release. - If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.
Edited by Gina Doyle