Advanced Search global search should not be affected by zoekt unless explicitly enabled

Problem

Advanced Search (Elasticsearch/OpenSearch) global search functionality should operate independently from zoekt code search. Currently, there may be unintended interactions between these two search systems that affect global search results when zoekt is not properly configured or enabled.

Expected Behavior

  • Global search via Advanced Search should work correctly regardless of zoekt configuration
  • Users should only experience zoekt-related search behavior when they explicitly enable and configure zoekt with proper infrastructure setup
  • Disabling or not configuring zoekt should have no impact on Advanced Search global search results

Current Issue Context

A self-managed customer reported that global search returns no results, while group-scoped searches work correctly. Investigation revealed:

  • Visibility and access control are not the cause
  • Console searches exhibit the same behavior
  • Reindexing doesn't resolve the issue
  • No errors in logs
  • Elasticsearch/OpenSearch configuration appears normal
  • The issue is specific to global search; group-scoped searches function properly

This suggests the problem may be in the global search query logic or how zoekt configuration affects the global search path.

Related Issues