Embed cookie feature/canary toggle in product
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Setting the cookie for canary is not entirely an obvious process for either GitLab.com or self-managed installations. Providing an in-product equivalent to next.gitlab.com (https://gitlab.com/gitlab-org/gitlab-ce/issues/58222) would let us build this capability directly in the product, and would provide a foundation not just for choosing binary canary on or off, but perhaps even per-feature toggles on a user basis.
Target audience
This does not directly align to our personas since it impacts the general persona of users trying out new features within GitLab.
Further details
In product discussions we frequently wish for the ability to allow certain users to have access to frontend features before they are ready for prime time. Having a "beta channel" for users to access features they are interested in can provide a feedback mechanism as well as give them access to features they are excited about.
Note that since this is a cookie-based method, this does not offer the ability to grant access to backend features. But still, having this for the frontend is a win.
Proposal
Bring https://gitlab.com/gitlab-org/gitlab-ce/issues/58222 into the product.
Permissions and Security
Since this feature sets per-user toggles, it does not require a change in the permission model for users. Some administrators of instances, though, may wish to disallow setting beta features on or off in their instance.
Documentation
TBD
What does success look like, and how can we measure that?
+beta feature usage and feedback
Links / references
cc @jeremy