54 results found
-
Display bucketing ranges in the GUI (when changing traffic allocation)
I know that Optimizely tries to keep bucketing consistent when traffic allocation and or distribution changes.
It would be great to be able to see the bucketing allocation (eg. 1-5000 for A, 5001-10000 for B) in the interface.
In this example it is simple, but when ramping up (and possibly at the same time changing the distribution of traffic) it would be great to be able to verify via the interface which buckets are being set.
I am aware of Customer Profile Service but I see this as independent from that.1 vote -
more prominent/named link to flag/rule definition from results
As a member of a center of excellence,
I would like to see a prominent link to the rule configuration in the results page
So I don't have to explain to users all the time the most efficient manner to get back to the rule. This will decrease user frustration when trying to understand what metrics definitions are.
Most users have not figured out that the environment link takes you back to the rule itself.
1 vote -
IP Filtering
IP filtering lets you exclude certain IP ranges from showing up in your experiment results. This is also how you can exclude yourself or your company from experiment results. - https://support.optimizely.com/hc/en-us/articles/4410283982989-IP-Filtering-Exclude-IP-addresses-or-ranges-from-your-results
This is currently available in Web Experimentation but not in Feature Experimentation.
Internal stakeholders and engineers are regularly forcing themselves into experiments to demo and debug, and this will be impacting our results. We would like to be able to exclude these
1 vote -
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
Michael2 votes -
"Status Last Changed" Field
Add a "status changed" date to the FX Flags overview page. Because currently, there is a "created" and "modified" column. However, "Modified" refers to any changes, and there is no easy way to see when a status was changed, so when a rule was changed to its current state (started/paused/concluded)... it would be valuable information for the customer just within the FX UI.
Additional context: https://jira.sso.episerver.net/browse/DHK-2914?focusedId=2087943&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2087943
4 votes -
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 -
Changing the State of a Feature Flag in Draft Status Should Notify User that Flag is Not Yet in Running State
If a flag status is Draft and a user attempts to change the value of that flag, the UI should notify the user that they are changing a flag that is not yet in Running state.
This will prevent cases where someone thinks they have changed a flag state, but as far as the system is concerned, they have not.
1 vote -
Disable losing variant(s) during experiment
As of now, in Feature Experimentation, if a variant performs (very) bad, there is no way to deactivate it or set its behavior back to baseline without needing to create a new rule.
This of course slows down experimentation speed.
I do understand that the results of that variant are not usable after setting a variant's behavior back to baseline behavior. However, that is not the issue. The goal is to simply be able to continue letting the test run while disabling a bad-performing variant.1 vote -
Audience integrations
To enable FX personalization, be able to pull audiences from other tools.
3 votes -
Built-in attributes for frontend/client SDKs
Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.
3 votes -
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 -
Introduction of filters
It would be great to have some kind of filters that allow a deeper dive into data. So if we wanted to see how many people bought a licence AFTER triggering a specified conversion
1 vote -
Flag Triggers/Kill Switches
Make change to flag (e.g., toggle on/off) based on event from external system (e.g., APM alert).
2 votes -
Dependent flags
Be able to trigger flags if certain actions happen, or make flags dependent on other flags. Both stateless and stateful approaches.
2 votes -
Observability/guardrail metrics
Help customers understand how flags/experiments are affecting site performance.
1 vote -
Events integrations
Customers want to have metrics they track in their analytics in Optimizely. Today they have to manually add new event instrumentation. Would be great to integrate with other analytics and import their event tracking in Optimizely (ie. similar to Segment integration)
1 vote -
Environment Filter for Webooks
Filter activity notifications via webhook to only production environment.
1 vote -
Event Inspector/Debugger
Ability for developers to enable an event inspector to ensure instrumentation is working correctly
1 vote -
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 vote -
Add Rule and Variation IDs to Decision Object
Currently, the decision object returned by an SDK's decide method includes the flag, rule, and variation keys that a user was bucketed into but does not return the (experiment rule and variation key that the user was bucketed into.
2 votes
- Don't see your idea?