Experiment cleanup: Redirect in-app trial users to the feature that they requested the trial from
Summary
The experiment is currently rolled out to 100% of users and has been deemed a success. The changes need to become an official part of the product.
- Experiment rollout issue: #335824 (closed)
- Experiment engineering issue: #273634 (closed)
- feature flag name:
feature set redirect_trial_user_to_feature
Steps
-
Determine whether the feature should apply to SaaS and/or self-managed - SaaS only as self-managed has an entirely different trial experience
-
Determine whether the feature should apply to EE - and which tiers - and/or Core - free SaaS only as paid SaaS tiers currently cannont start a trial on their own in-app
-
Determine if tracking should be kept as is, removed, or modified. - Experiment specific tracking code can be removed
-
Ensure any relevant documentation has been updated. -
Consider changes to any feature_category:
introduced by the experiment if ownership is changing (PM for Growth and PM for the new category as DRIs) -
Check to see if the experiment introduced new design assets. Add them to the appropriate repos and document them if needed. -
Optional: Migrate experiment to a default enabled feature flag for one milestone and add a changelog. Converting to a feature flag can be skipped at the ICs discretion if risk is deemed low with consideration to both SaaS and (if applicable) self managed -
In the next milestone, remove the feature flag if applicable -
After the flag removal is deployed, clean up the feature/experiment feature flags by running chatops command in #production
channel -
Ensure the corresponding Experiment Rollout issue is updated
Edited by Alper Akgun