action #33676

Group results by group name, not build number in parent_group_overview

Added by mkravec about 2 years ago. Updated 10 days ago.

Status:In ProgressStart date:22/03/2018
Priority:LowDue date:
Assignee:ilausuch% Done:

60%

Category:Feature requests
Target version:Current Sprint
Difficulty:
Duration:

Description

Motivation

What we 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.

Why change it

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"

poo-after.png - parent group - proposal (58.8 KB) mkravec, 23/03/2018 10:00 am

poo-before.png - parent group - now (174 KB) mkravec, 23/03/2018 10:00 am

Clipboard - March 24, 2020 10_39 AM.png (149 KB) ilausuch, 24/03/2020 09:40 am

Clipboard - March 24, 2020 10_40 AM.png (114 KB) ilausuch, 24/03/2020 09:40 am

4270
4273
9606
9609

History

#1 Updated by EDiGiacinto about 2 years ago

  • Project changed from openQA Tests to openQA Project

#2 Updated by coolo about 2 years ago

  • Status changed from New to Rejected

not sure what persona you have in mind, but the parent group overview is the way it is because the release managers want to see all results for their product in one bar.

#3 Updated by coolo about 2 years ago

  • Subject changed from [tools] Group results by group name, not build number in parent_group_overview to Group results by group name, not build number in parent_group_overview
  • Category set to 124
  • Status changed from Rejected to New
  • Target version set to Ready

I should be specific: SLE release managers. So thinking about, we might offer a parameter or group setting

#4 Updated by mkravec about 2 years ago

I attached few images to explain it better.

I think this would not hurt SLE also (because main page is almost the same as parent group page now) - but as you say that's up to release managers :)

Maybe we can reuse "Sort by build value / Sort by time job most recently created" option, I think we won't need "by time job most recently created" anymore.

#5 Updated by coolo over 1 year ago

I can tell you that SLE release managers take screenshots of exactly this page into go/no-go meetings. So changing it without an option is not an option - pun intended.

#6 Updated by mkittler over 1 year ago

So this is basically grouping the builds by job groups (instead of grouping the job groups by builds).


It is true that the current parent group overview is redundant. So I suppose it is used as "filter" by those managers and we shouldn't remove that possibility. Making the new view optional would be possible of course. However, it raises the question where to place the switch. Also it would be a bit weird/confusing to have two actually different pages combined under the name "parent group overview".

#7 Updated by okurz 10 months ago

  • Category changed from 124 to Feature requests

#8 Updated by Xiaojing_liu 8 months ago

  • Assignee set to Xiaojing_liu

#9 Updated by Xiaojing_liu 7 months ago

  • Target version changed from Ready to Current Sprint

#10 Updated by Xiaojing_liu 7 months ago

  • Assignee deleted (Xiaojing_liu)
  • Priority changed from Normal to Low
  • Target version changed from Current Sprint to Ready

in my humble opinion, the priority is low, and need to pay much effort on it. So I cancel assigning it to me. I would like to not do it until there is a strong requirement.

#11 Updated by mkravec 7 months ago

CaaSP is not tested by openQA anymore - if not needed by others you can close this issue.

#12 Updated by okurz 4 months ago

  • Description updated (diff)
  • Status changed from New to Workable

#13 Updated by ilausuch about 1 month ago

  • Assignee set to ilausuch

#14 Updated by cdywan about 1 month ago

  • Status changed from Workable to In Progress
  • Target version changed from Ready to Current Sprint

#15 Updated by cdywan 16 days ago

@ilausuch Are you still working on this? On should we discuss this a bit more?

#16 Updated by ilausuch 12 days ago

Added option to change the view

#18 Updated by okurz 11 days ago

ilausuch wrote:

Added option to change the view

please use the existing view for changing the job group settings where we already have a selection for "sort by build" and "sort by time"

#19 Updated by ilausuch 10 days ago

Also available in: Atom PDF