Simplify Advanced Global Search name to Advanced Search
Problem
We have search functionality spread across the product: issues and MR's, log search, and global search to name a few. This can cause confusion if we are not specific when talking about search functionality, since it is not clear what area of the product we are talking about.
Currently some of these features have longer names, which causes people to shorten them for convenience. When that happens, it is no longer clear what feature one is talking about.
Solution
We should work to simplify the Global Search naming, if possible.
Proposal
Global Search Team
- Advanced Search
- uses Elasticsearch
- Has a Search API
- Basic Search
- No elastic
- Has a Search API
Syntax Search
Some aspects to keep in mind:
- Global Search from the /search endpoint
- Global Search has a "Basic" mode which does not require Elasticsearch and an "Advanced" mode which does require Elasticsearch. We will need to disambiguate between these in some way, as the feature set and requirements are different.
- Filter bar searches (/issues, /merge_requests, /epics) (Part of Plan)
- Search within dropdowns (milestone, users, right side of issues) (Part of the Global FE)
- Log Search (Part of APM)
Prior work and discussions
Edited by John McGuire