TW group change tasks for Fulfillment/Purchase
Use this template to manage changes when there is a new stage/group, a deprecated stage/group, or when a group moves to a different stage.
- Stage/group change: ~"group::purchase" is being removed per gitlab-org/fulfillment/meta#1667 (closed)
- Stable counterpart technical writer(s) affected: @fneill
- Technical writing manager affected: @kpaizee
- Group change expected to be complete by:
16.10
Tasks for assigned technical writer
- In the
www-gitlab-com
repository:-
Check that an update for data/stages.yml
is in progress, and link the MR to this issue. A group or stage change is usually initiated by a Product Manager or Engineering Manager, who is responsible for following the process for Changes. It the PM or EM's responsibility to raise the MR to updatestages.yml
. -
Once the stages.yml
MR is merged, check that the changes are reflected in Assignments to DevOps Stages and Groups. The assignments table automatically pulls in the data fromstages.yml
. There should be no additional action required.
-
- In the
gitlab
repository, update as needed (in the following order, but can be done in the same MR):-
The metadata in all related markdown files. -
Group assignments in lib/tasks/gitlab/tw/codeowners.rake
. -
.gitlab/CODEOWNERS
by running thetw:codeowners
Rake task to ensure no pages are missed.
-
-
In the Technical Writing project, update the Milestone Planning template.
Tasks for technical writing manager
-
Update the queries on the TW Tableau dashboard. -
Update google sheets used for team rebalancing planning. -
N/A Check Workday for the Job Title Specialty (Multi-Select). If the specialty does not exist, create an issue in the People Group general project, and use the Workday: Job Title Specialty Request template. -
Update Workday with the new group assignments. Workday updates the group assignments in data/team_members/person
. Interim instructions during Workday rollout: Manager emailspeople-connect@gitlab.com
with details of changes.
Edited by Fiona Neill