4 results found
-
Visibility into flag usage
Depending on the number of teams operating in FX, tech debt accumulates quickly if not managed. Help customers determine how and when to consider tech debt in their FX endeavors.
Some customers struggle with outdated flags that have not been used in a while, but it is hard for them to determine which ones are outdated.
Help customers understand how their users are reacting to a new feature rollout.
6 votesFlag Statuses provides visibility into rules and rulesets throughout the flag lifecycle.
https://support.optimizely.com/hc/en-us/articles/43267083759885-Flag-statuses-in-Feature-Experimentation
Signup for the beta here: https://www.optimizely.com/beta-signup/?beta=Flag+Statuses+in+Feature+Experimentation
-
Introduce concept of Feature Flag Types
Almost none of my customers implement long-term flags. Every time they run a new experiment, they create a new flag, and remove it after. Even if they could have reused the flag for a new experiment a month later. This creates a lot of additional work.
1 voteCustom Fields can be configured to attach metadata on flags for organization purposes.
Signup for the beta here: https://www.optimizely.com/beta-signup/?beta=Custom+Fields+for+Feature+Experimentation
-
Product Feedback: Holdout Experiments
I'd like to measure the effectiveness of our experimentation program through a quarter-long holdout experiment. Is there an easy, self-serve method to set up holdout groups (say, 5% of traffic that would not receive any experiment treatments during the quarter, or do we need to manage this in code via a separate flag? Thanks!
2 votes -
Workflow approval
Clients wants to be able to have an approval workflow before a flag or test is started. They do this because they want to ensure that someone needs to get approval before changing the configuration of a flag to ensure a second pair of eyes before changes are made (similar to approving code changes.
4 votes
- Don't see your idea?