56 results found
-
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.
2 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 -
Audience integrations
To enable FX personalization, be able to pull audiences from other tools.
3 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 -
Built-in attributes for frontend/client SDKs
Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.
3 votes -
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 -
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.
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.
3 votes -
Observability/guardrail metrics
Help customers understand how flags/experiments are affecting site performance.
1 vote -
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.
5 votes -
Ability to Redesignate the Primary Environment in Feature Experimentation
A customer has requested the ability to change the primary environment in Feature Experimentation after the initial project setup. Currently, the primary environment is automatically assigned and cannot be modified, which has led to ongoing frustration for their team.
They would like the ability to:
* Reassign the primary environment to another existing environment within the project.
* Make this change via the UI or API with appropriate safeguards (e.g., confirmation prompts, permissions.1 vote -
Feature to create flags template that can be used in creating custom flag
Summary:
This feature request proposes the ability to create flag templates that can be used as a foundation for generating custom flags. Templates would streamline the flag creation process, ensuring consistency and saving time when generating multiple similar flags.
Use Case:
Currently, creating flags often requires starting from scratch . This is both time-consuming and prone to errors. By introducing customizable templates, users could:
* Define reusable structures for flags, including predefined attributes and settings.
* Quickly apply these templates to generate custom flags with minimal effort.
* Maintain consistency in flag configuration across projects or teams.
Benefits:
* Efficiency:…1 vote -
Add "name" field to FeatureFlag object in datafile
I would like to ask if it's possible to add a "name" field to the FeatureFlag object in in datafiles/xxxxx.json which is having all the configured feature flags there.
To give some more context on the structure I'm talking about:
{
...
"featureFlags": [
{
"id": "123456",
"key": "experiment_key",
-> "name": "Experiment name", <- NEW FIELD HERE
"rolloutId": "rollout-1233456",
"experimentIds": [],
"variables": []
}
...
],
...
}
New "name" field would be having a value of the name of the related flag.
I'm guessing it could be not available there by default because of privacy/security reasons, but if that's…1 vote -
Add "rule type" property to decision object
While the decision object returned from the SDK currently provides the flag status, variation key, and rule key, there is currently no built-in way to determine whether the rule that returned the decision was an A/B test or targeted delivery. A workaround would be to use specific naming conventions for different rule types, but it would be useful to have this information baked into the decision object by default.
1 vote -
Add rule type property to decision object
While the decision object allows you to see which rule delivered a feature, it does not specify whether this rule is an A/B Test, Targeted Delivery, etc.
Customer naming conventions could theoretically provide this kind of context, but we've received a request from Nike to make this available in the SDK itself.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.
1 vote
.png){kind=link}
- Don't see your idea?