Skip to content

Experiment Tracking: upgrade_link_in_user_menu_a

Overview

Add an 'upgrade' option in the top right drop down (user settings menu) on GitLab.com

This is an experiment tracking issue for: product#843 (closed) using the scoped experiment labels.

As well as defining the experiment rollout and cleanup, this issue incorporates the relevant Feature Flag Roll Out steps.

Note this adds the Upgrade link, whereas #101 (closed) adds the user notification dot.

Owners

  • Team: group::expansion
  • Most appropriate slack channel to reach out to: #g_expansion
  • Best individual to reach out to: @timhey

Expectations

What are we expecting to happen?

Some users will see an Upgrade link in the user menu.

Caveat: you need a user who is not a member of any group (including personal namespace) already on Gold.

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Staging Test

To force this experiment on staging use ?force_experiment=upgrade_link_in_user_menu_a

See #159 (closed)

Rollout plan:

See product#843 (closed)

  • Runtime: TBD
  • We will roll this out behind a feature flag and expose this to 30% of users to start then ramp it up from there.
  • feature flag upgrade_link_in_user_menu_a (see experimentation.rb in gitlab)

/chatops run feature set upgrade_link_in_user_menu_a_experiment_percentage 30

  • 2020-07-01 - Enable for 30% of users
  • 2020-09-02 - Increase to 50% of users
  • 2020-10-13 - Review increase to 100%)
  • TBD - review in 2 weeks, consider removing feature flag / experiment code to make this part of the SaaS product

Beta groups/projects

  • ...
  • ...

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 behavior.
  • 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

Results:

Edited by Phil Calder