diff options
Diffstat (limited to '.gitlab/issue_templates/Experiment Successful Cleanup.md')
| -rw-r--r-- | .gitlab/issue_templates/Experiment Successful Cleanup.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Experiment Successful Cleanup.md b/.gitlab/issue_templates/Experiment Successful Cleanup.md index 1dd57332b8e..14a29452e49 100644 --- a/.gitlab/issue_templates/Experiment Successful Cleanup.md +++ b/.gitlab/issue_templates/Experiment Successful Cleanup.md @@ -11,6 +11,8 @@ The changes need to become an official part of the product. - [ ] 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. +- [ ] Determine whether there are other concerns that need to be considered before removing the feature flag. + - These are typically captured in the `Experiment Successful Cleanup Concerns` section of the rollout issue. - [ ] 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](https://docs.gitlab.com/ee/development/feature_flags) 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 |