Automatically open an issue to toggle off a feature flag once percent rollout hits 100%
Problem to solve
Users who use feature flags for gradual launches are using the percent rollout strategy. starting from a low percentage and increasing it until they reach 100%. Once a feature flag reaches 100% there is really no point to keep the flag in place. Many teams are creating issues to remind themselves to remove the flags and as a single toolchain - we could do this for them.
Intended users
Further details
An example of such an issue can be found here: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/1186
Proposal
Create a new setting under Operations Feature Flags that is similar to the one in incident response:
Action to take when feature flag is fully rolled out More information
Checkbox - Create an issue. Issues are created for each feature flag that is fully rolled out.
A user can define an issue template (optional)
Checkbox - Send a separate email notification to Developers.
Save Changes
Some users want to set a period for the flag to stay in production while at 100% - for example 30 days, so I am in a dilemma if a due date should be added to the issue based on a configurable variable of days (optional) - TBD
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
In the long run the number of feature flags should be reduced as automating the creation of these issues will catch more flags than creating this manually.
What is the type of buyer?
Is this a cross-stage feature?
This is a cross stage feature with devopsplan as this triggers opening a new issue
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.