coordination #89062
Updated by okurz almost 2 years ago
## Motivation https://confluence.suse.com/pages/viewpage.action?spaceKey=openqa&title=QAM+openQA+review+guide explains the current process for openQA test review within SUSE QAM. We have already learned that they rely on some special rules which have not been foreseen like this within openQA, e.g. they see the black certificate as "tests reviewed and failures can be ignored" rather than "every job has a comment but not necessarily more than that" . We can try to improve openQA so that it features can be used in the correct way and review workflows become even easier. ## Ideas /tests can already be configured like https://openqa.opensuse.org/tests/?resultfilter=Failed&resultfilter=Incomplete&resultfilter=timeout_exceeded , even over UI elements. Also /tests already shows a comments icon but makes no distinction like on /tests/overview or "next & previous" between "plain comment", "label" or "bugref". * *DONE:* DONE: Distinguish between "plain comment", "label" and "bugref" same as we do in /tests/overview and "next & previous" -> #94937 * *DONE:* Add query parameter to filter only jobs that need review, e.g. "todo=1", same as on /tests/overview . At best use the same logic to prevent duplication * Allow to show more than the default 500 finished jobs on /tests on request * On /tests also limit "running" and "scheduled" jobs, same as finished, but give the user the opportunity to show more or the additional ones, e.g. on an extra page for each running, scheduled, finished * Optional: Add UI element to configure this, e.g. again like on /tests/overview the "todo" checkbox * Optional: Add further filter query parameters (+doc, +UI control elements) for * job group include/exclude regex (similar to what we have on the index page) * filter for "no group/any group" * test module include/exclude regex * further filter possibilities, e.g. medium, flavor, arch, machine