You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to enhance the integration of Experiments in the new Visual Editor. Some things like:
Right now we don't have any hint for draft/scheduled experiments
The badge for running experiments will probably change after UI/UX review
We don't have a way to go back to Experiments or Default Variant after opening a Variant in the Visual Editor
We don't have a way to hint the users that they are editing or viewing a Variant
Experiments is not enabled in the Headless version of the Visual Editor. This means we should create states for our navigation bar to hint the user about this.
Right now we can edit variants while an experiment is scheduled. This shouldn't happen
Proposed Objective
User Experience
Proposed Priority
Priority 2 - Important
Acceptance Criteria
Experiments should be visually integrated to the Visual Editor.
We shouldn't be able to edit variants when an experiment is running or is scheduled to run.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Pending design
I will share figma files when I have it.
Assumptions & Initiation Needs
Experiments is already running and stable in the new Visual Editor
Quality Assurance Notes & Workarounds
No notes or Workarounds at the moment.
Sub-Tasks & Estimates
No Sub tasks.
The text was updated successfully, but these errors were encountered:
Parent Issue
#27546
Task
We need to enhance the integration of Experiments in the new Visual Editor. Some things like:
Proposed Objective
User Experience
Proposed Priority
Priority 2 - Important
Acceptance Criteria
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Pending design
I will share figma files when I have it.
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
No notes or Workarounds at the moment.
Sub-Tasks & Estimates
No Sub tasks.
The text was updated successfully, but these errors were encountered: