Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.


We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

ADD FEEDBACK

Content Management

Showing 425 of 1912

Improve UI for a better editing experience on language settings and similar popups

While the updated CMS area in Optimizely 12 has improved in many ways, some parts of the UI have been changed in a way that makes editing more difficult. One such area is the language settings, where previously only languages that had settings ass...
6 months ago in Content Management / Editing 0

Add activity logging into Form Submissions for EpiServer Forms

As GDPR administrator i would like to know who was viewing, editing data that has been sent via EpiServer Forms. This is why all actions such: - display form submissions - download form submissions report - deleted submitted data in Form Submissio...
over 4 years ago in Content Management / Forms 0 Future consideration

Add an option to DXC for a NodeJS server in addition to an Episerver instance

I want to have a NodeJS server running on Azure, alongside my Episerver instance. To start, this would be a simple, naked NodeJS instance. I could do whatever I like with this. It would be deployable apart from the Episerver instance -- I could pu...
almost 5 years ago in Content Management / APIs / Technical 1 Investigating

Bypass approval sequence for admins

As an administrator I'd like to be able to publish content bypassing the approval sequence. Can there be a feature added to say which roles a particular approval sequence must follow?
over 4 years ago in Content Management / Collaboration & Approval 5 Future consideration

Enhance the Audience Feature to display the affected number of items

Audience groups should include the dependent items that use them, similar to blocks, this will give visibility to authors on all the effect areas where that personalization was used when a change is made
5 months ago in Content Management / Personalization 0

Adding multiple blocks under Personalization group

EPiServer.CMS version 12.22.7 When trying to add multiple blocks under one personalization group with the same visitorgroup, they can't be merged together as it is today. And when trying to do this as in the attached image, it is just the top item...
almost 2 years ago in Content Management / Personalization 1

Export Reports

As an admin I want to be able to export a report from the reports system So that I can distribute required updates to the broader author group. The outcome is the ability to complete an export of any report within the reports system
almost 5 years ago in Content Management / Reporting 0 Investigating

Search capability missing from select page or block dialog.

If site has thousands pages and blocks, it is very difficult to select correct page or block to link each other. Current you have to browse via tree to find correct content to create link or select block. Select page or content dialog should have ...
about 1 year ago in Content Management / Editing 0

Hide broken links on expired content from Link Status report

Currently, the Link Status report shows broken links that are present on expired pages. I would prefer it if broken links on expired content could be excluded from the report. This could be configurable. Jira ticket
over 4 years ago in Content Management / Technical 1 Future consideration

Improve user experience for editors when switching from one site to another

At the moment, when a logged in editor switches from one site (Site A) to another (Site B), where she/he has access to, the user is forced to re-log-in to Site B, and the entire CMS is re-loaded, which takes a long time. The current user experienc...
about 3 years ago in Content Management / Multi-site 0 Investigating