Fulfillment Section Rollout
Description
Fulfillment is moving to its own section with gitlab-com/www-gitlab-com!62755 (merged) and I'm unsure of the implications we need to consider
Tasks
-
Create sectionfulfillment, devopsfulfillment, ~"group::purchase", groupprovision, Category:Purchase, and ~"Category:Provision" gitlab-org
group labels -
Consider changes to the Embedded Team Dashboard for UX and Quality -
Update group-definition.yml
and generate corresponding policies and jobs => !643 (merged)
!639 (closed)
Migration =>-
Rename ~"group::fulfillment" to devopsfulfillment -
Migrate current devopsfulfillment + frontend issues/MRs to sectionfulfillment + ~"group::purchase" - sectiongrowth - devopsgrowth in gitlab-org/gitlab
: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/769726383- Expected updates: 78 issues, 100 MRs
-
[To be confirmed] Migrate current devopsfulfillment issues/MRs to sectionfulfillment + groupprovision - sectiongrowth - devopsgrowth in gitlab-org/customers-gitlab-com
: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/769726383- Expected updates: 1782 issues, 1775 MRs
-
Migrate current devopsfulfillment issues/MRs to sectionfulfillment + groupprovision - sectiongrowth - devopsgrowth in gitlab-org/license-gitlab-com
: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/769726387- Expected updates: 110 issues, 76 MRs
Potential migration
-
Migrate ~"Category:Billing" 794 issues, 65 MRs, and 14 epics to Category:Purchase / ~"Category:Provision"?
Edited by Rémy Coutable