13 results found
-
"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 -
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.
2 votes -
Audience integrations
To enable FX personalization, be able to pull audiences from other tools.
2 votes -
Built-in attributes for frontend/client SDKs
Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.
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 -
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 -
Observability/guardrail metrics
Help customers understand how flags/experiments are affecting site performance.
1 vote
- Don't see your idea?