Experience Recommendations - Verify:Pipeline Authoring FY25-Q2

• UX Scorecard Part 1: #2578 (closed)
• Resulting Recommendations:

  Issue	Type	Status	Description
  Catalog breadcrumb does not lead users to the i... (gitlab#472190 - closed) • Anna Vovchenko • 18.3	typebug	workflowcomplete	Catalog details page, bug
  Frontend: Set the components tab as the default... (gitlab#472631 - closed) • Briley Sandlin • 17.3	typemaintenance	workflowcomplete	Catalog details page, UX improvement
  Design: Explore dynamic snippets options in the... (gitlab#473027) • Unassigned • Backlog	typemaintenance	workflowready for design	Catalog details page, UX improvement
  Design: Add a link to the template/component re... (gitlab#473028) • Unassigned • Backlog	typemaintenance	workflowready for design	Catalog details page, UX improvement
  Spike: Explore alternative ways to make a relea... (gitlab#463253) • Furkan Ayhan • Backlog	typefeature	workflowproblem validation	Better UX in the release process
  Frontend: Add an indicator if the release goes ... (gitlab#438958 - closed) • Briley Sandlin • 17.6	typemaintenance	workflowcomplete	Better UX in the release process
  Frontend: Add a modal to specify project descri... (gitlab#434366) • Unassigned • Backlog	typemaintenance	workflowplanning breakdown	Better UX in the creation process
  Backend: Create project template for CI components (gitlab#399199 - closed) • Philipp Hahn • 18.0 • On track	typefeature	workflowcomplete	Better UX in the creation process
  Frontend: Update the catalog icon in the pipeli... (gitlab#473043 - closed) • Sunjung Park • 17.3	typemaintenance	workflowcomplete	Better UX in the onboarding process

Experience Recommendations Checklist

Learn more about UX Scorecards

1. Add this issue to the stage group epic for the corresponding quarter's UX scorecards.
2. 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.
3. Create an issue for each recommendation using one of the Actionable Insight templates in the GitLab project, depending on if it relates to a product change or needs more exploration. 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. To help with prioritization, add a severity label to communicate appropriate urgency and impact to the experience. Link to the epic or issues here.
   • Recommendations do not need to be documented in your Dovetail project.
4. 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.