10 results found
-
Folder/Organization System
I would like the ability to create folders within projects to organize our work. This would allow users to organize work by developer or by area of the site.
5 votes -
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 -
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.
3 votes -
Provide SRM monitoring on the results page
Hey!
As Team Lead Web Analytics I often see teams struggling to solve SRM issues.
It would be immensely helpful if the results interface would provide a graph depicting the user distribution between variants. This seems like a low-hanging fruit for Optimizely and would facilitate debugging SRMs strongly.
Thanks!
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 -
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 -
"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 -
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 -
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
.png){kind=link}
- Don't see your idea?