Use this epic, and linked sub-epics, issues and boards, to plan and complete Q3 UX OKR work for Plan. ## UX Scorecards Plan and complete Q3 UX OKR, Plan work for [Move 50% of UX Scorecard scores up a grade level](https://gitlab.com/groups/gitlab-org/-/epics/1676) * [ ] **12.5** - [Q3 UX OKR, Plan: Understand Dependencies Score](https://gitlab.com/groups/gitlab-org/-/epics/1719) * [ ] **12.5** - [Q3 UX OKR, Plan: Todos and Issues](https://gitlab.com/groups/gitlab-org/-/epics/1749) * As [per @annabeldunstone](https://gitlab.com/groups/gitlab-org/-/epics/1720#note_209847725), we are not moving forward with the JTBD for the Q3 OKR. * [ ] **12.5** - [Recently used labels](https://gitlab.com/gitlab-org/gitlab/issues/30619) * Moved forward with using a text label instead if an icon for recent searches- https://gitlab.com/gitlab-org/gitlab/issues/30619#note_232494053 We can track work in the linked UX Scorecard epics. ## Validation Issues Plan and complete Q3 UX OKR, Plan work for [20 UX team validation Issues](https://gitlab.com/groups/gitlab-org/-/epics/1675) * [x] **12.3** - [Labels in issue boards](https://gitlab.com/gitlab-org/ux-research/issues/267) * [ ] **12.3** - [Issue list re-design proposal validation](https://gitlab.com/gitlab-org/ux-research/issues/317) * [ ] **12.4** - [Baseline experience and expectations on To-Dos](https://gitlab.com/gitlab-org/ux-research/issues/312) * [ ] **12.4** - [How Teams Organize and Track Sprints and Releases ](https://gitlab.com/gitlab-org/ux-research/issues/306) * [ ] **12.4** - [Assessing the usability of Epics. Evaluating proposals to improve Epics.](https://gitlab.com/gitlab-org/ux-research/issues/228) * [ ] **12.5** - V6 * [ ] **12.5** - V7 We can track work with this board: * [UX Management Dev](https://gitlab.com/groups/gitlab-org/-/boards/1241198?milestone_title=%23upcoming&&label_name[]=problem%20validation) (filter via `Solution Validation` and `Problem Validation` labels) ## Pajamas Components Plan and complete Q3 UX OKR, Plan work for [Pajamas to Vue Components](https://gitlab.com/groups/gitlab-org/-/epics/1677) Turn remaining `##` foundational UI components into single-source-of-truth components that are implemented in Vue and thoroughly documented on design.gitlab.com. * [ ] **On Track** - Component Name (link to corresponding [Pajama Sub-epic](https://gitlab.com/groups/gitlab-org/-/epics/973)) * [x] **Complete** - [Labels](https://gitlab.com/groups/gitlab-org/-/epics/1014) * [ ] **On Track** - [Dropdowns](https://gitlab.com/groups/gitlab-org/-/epics/1018) * [ ] **On Track** - [Forms](https://gitlab.com/groups/gitlab-org/-/epics/1021) * [x] **Complete** - [Tokens](https://gitlab.com/groups/gitlab-org/-/epics/1123) We can track work via [Pajama sub-epics](https://gitlab.com/groups/gitlab-org/-/epics/973) and these boards: * [Pajamas Board](https://gitlab.com/groups/gitlab-org/-/boards/1024944?&label_name[]=Pajamas) * [UX Management Dev Board](https://gitlab.com/groups/gitlab-org/-/boards/1241198?milestone_title=%23upcoming&&label_name[]=problem%20validation) (filter via Pajamas labels) * [Pajamas Progress Spreadsheet](https://docs.google.com/spreadsheets/d/1lvmyXIRDMeR2iUqCr9UqNyFSKi4E0kCattXibfdluXM/edit#gid=1817586819) @annabeldunstone @uhlexsis @hollyreynolds