action #33676
Updated by okurz over 4 years ago
## Motivation ### What we have have: On home page (https://openqa.suse.de/) we display: - parent group name - show last 3 builds in parent group - each build can be expanded to display sub-groups On parent group overview page (https://openqa.suse.de/parent_group_overview/15) we display the same information: - list of sub-groups - show last 10 builds in parent group - each build is expanded to display sub-groups This seems redundant and loading time of parent group overview is quite slow. That's why I think parent group overview is not used much, but I might be wrong here. ### My proposal Change parent group overview page to group results by sub-groups, not build numbers and show: - list of sub-groups - each sub-group will display results for last build - each sub-group can be expanded to display multiple builds (maybe not needed since it's visible on group overview page - https://openqa.suse.de/group_overview/110) ### Why change it - display mechanism works fine only if every medium in sub-group has identical build number (works in SLE - https://openqa.suse.de/parent_group_overview/15) - display mechanism is useless for every parent group that groups different build numbers (broken in CaaSP - https://openqa.suse.de/parent_group_overview/18) - managers & reviewers might appreciate it - I have to open 6+ pages to find results of last CaaSP build - page loading time might improve ## Acceptance criteria * **AC1:** The parent job group overview page can be configured to group builds by job group (instead of grouping job groups by builds) * **AC2:** The current parent job group overview grouping is still available ## Suggestion * Based on a parameter change parent group overview page to group results by sub-groups, not build numbers and show: - list of sub-groups - each sub-group will display results for last build - each sub-group can be expanded to display multiple builds (maybe not needed since it's visible on group overview page - https://openqa.suse.de/group_overview/110) * The switch can be included on the template page to reload the page with changed settings or an attribute of the parent job group, similar as for job group where we configure the order "by value" or "by date"