UX Scorecard - Verify: Pipeline Security FY24-Q4 - Recommendations for store and access reusable variables
- UX Scorecard Part 1: UX Scorecard - Verify: Pipeline Security FY24-Q... (#2443)
- Resulting Recommendations: Recommendations epic
# | Insight / Finding | Recommendation | Stage |
---|---|---|---|
1 | The Variables feature is hard to find | Improve the discoverability and access points of the variables feature | Look for variables |
2 | Ambiguity in terminology and descriptions | Actionable Insight for Docs: More CI variable examples | Add variables |
3 | Opportunities for improving input validation | Refine variable value input validation approach | Add variables |
4 | Users can’t tell if a branch is protected or not |
Indicate whether a branch is protected or not in branch selector |
Run a pipeline |
5 | We don't provide suggestions for available variables | Design: Surface the available variables when adding variables to job and pipeline runs | Run a pipeline |
6 | Job log uses text and colour to convey job status | Enhance accessibility and inclusiveness in job log | View job log |
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 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.
-
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 Bonnie Tsang