20 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.
4 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
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 -
Filter metrics by linked 'event'
In the overview page of metrics hub, I would like to filter by linked event. So I can see all the existing metrics linked to a specific event. Currently it's only possible to filter by metrics name, id or description.
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 -
Triggering tests
It is sometimes hard to trigger a test variant when deeper into a flow. Could a bookmark be created to easily trigger a test on any given page?
1 vote -
How long to get statistical significance
When the platform says another 50k users to reach significance, could a date be added? E.g. it has taken 3 weeks to get to 25k so give the date in 3 weeks as the date when the 50k will be reached
1 vote -
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.
1 vote -
Audience integrations
To enable FX personalization, be able to pull audiences from other tools.
2 votes -
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 -
Observability/guardrail metrics
Help customers understand how flags/experiments are affecting site performance.
1 vote -
Use Custom Event Properties for ratio metrics
Hello!
We very much appreciate the arrival of ratio metrics. However, they do provide limited value to us as long as Custom Event properties are not usable for either numerator or denominator.
It would be awesome to see that added.
Role: I am the Team Lead for our experimentation center-of-excellence and infra team.
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 -
OpenFeature SDK Support
Make SDKs compatible with OpenFeature standard.
1 vote -
Event Inspector/Debugger
Ability for developers to enable an event inspector to ensure instrumentation is working correctly
1 vote -
Dependent flags
Be able to trigger flags if certain actions happen, or make flags dependent on other flags. Both stateless and stateful approaches.
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 -
Custom Fields/Tags
It's hard to manage flags/tests at scale without being able to group them and capture more metadata on them.
1 vote
.png){kind=link}
- Don't see your idea?