Concept: Universal search for people / recordings / cohorts / events / groups

Is your feature request related to a problem?

This issue tries to outline a solution to many disparate issues with the meta problem being:

• search capabilities outside of insights are lacking
• cohorts feature especially is very isolated from the rest of the app
• improving each search feature leads only to improvements in one product area.

Describe the solution you'd like

A insights-like search functionality for everything qualitative: people / recordings / cohorts / events / groups.

Similar to insights, this would take the form of a sentence (containing various dropdowns), like:

Show me [People | Group Type G | Cohorts | Recordings | Events from people | Recordings from people] who [Have property | Belong to COHORT | Have done Y]

Where user can easily switch between what's being shown via dropdown or via selecting a new tab from side navigation.

There are also context-specific actions, for example:

• When searching for people / specific group types, you can also save the results as a cohort
• In recordings, Have done Y would only show recordings which match the filter

Viewing a cohort then becomes an action of selecting the appropriate filter and showing the same results as elsewhere. Note that with this approach, creating cohorts of groups would also become possible.

We could link to this view from any person modal with a static filter being set (e.g. has completed funnel step Y).

There could also be a time filter for various views.

This view could also power additional analytics - e.g. show correlated properties for people/cohort/group that was selected, show who might be slipping away, etc.

Describe alternatives you've considered

Universal search experience like one outlined in https://www.figma.com/file/NHPA2hVWwaKp4eTGWdigs9/?node-id=128%3A437. However this is too 'hard' to solve as an initial step.

Additional context

Grab bag of related issues:

• https://github.com/PostHog/posthog/issues/7265
• https://github.com/PostHog/posthog/issues/7941
• https://github.com/PostHog/posthog/issues/4955
• https://github.com/PostHog/posthog/issues/3765
• https://github.com/PostHog/posthog/issues/6186
• https://github.com/PostHog/posthog/issues/3032
• https://github.com/PostHog/posthog/issues/6299
• https://github.com/PostHog/posthog/issues/7876
• https://github.com/PostHog/posthog/issues/2594
• https://github.com/PostHog/posthog/issues/6186

cc @clarkus @EDsCODE @paolodamico @mariusandra @rcmarron

Thank you for your feature request – we love each and every one!

No implementation files, tests, or entry points are named. Start by reviewing the linked issues and the referenced Figma concept to understand existing search and cohort behavior; the issue does not define a bounded scope or concrete done condition.