coordination #70840
Updated by okurz over 3 years ago
## Motivation
## Acceptance criteria
## Suggestion
* clickable search results. We should link results, e.g. a job template links to the job group.
* names of test suite database
* https://github.com/okurz/scripts/blob/master/openqa-db_query_last_use_of_module provides an external tool relying on database access but it can help to find out scenarios running a specified test module.
* add keyboard shortcut to reach search field, again maybe just like github
* optional: include job groups in search as well
* optional: add search qualifiers, e.g. "testsuite:<testsuite_search_term>" or "finished:<t_finished>" (for jobs)
* optional: extend for other stuff to search for, e.g. users, audit events, everything else we have in openQA … except maybe API keys and secrets ;)
* see https://developer.github.com/v3/search/ for reference
* More potentially interesting match types:
* Needles
* Assets
* Bugs
* Job by job module
* mkittler also suggested we display the type of result, maybe as an icon.
* optional: Include search field in the tutorial popup "feature tour"