https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-05-28T11:30:01ZopenSUSE Project Management ToolopenQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2160172019-05-28T11:30:01Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul><p>PR: <a href="https://github.com/os-autoinst/openQA/pull/2084" class="external">https://github.com/os-autoinst/openQA/pull/2084</a></p>
<p>Just a 5-minute fix - maybe I can add tests later.</p>
<p>Btw, that the search doesn't cover the settings anymore was not intended. When I improved sorting I accidentally messed the search for settings.</p>
<blockquote>
<p>Allow to show "all" entries per page, not only up to 100</p>
</blockquote>
<p>With the amount of test suites we currently have that would be quite slow/unresponsive.</p>
openQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2160532019-05-28T11:57:10Zokurzokurz@suse.com
<ul></ul><p>mkittler wrote:</p>
<blockquote>
<blockquote>
<p>Allow to show "all" entries per page, not only up to 100</p>
</blockquote>
<p>With the amount of test suites we currently have that would be quite slow/unresponsive.</p>
</blockquote>
<p>Yes, obviously but the user needing to go through all the pages is slower :) How about you write "All" in red to tell the user that this might be dangerous? ;)</p>
openQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2164762019-05-29T09:20:53Zokurzokurz@suse.com
<ul></ul><p>PR merged and deployed on o3, works in production, thanks. Now about the "only 100 jobs per page", it's obviously less important but in other cases we also offer an option for "All" so should we still do that here or not at all?</p>
openQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2173972019-06-03T10:41:19Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Obviously the only useful way to use the table with currently over 2000 entries is using the filter in the first place. But that hopefully decreases the number of rows to something under 100. So I think showing up to 100 rows at a time is enough. We can increase the max. page size if it is demanded but I wouldn't add an 'All' option. That simply doesn't scale and the user should instead use a more specific search term.</p>
openQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2176822019-06-03T19:05:22Zokurzokurz@suse.com
<ul></ul><p>Ok. I just fear that this will just make it more likely for people to add even more test suites. I would not mind if you also limit the number of allowed entries in the database to something like 2000 ;)</p>
openQA Project - action #52232: UI: search for testsuite settings only on current page vs. only 100 jobs per page possiblehttps://progress.opensuse.org/issues/52232?journal_id=2227102019-06-21T05:35:19Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-12 priority-3 priority-lowest" href="/issues/53402">action #53402</a>: [beginner] Not possible to search for test suites (again?) using regex, e.g. `^gnome$`</i> added</li></ul>