coordination #70840
[epic] further features for the "search" feature
100%
Description
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 #71422
- 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>orfinished:<t_finished>(for jobs) - see https://developer.github.com/v3/search/ for reference
- optional: extend for other stuff to search for, e.g. users, audit events, needles, assets, bugs, everything else we have in openQA … except maybe API keys and secrets ;)
- mkittler also suggested we display the type of result, maybe as an icon.
- optional: Include search field in the tutorial popup "feature tour"
Subtasks
Related issues
History
#1
Updated by okurz 11 months ago
Updated by - Copied from action #34486: database of "test cases" or how to search for tests we have in openQA added
#5
Updated by Xiaojing_liu 11 months ago
Updated by This pr is used to find job template by test suite name: https://github.com/os-autoinst/openQA/pull/3395
Updated by #10
Updated by szarate 10 months ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
#11
Updated by asmorodskyi 4 months ago
Updated by szarate wrote:
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
list is not available anymore so no way to figure out the reason :(
#12
Updated by asmorodskyi 4 months ago
clickable search results. We should link results, e.g. a job template links to the job group.
+1
optional: include job groups in search as well
no-go until more granular searching capabilities will be implemented ( see below )
optional: add search qualifiers, e.g. testsuite: or finished: (for jobs)
+1 also I would vote for removing "optional" here and increase priority . Currently it is really hard to find something in Test Suite / Medium types etc. without using browser search additionally. But browser search failing due to pagination of entities.
see https://developer.github.com/v3/search/ for reference
optional: extend for other stuff to search for, e.g. users, audit events, needles, assets, bugs, everything else we have in openQA … except maybe API keys and secrets ;)
mkittler also suggested we display the type of result, maybe as an icon.
+1 but I am not sure how it correlates with one above ?
From ticket description unfortunately is not clear if this is meant for all pages ( Medium types / Test Suite / Machines / Assets / Workers ) or only for Test Suites ?
#13
Updated by cdywan 4 months ago
Updated by asmorodskyi wrote:
clickable search results. We should link results, e.g. a job template links to the job group.
+1
optional: include job groups in search as well
no-go until more granular searching capabilities will be implemented ( see below )
optional: add search qualifiers, e.g. testsuite: or finished: (for jobs)
+1 also I would vote for removing "optional" here and increase priority . Currently it is really hard to find something in Test Suite / Medium types etc. without using browser search additionally. But browser search failing due to pagination of entities.
see https://developer.github.com/v3/search/ for reference
optional: extend for other stuff to search for, e.g. users, audit events, needles, assets, bugs, everything else we have in openQA … except maybe API keys and secrets ;)
mkittler also suggested we display the type of result, maybe as an icon.+1 but I am not sure how it correlates with one above ?
From ticket description unfortunately is not clear if this is meant for all pages ( Medium types / Test Suite / Machines / Assets / Workers ) or only for Test Suites ?
I would think we'll need a filter for all supported types. If we list assets we should probably be able to say "only assets".