List of potential QoL improvements with Advanced Search
## Potential improvements
### Use Advanced Search to speed up users autosuggestion
Currently, when you first open an issue/MR/epic and select the user dropdown, you need to wait a couple seconds until `autocomplete_sources/members` returns an array of users. I believe we can utilize users index in Elasticsearch to drastically speed it up.
Related issues: https://gitlab.com/gitlab-org/gitlab/-/issues/367559 and https://gitlab.com/gitlab-org/gitlab/-/issues/388200
### Use Advanced Search to speed up projects dropdowns
Similar to the above, we have a lot of project dropdowns in GitLab, so we can use Advanced Search if it's enabled to improve UX.
### Index groups and use Advanced Search to speed up groups dropdowns
Another dropdown-related idea. We'll need to index all groups to do that.
### Use Advanced Search to speed up labels dropdowns
We currently only index labels as part of issues, but we can consider indexing labels separately.
### Achieve feature parity with MR/issue lists
If we achieve feature parity with the existing MR/issue pages (for example, https://gitlab.com/gitlab-org/gitlab/-/issues) we can switch the backend from PostgreSQL to Advanced Search and achieve noticeable performance improvements.
<!-- Please add a label for the type of maintenance as per https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification -->
epic