[GS] Search across Spaces

[joshdover]

Related to #61657 and #65222

Add support for searching SOs across all spaces user has access to in a single query.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[elasticmachine]

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

[pgayvallet]

Depends on #27003

[alexfrancoeur]

@ryankeairns we should probably discuss more during our next planning sync, but I'd argue that we may want more granular search (#72680) before expanding to spaces. This will also help us hide (or remove) the feature directory.

[ryankeairns]

@ryankeairns we should probably discuss more during our next planning sync, but I'd argue that we may want more granular search (#72680) before expanding to spaces. This will also help us hide (or remove) the feature directory.

+1 to that approach, having played with this a bit I only wish it had more depth of content :)

[ryankeairns]

With the proposed designs for adding tags to the search UI, we've arrived at needing to reconsider the UX for cross-space search. The early designs of navigational search used the right end of the row to convey the Space as follows:

Early design

Evolving design with tags

As search has evolved organically, tags - and their use in the new search syntax (e.g. tag:mytag) - have arrived before cross-space capabilities. Through this evolution, we're also seeing that mixing results from multiple spaces generates interaction complexities and/or an increase in the sheer volume of results. The main takeaway is that it seems we're heading down a path where we're trying to do too much and risk losing the essence of what the search UI currently provides - simple, quick navigation.

Taking that into consideration, we're proposing moving forward displaying tags at the right end of the row and exploring alternatives for the Spaces UX. A number of initial ideas were generated, all of which leave us feeling confident that we can arrive at an alternative that won't be hindered by our decision for tags.

Some of those ideas include (non-mutually exclusive):

• Moving things such as cross-space search to a dedicated, advanced search page
• Adding space:myspacename to the search syntax
• Display indicators where an item may exist in multiple Spaces (we're reserving the icon space on the left, just in case)
• Consider secondary actions for opening a focused item in the not-current Space
• Provide an advanced setting to toggle cross-space search

The good news is we have options. In the near to medium term, the additional search syntax may cover most of the use case.

cc:/ @MichaelMarcialis @myasonik

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[petrklapka]

Very old issue. Needs a dustoff to see current status and security implications etc.

[petrklapka]

@legrego @kevinsweet @clintandrewhall - Flagging this as a "candidate to close" since cross space now also implies cross-solution. If global search cannot find apps/pages across Solution types/Spaces, is there enough value left in finding user objects across spaces to still consider this?

[legrego]

Flagging this as a "candidate to close" since cross space now also implies cross-solution. If global search cannot find apps/pages across Solution types/Spaces, is there enough value left in finding user objects across spaces to still consider this?

I still think there is value in this. Searching for "my stuff" regardless of where it lives is useful. The introduction of solution views may change the types of entities we choose to surface, but it doesn't negate the utility in my opinion