-
Epic
-
Resolution: Done
-
Undefined
-
None
-
ACM 2.8.0
Epic Goal
...
Ensure that the options provided by the Search autocomplete feature provides complete and consistent results.
Why is this important?
...
For autocomplete in the Search bar, the options in the drop-down are fetched once based on the type of input; for ex: `kind:` or `name:`. To improve performance, there is a limit on the data the query can fetch. This will result in the autocomplete not having all the data the user is expecting. So, it is important to filter the results based on the user's input.
Scenarios
...
Related case: https://issues.redhat.com/browse/ACM-5242
https://issues.redhat.com/browse/ACM-5287 - duplicate
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>