[Feature flag] Rollout of `design_management_copy_designs`
What
Remove the :design_management_copy_designs
feature flag added in !41714 (merged).
Owners
- Team: groupknowledge devopscreate
- Most appropriate slack channel to reach out to:
#g_create_knowledge
- Best individual to reach out to: @.luke
Expectations
What are we expecting to happen?
Designs to be moved when an issue is moved #13426 (closed).
What might happen if this goes wrong?
Worst-case would be the issue move feature is impacted.
What can we monitor to detect problems with this?
- Grafana
Projects::IssuesController#move.json
performance (latency in particular) - Sentry for any errors
- Grafana Sidekiq overview
- Grafana Sidekiq queue detail for
design_management_copy_design_collection_worker
Beta groups/projects
If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.
-
gitlab-org/gitlab
project
Roll Out Steps
-
Enable on staging -
Test on staging - [-]
Ensure that documentation has been updated(~bug) -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour -
Coordinate a time to enable the flag with #production
and#g_delivery
on slack. -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
-
Cross post chatops slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Edited by Luke Duncalfe