Global Search MVP

[ryankeairns]

This issue represents the Phase 1 "MVP" described in the [Meta] Global Search issue.

---

Summary

In order to provide users a better navigation experience, we would like to add a global search feature that would assist them in finding specific applications and saved objects via shortcuts. While there are several possible extensions of this feature, the MVP is focused on augmenting Kibana navigation.

Target outcome

Users can quickly navigate Kibana applications and saved objects without having to repeatedly click through navigation.

Requirements for MVP

Pre-reqs, decisions, and assumptions

👉 Prerequisite: URL Service
- #25247 - [see this comment regarding contingency approach](#25247 (comment)
- Also, this basic implementation has been merged

👉 Prerequisite: Search service - interface that wraps existing APIs; Platform will provide support

👨‍⚖ 3/24 Decision for MVP: Use client-side solution for identifying available apps
👩‍⚖ 3/24 Decision for MVP: Search results will be scoped to current Space only
👨‍⚖ 8/14 Decision for MVP: Use app list for initial result set; continue discussing next iteration here

Features

1. Search input in header (see mockup and prototype)
   • The input may be open by default except on mobile screen sizes where we'll likely need a search header button to toggle it open
2. Shortcut to open/focus search (e.g. Command/Windows + K)
3. Search results should return apps and saved objects
   • Links to applications by name, e.g. “Dashboard” and “Visualize”
   • Links to saved objects
     • Dashboards
     • Visualizations
     • Saved searches
     • Canvas workpads
     • Maps
     • Graphs
     • ML jobs (future)
     • SIEM Timelines
     • etc.
4. Display recent items (moved out of MVP [GS] Improve initial results display #75040)
   • Upon initial focus of the search input, we should return the MRU (most recently used) saved objects for the current user. Recently viewed items exist atop the current left hand nav, but do not exist in the upcoming nav redesign as there are no submenus. We're relocating them here as it also provides a nice starting experience when you focus on the search input.

---

Design / mockups

From elastic/eui#3490 (comment) :

Here's a run-through of all the different iterations (mistakenly referred to as edge-cases) using the pre-defined template:

🎥 Screencast | 🎨 Mockups | 👩‍💻 Coded prototype

A quick screenshot for each of the result types:

All results are the same height.

Search service spec

https://docs.google.com/document/d/19wuwElchLp2XanYy2ttMDTZ1oQG9rwqXoSArb_iHO2I/edit# (Elastic only)

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[ryankeairns]

See this comment regarding building links with the existing Saved Objects API: #25247 (comment)

[ryankeairns]

There's a chance that, for branding reasons, we do away with all app/sub-solution logos which would mean no logos in the search results. Instead, we'd just rely on the text name and description text as seen in the mockups above.

As of now, this is just in the discussion phase and I will report back with updates.

[cchaos]

Without the logos, I think the big design task task is figuring out how to differentiate between just App (plugin) names and saved objects.

[ryankeairns]

Perhaps something like this where we use the solution logo alongside app results, which also associates to the organization within the left nav:

[pgayvallet]

FYI, started the discussion on the GS service interface: #61657 (comment). Inputs/comments are very welcome.