[Lens][Dashboard] Merge visualization and panel settings

[drewdaemon]

Describe the feature:
Lens panels on a dashboard currently have two actions for customizing the appearance of the panel, both of which open a flyout

• Edit visualization
• Panel settings

These experiences could be merged so that users have a one-stop-shop for all settings related to panel appearance. There are technical and ownership reasons for the way it is set up now. However, I can't see any user-facing reason to keep them separate.

Merging the two would simplify the context menu require fewer clicks (and mis-clicks) while customizing Lens dashboard panels.

It might make sense to delay this task until more panel types support inline editing.

Screenshots

the actions

panel settings

visualization settings

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[stratoula]

Although this is something we would like to do in the future I don't think we should do it now for 3 reasons:

• Inline editing is still under progress and we haven't finalized yet the features we want to add
• Inline editing is a Lens only feature so it will be confusing to have this action to some panels while the Lens panels will include it inside the editing experience.
• Inline editing is about Lens attributes while panel settings is about dashboard settings. They don't make sense outside a dashboard so contextually I would like to think it more.

[ThomThomson]

@stratoula, I agree with your assessment. Additionally, we're currently in the middle of the major Embeddable refactor, which would preclude us from working on this any time soon.

Also bumping the impact up to medium because as a user, the separation of these settings doesn't make sense.

[Heenawter]

Noting here that, in user testing for the Links panel (which also has an inline/flyout editing experience), we saw quite a bit of confusion around where different settings lived - it made no sense, from a user perspective, why "Panel settings" were different from the Link-panel-specific creation experience. I assume the same kinds of issues will surface with Lens now that inline editing is available...

In an ideal world, the "Panel settings" flyout should be removed for all non-legacy panel types - we're definitely far from that goal, but I can dream 🙈

[stratoula]

There is an important distinction between the Lens SOs and the links panel. Lens charts have an editor where they are created, they are not dashboard elements. They have their own names and descriptions. The panel settings overwrite them (which is already very confusing).

So expect from the tech work that needs to be done and the fact that we need a feature parity in dashboard before we do that, we also need to fix the confusion between visualizations names/descriptions and panel names/descriptions. If we don't find a solution for that, moving the panel settings inside the visualization editing will be a big confusion, creating more problems than solving.

[MichaelMarcialis]

The latest design mockups for this issue have been crafted and are ready for handoff to engineering. Some key screenshots from the mockups can be found below. Please view the full Figma document for all mockups and developer notes.

---