Convert `soft_email_confirmation` FF to an application setting
Summary
The experiment is has been determined experimentinvalidated/failed.
However due to possible self-managed use and documentation(see #371638 (comment 1093036084)) we will be keeping this functionality, but changing it to an application setting.
Steps
-
Add application setting with UI to control -
Try to carry over possible self-managed instance settings that may have the feature flag set to true (not sure how this would work yet). This may require this issue to span 2 milestones - one to add in the new code, capture the current setting of the feature flag and apply it to the application setting, and then the next to remove the feature flag and any 'migration' best effort code to carry over the feature flag setting -
Determine whether the feature should apply to SaaS and/or self-managed -
Determine whether the feature should apply to EE - and which tiers - and/or Core -
Determine if tracking should be kept as is, removed, or modified. -
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 Roy Liu