Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
alexmarhaba opened this issue Jun 10, 2024 · 4 comments · Fixed by #182535
Assignees
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews) Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas

Comments

@alexmarhaba
Copy link

alexmarhaba commented Jun 10, 2024

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

@alexmarhaba alexmarhaba added Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jun 10, 2024
@elasticmachine
Copy link
Contributor

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

@Heenawter
Copy link
Contributor

Heenawter commented Jun 10, 2024

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 three 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) - View mode only

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.

@Heenawter Heenawter added the Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews) label Jun 10, 2024
@cqliu1 cqliu1 self-assigned this Jul 25, 2024
@andreadelrio
Copy link
Contributor

Please let's align all of these by using the same label Open in Discover with the discoverApp icon.

@davismcphee
Copy link
Contributor

Just a note that it might be a bit trickier than it seems at a glance to align all of these actions since they do different things:

  • "Explore in Discover" and "Explore underlying data" navigate the user to Discover with the necessary query, filters, etc. to recreate the view of the data they are currently looking at.
  • "Open in Discover" opens the underlying saved search the panel is based on, not carrying over things like Dashboard query, filters, etc.

As @Heenawter mentioned there are probably more actions and each with nuances in their behaviour, so aligning them all probably involves more analysis and decision making beyond just changing labels and icons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews) Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants