-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Meta] Global Search #57576
Comments
Pinging @elastic/kibana-core-ui (Team:Core UI) |
@ryankeairns @myasonik Does this issue supersede #15019? (In which case I think that other issue could be closed). |
The Currently in NP, For this specific use-case, we could just 'aggregate' SO results from the server with application results 'generated' from the client, however as we want to be able to use the functionality in https://github.com/elastic/dev/issues/1370, this doesn't seems like an option. Not sure what the best approach is going to be to solve this. Thinking out loud: Moving app registration to server-sideI don't think we want to go back to the 'uiExport' nightmare, so I'd say this is insta-excluded Duplicating registration on both client and server-sidePlugins would have to register applications metadata on the server-side in addition to the client side. That would include at least Use AST at build time to parse the calls to
|
For posterity's sake, we have decided to go with the "Ignore the chatops requirement" option for the time being. It should be fairly negligible difference effort of doing it now vs. later, so we are opting for later in order to keep the MVP of Global Search unblocked. |
FYI, I created an RFC for the initial implementation of core |
As discussed with @ryankeairns , closing to focus on the next phase of search #83354 |
Summary
The Kibana design team has proposed adding a global search bar that would assist users in navigating the growing number of applications and objects. This would augment, or be an alternative to, the main Kibana navigation UI.
This feature could be expanded to accommodate additional capabilities such as shortcuts to create new objects, user-defined shortcuts, and more. However, the initial focus is improved navigation.
Target outcome
Users can quickly navigate Kibana applications and saved objects without having to repeatedly click through navigation.
Requirements
MVP - Search as navigation - #58049
Prerequisite: URL service - #25247
“Dashboards” and “Visualizations”...etc
Future considerations (to be further prioritized post-MVP)
Feature results provider: [GS] Feature results provider #72680
Search across multiple Spaces: [GS] Search across Spaces #67977
Scoped results / search syntax: [GS] Advanced search syntax to fine tune results returned #74290
Entity results provider: [GS] Entity results provider #74283
Additional search content; also building on the 'syntax' concept
Change the scope of search based upon context.
Contextual, app-based commands tied to key commands
Pinning (a suggestion; UX unclear; blocked until proper personalization)
Enhanced results using Pulse telemetry data
Advanced search/Results page (i.e. advanced search; robust filtering with App Search; see mockup)
Natural language processing
Phased approach
7.10
7.X/8.X
Prototypes and mockups
Figma prototype
https://www.figma.com/proto/EG8LewmUTK2la66aXfkOKE/Kibana-Header?node-id=484%3A410&viewport=-1025%2C-871%2C0.5&scaling=min-zoom
Search input mockup
Results page (future)
The text was updated successfully, but these errors were encountered: