Skip to content
← Turn your feedback into functionality

Feature Experimentation

Feature Experimentation

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Welcome! 👋

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

6 results found

  1. Setting significance on experiment level

    We are supporting over 25 teams running experiments, running close to 500 experiments per year. The requirements regarding significance level differ strongly from team to team - sometimes even from experiment to experiment.

    It would help us a lot if we could set significance level for each experiment explicitely.

    We also think this is a low-hanging fruit since we can see from API calls that significance level is actually a variable that already exists per experiment. Also - as results are calculated every time I view the results page, this appears to be possible to implement without too much difficulty?

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. JIRA Integration for Feature Flags

    Unfortunately, in the new Flags UI the JIRA Integration is no longer available (as it is not yet migrated). My Idea Post is about requesting its availability.

    In our Company we have a very close relationship between JIRA Tickets + Experiment Rules (1:1). That's why, this integration is/was helpful to relate Code/Work accordingly.

    Many thanks in advance
    Michael

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Remove unused experiments from user profile service

    Currently, user profile service (UPS) maintains a map of user IDs to the experiment IDs they've previously been exposed to and the variation ID they received. The SDKs continuously append to the UPS without any cleanup, even if an experiment has been concluded and is no longer relevant.

    Customers have in the past implemented diff logic to compare the live experiment IDs in the datafile vs UPS and remove experiment IDs from the UPS that are no longer in the datafile.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Built-in attributes for frontend/client SDKs

    Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Datafile Relay Proxy

    If Optimizely's CDN goes down or is inaccessible, the SDKs don't have a default fallback mechanism to evaluate feature flags without access to the datafile hosted on the CDN.

    It's possible to initialize the SDK with a cached datafile, but that requires custom logic. Ideally, Optimizely could provide a default mechanism to provide a fallback datafile (e.g., a "relay proxy" service that caches the datafile, or a default mechanism within the SDKs).

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. OpenFeature SDK Support

    Make SDKs compatible with OpenFeature standard.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?