UX Transition for Variables
Context
This issue is dedicated to the seamless transition of UX and Design responsibilities for Variables in Pipeline execution
from @v_mishra to @nadia_sotnikova.
The designer currently assigned to the stage group is responsible for providing the relevant content for the newly assigned designer. However, it is encouraged to partner closely with Product Management, Design leadership, and stage group counterparts to provide the necessary information for a seamless transition.
☑ Tasks
The below tasks should be completed before finalizing the transition and closing this issue.
-
Update the title of the issue to: UX Transition for _ STAGE GROUP, GROUP, OR CATEGORY_
. -
Assign the transition issue to yourself and your Product Design Manager. -
Fill out the sections below with the relevant content for the stage, group, or category. -
Inform relevant Product Managers (PMs) and Engineering Managers (EMs) of the transition -
Communicate the change with the larger team on Slack. -
When the content is ready, assign the new designer to the issue, and @mention
relevant PM, EM, and Product Design Manager. -
Newly Assigned Designer: When you feel comfortable, unassign the previous designer and close this issue.
⌛ History and timeline
Timeline for the transition
Milestone | Description |
---|---|
14.00 |
The MR for moving the category Variables to pipeline Authoring has already been merged: gitlab-com/www-gitlab-com!82635 (merged) |
👓 Product vision
-
Feature label(to be moved): ci::variables
-
Jobs to be Done (JTBD) handbook page: PE JTBDs
-
Additional resources:
- Add resource: GitLab environment variables demystified
👷 Current and upcoming initiatives
Priority | Milestone | Current status | Issue/MR link | Design resource | Comments |
---|---|---|---|---|---|
High |
%14.0 | Closed |
UX scorecard | Dovetail | Pipeline execution team is responsible for completing this research |
High |
%14.1 | Closed |
Problem validation: Variables layout and UI polish Issues | Dovetail | Pipeline execution team is responsible for completing this Task |
Once completed, the findings and proposal would be shared with the ~"pipeline authoring" team.
Parked tasks
🗓 Meetings and rituals
None