Project

General

Profile

action #52232

UI: search for testsuite settings only on current page vs. only 100 jobs per page possible

Added by okurz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
-
Start date:
2019-05-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Problem

https://openqa.opensuse.org/admin/test_suites has a search field which seems to search within the test suite name as well the description but not the settings column so a user has to revert to the browser search functionality which however is limited to only search on the current page. One can select to show up to 100 test suites per page but not "all" meaning one has to search on every single page to find all occurences.

Suggestions

  • Extend the search field (again, after it was removed) to cover search in the settings as well
  • Allow to show "all" entries per page, not only up to 100

Related issues

Related to openQA Project - action #53402: [beginner] Not possible to search for test suites (again?) using regex, e.g. `^gnome$`Workable2019-06-21

History

#1 Updated by mkittler over 3 years ago

  • Status changed from New to In Progress
  • Assignee set to mkittler

PR: https://github.com/os-autoinst/openQA/pull/2084

Just a 5-minute fix - maybe I can add tests later.

Btw, that the search doesn't cover the settings anymore was not intended. When I improved sorting I accidentally messed the search for settings.

Allow to show "all" entries per page, not only up to 100

With the amount of test suites we currently have that would be quite slow/unresponsive.

#2 Updated by okurz over 3 years ago

mkittler wrote:

Allow to show "all" entries per page, not only up to 100

With the amount of test suites we currently have that would be quite slow/unresponsive.

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? ;)

#3 Updated by okurz over 3 years ago

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?

#4 Updated by mkittler over 3 years ago

  • Status changed from In Progress to Resolved

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.

#5 Updated by okurz over 3 years ago

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 ;)

#6 Updated by okurz over 3 years ago

  • Related to action #53402: [beginner] Not possible to search for test suites (again?) using regex, e.g. `^gnome$` added

Also available in: Atom PDF