Skip to content

Feature Experimentation

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Custom Fields can be configured to attach metadata on flags for organization purposes.


    https://support.optimizely.com/hc/en-us/articles/42778979654669-Custom-fields-in-Feature-Experimentation


  3. In Flags, it is not possible to change the order of variants and have a different "Baseline" variation by default in the Results Page.
    Regardless the possible workaround (change the baseline variation from the results page, the proper behaviour would be to being able to switch the order of the variants (and so decide what the default "Baseline" variant is directly in the Flags Page.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  • Don't see your idea?