56 results found
-
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 -
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 -
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 -
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 -
Results to Experiment Details Page Navigation Improvement
When you click on the Results button of a specific experiment, you want to be able to navigate from the results screen to the Experiment details page. Instead, currently, you have to go back to the main list of experiments, then find your specific experiment, to click into the details.
1 vote -
Versioning within an Experiment
A versioning capability within an experiment, so that when you are building, if someone makes unintended changes, they can revert back to the old version. There is interest in this feature both in the visual editor and for general changes in the experiment around page, audience, etc. These could be tackled separately.
1 vote -
custom content in ui
role: COE lead for experimentation
problem: lack of exposure to internal processes and standards and changes to them
outcome: i would like to be able to insert custom text into the UI at various points, including but not limited to:
* flag list
* create flag overlay
* flag page - ruleset list
* rule definition page
* audience list
* audience creation screen
* attribute list
* attribute creation screen
* event list
* event creation screen
* etc.basically anywhere you create, define, update and/or name things.
the intent is to provide content that descibes the current standards…
1 vote -
flag relationships
I manage platform use.
I am trying to make it easier for users to see all related flags that might be used for a single delivery.
I would like a way to list 'related flags' somewhere in the flag definition. there can be multiple flags related to multiple flags. one flag might have a few different relations. the relation list should be links to prod environment page for the defined related flag.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 -
List Flags With Rules, API Endpoint
This is a request to create a REST API endpoint that satisfies the following requirements.
A List Flags endpoint (to return all flags that returns both flags with rules (including variation names, and those with targeted delivery specifying which variation is enabled in the delivery.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 -
Enhance efficiency of UserProfileService with decideAll(
When calling decideAll( with a User Profile Service (UPS, the method looks up the UPS for each flag.
The request is that the SDKs be updated to default to just one lookup for all flags.
This will prevent unnecessary resource consumption for customers who utilize decideAll( method and also implement/rely upon a USP.1 vote -
Archive Notification for task Watchers
When a task is archived, a notification is sent to all watchers assigned to the task.
1 vote -
Apply Audience Automatically At The Project Level
As an experimenter I would like to be able to have an audience auto populate for an entire project. The bot filtering provided within Optimizely does not exclude additional bots that we need to remove from testing as an organization, and therefore we need to apply an additional audience to our tests to remove these bots from all test. Currently we have to do this manually for every test which allows for human error. But we would like to be able to auto populate this for all feature experiments within a project to avoid this step being forgotten.
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 -
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 "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 -
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
.png){kind=link}
- Don't see your idea?