Experience Recommendations - Verify:Pipeline Authoring FY21Q3 - Pipeline authoring experience

  • UX Scorecard Part 1: #1376 (closed)
  • Resulting Recommendations: {{when ready, add a link to your recommendations epic}}

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. 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.
  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.

Recommendations

  • Make the CI feature more discoverable, for example recommend it to maintainers of a project. gitlab#280828 (closed)
  • Explore ways to make the distinction between DevOps and CI/CD more clear and explore ways to align the user experience. gitlab#280572
  • Provide more guidance on how to set up CI, what are the steps, what are the requirements gitlab#269755 (closed), gitlab#272557 (closed)
  • Provide at least a basic template to start with, as opposed to a blank page gitlab#269755 (closed)
  • Provide more context about the templates, make them easier to browse, search, and preview, communicate the value of each template gitlab#267009 (closed) gitlab#259675 (closed) gitlab#28049 (closed)
  • Make relevant documentation accessible from within the UI gitlab#273203 (closed)
  • Make it easier to understand whether a runner is set up, and if not, how to set it up, and what are the options available
  • Provide recommendations on how a template may need to be customized for any given project
  • Provide immediate pipeline status feedback once CI configuration has been saved gitlab#280829 (closed)
  • Make it easier to see the pipeline progress and job logs from the editor page gitlab#280829 (closed)
  • Make a link to the deployed application easily discoverable
Edited by Nadia Sotnikova