101 results found
-
Developer experience
I want Optimizely’s new developer experience to support a true IDE-first, GitHub-native workflow. I should be able to do all coding in my own IDE, manage changes through GitHub, and publish through automation and CI/CD workflows without depending on the Optimizely editor for core development tasks. The editor should support preview and collaboration, not replace standard developer tooling and deployment workflows.
1 vote -
I want Optimizely’s new developer experience to support a true IDE-first, GitHub-native workflow. I should be able to do all coding in my ow
Software Engineer
1 vote -
o Adding pagination to events to limit the number of events loaded at once.
Currently, loading the full list of events puts a significant load on the page.
The Events view becomes very slow, and in many cases it takes several minutes before the events finish loading.
Pagination (or lazy loading / load more) is needed to reduce the amount of data rendered at once and to improve usability.1 vote -
Opal UI - is Awful!!
Opal is very difficult to see -- there's no contrast between it and a page in reporting (or anywhere Opal appears)
Recommend giving her some color! See screenshots.
1 vote -
Bug Fix
Bug Fixes on text editor (mainly shared code)
Native find on page doesn't work reliably (sometimes shows more occurrences than there actually are, doesn't jump to the place in the code when you hit enter)
- Would be great to implement that properly
Starting typing at all makes the current line jump to the bottom of the screen, which is really frustrating and quite confusing.
- Ideally just keep the scroll position what it is when you start typing.
(I'm using Chrome on Mac OS)
1 vote -
Version control
A slightly better interface of what changes have been made before committing. I know you can view history, but it's not that easy to understand. Being able to see lines of code that have changed in each of the shared js, shared css and variations would be very helpful, rather than just the number of lines changed.
1 vote -
Create a dev only toggle that won't show the website preview
I am a developer who uses Optimizely for a lot of experimentation and have to spend a lot of the time inside of the code editor. The new editor creates way too much friction. I don't need my entire website to load and then inject optimizely's scripts. This cant take multiple seconds just to change one line of code.
I would much prefer it if we could have something like a toggle on our profile where we could choose to never show the preview and just show us the variation code in a code editor. I can always copy a…
8 votes -
New Visual Editor - Carry over click tracking from Lagacy Editor
Please make sure to carry over click tracking fucntionality from Lagacy Editor. This is a fundamental function in the current legacy editor and the old legacy editor should not be phased out until this function is added to new editor
5 votes -
New Editor
Hello I have been using Optimizely for over 5 years and greatly enjoyed the product. The new editor that is slated to be fully launched greatly complicates my workflow. Most of the coding and edits I do in this editor I have to use an external editor to write and then copy them into the new Optimizely editor because of the layout and bugs in this new experience.
Here are some of the bugs I have noticed while using the new layout:
-the preview screen the editor is overlayed on distorts the elements and hides the element being edited behind…2 votes -
The new editor
I'm a developer who uses Optimizely for many personalizations and A/B tests, and I've noticed the new UI for the editor. I just want to say I hate it.
It's absolutely horrendous. It takes several minutes to load. And, when it finally loads, it doesn't always work. Even when it does work, the editor is tiny. While it is nice to be able to see what I'm working on reflect on the page after I save, the tiny editor just ruins it because it's not great for long lines of code. I don't want to try to read through 200…
20 votes -
results page versions
AS An
experiment analystI WANT TO
save the settings of the results page including start/end time, segments, etc... and have it accessible via share link and also as a link displayed on left sideSO THAT
i can share detailed and specific findings with others easily and return to the ones i've created easily.1 vote -
Block Publish When Experiment Uses Archived Event or Metric
We found an experiment can be published even though it referenced an archived event.
Request:
Please add pre-publish guardrails so experiments cannot be published when they reference archived component dependencies.
Expected behavior:
- Block publish if any linked event, metric, or required page dependency is archived
- Show a clear warning with the archived item names
- Provide direct links to fix or replace each archived dependency before publishThis would prevent avoidable debugging and protect experiment data quality.
1 vote -
results display improvements
AS A
experiment creator and reviewerI WANT TO
improve the results page by increasing the context available for visitors that get to the page from a shared results link and may lack context into what the actual experiment is.
1. upload an image of the control and variant to the results section/page per variation or re-use the upload in variations list.
2. include hypothesis - could be input as part of the metrics screen
3. include notes - could be input as part of the metrics input. should allow inclusion of links so that references to other documentation -…1 vote -
stand-alone image upload
AS AN
experiment builder that utilizes the code editor 95% of the timeI WOULD LIKE TO
be able to upload images that are used in the variant without having to create a change in the editor to access the image uploaderSO THAT
my build process makes more sense and I don't create an unecessary change that I then have to delete after I upload the image and get the URI.1 vote -
hiding early results
AS AN
experimentation governance and operations managerI WOULD LIKE TO
be able to 'hide results' for a time by experiment to avoid devs and partners reviewing an experiment and disseminating detailed results before we have anything near conclusive. Having a project wide settable baseline would be good along with the ability to manage it at the experiment layer. Base layer should still be displayed such as visitors, split percentages, SRM, etc... Conversion rates and success metrics should not be shown until the hide time has passed. Admins should always see all metrics.SO THAT
I can avoid negatively impacting…1 vote -
Duplicate Pages
I want to have the ability to duplicate a page. Often times the page configuration is similar, for example when creating pages across environments. However, because Page duplication is not possible this causes a lot of additional work by setting up pages from scratch.
6 votes -
Adjustment of permissions for users without publishing rights
Enable publishing with a test cookie / audience as priority. The Editor role should inherit all Publisher permissions except standard publishing, but should be able to publish when a specific audience/test cookie is applied.
Enable restoring experiments from the archive.
Allow setting experiment end dates.
Provide permissions to edit Pages.
1 vote -
Enhance Search Functionality
Currently, its capabilities are limited in two main areas:
Query Handling: The search processes only the first word of a multi-word query. For instance, a search for “Headers for PDP” will only return results matching “Headers.”
String Matching: The search requires a complete word match and does not return results for partial strings. For example, searching for “experi” will not find items containing the word “experiment.”
These factors reduce the discoverability of specific experiments, particularly in projects with a large volume of tests which is causing friction and frustration.1 vote -
Request to Extend Session Timeout
Kaufland has raised concerns about the current session timeout behaviour in the app. Users are automatically signed out after 30 minutes of inactivity, which results in them having to log in multiple times throughout the day. This is causing frustration and negatively impacting the user experience.
Kaufland would like the option to increase the session timeout window, or make it configurable, so users can remain logged in for longer periods without interruptions.
1 vote -
Missing preview url in new visual editor
The "share preview" is missing in the new editor. Once the old VE is retired, how do we share the changes with other team members for review?
5 votes
- Don't see your idea?