Roll out boards_with_swimlanes feature flag
What
Remove the :boards_with_swimlanes
feature flag
Owners
- Team: Plan
- Most appropriate slack channel to reach out to:
#s_plan
- Best individual to reach out to: fguibert, cablett, jprovaznik
Expectations
What are we expecting to happen?
Swimlane view is enabled in UI, grouping of board issues by epics is available in GraphQL API
What might happen if this goes wrong?
On BE side, the query to group issues by epics is potentially more expensive, so the query might be slower. Not aware of potential threats, please add others if you there are other related MRs to this feature.
What can we monitor to detect problems with this?
You would notice slow graphql requests to get board's epics
field.
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.
- https://gitlab.com/tech-marketing/demos/gitlab-agile-demo/large-co/sector-alpha/lob-1/app-a
- gitlab-org in second phase
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
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 Florie Guibert