[Feature flag] Enable usage of GraphQL for roadmap
What
Remove the :roadmap_graphql
feature flag
Owners
- Team: Plan Portfolio Management
- Most appropriate slack channel to reach out to:
#g_plan
- Best individual to reach out to: @kushalpandya or @felipe_artur
Expectations
Epics roadmap will hit GraphQL to gather data and functionality should not change.
What might happen if this goes wrong?
Broken Roadmap with wrong number of epics. That could happen because we added a limit to GraphQL pagination.
What can we monitor to detect problems with this?
We can check for new errors on Sentry using https://sentry.gitlab.net/gitlab/gitlabcom/?query=graphql
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
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
and in your team channel -
Announce on the issue that the flag has been enabled -
Flag will be enabled after performance check. More information in #12887 (comment 274767312) -
Default the flag to on first -
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 -
Unblock #13758 and proceed merging !15731 (closed)
Edited by Felipe Artur