search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.48k stars 8.04k forks source link

[Dashboards] Users may be missing out on "Explore in Discover" because they stay in Edit mode #185893

Open alexmarhaba opened 3 weeks ago

alexmarhaba commented 3 weeks ago

Describe the feature: Some users are unaware of "Explore in Discover" option because in Edit mode, it is hidden under "More options". We recommend showing "Explore in Discover" in the primary options menu of a visualization when in Edit mode.

More context: During a user interview with a developer, the user showed how he often explores data in Discover while creating or editing his visualizations in Dashboards by manually copy pasting filters in Discover. He was unaware of the "Explore in Discover" option in the visualization's menu in Dashboards.

Current options menu in edit mode: image

Current options menu in view mode: image

elasticmachine commented 3 weeks ago

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

Heenawter commented 3 weeks ago

Agreed on bringing the "Explore in Discover" action to the top of the menu in edit mode! I think the question becomes... which action are we specifically talking about here?

Basically, there is more than one "Explore in Discover"-esque action... Here's just two of them, although I believe there is more depending on various settings + which panel type you are looking at.... (Possibly even an observability-specific action? Hmmm...)

Screenshot Owner
image Visualizations
image Data Discovery (when the exploreDataInChart setting is enabled)
image Data Discovery (specifically only for saved searches)

If we only care about Lens panels, bringing this to the top of the menu in edit mode should be pretty straightforward - but I wonder if this would make the duplication / inconsistency on other panel types more apparent? I wonder if, instead, it would be better to unify all of the "Explore in Discover"-esque actions as part of this effort so that the location + behaviour is consistent across all panel types?

This would definitely add some complexity, so... do we think this is worth doing? Or should we just prioritize bringing the Lens-specific "Explore in Discover" action to the top (despite the fact that it would add inconsistency to the panel menu)? Pinging the @elastic/kibana-data-discovery team in particular, since they should own the bulk of these actions.