Project

General

Profile

action #33676

Group results by group name, not build number in parent_group_overview

Added by mkravec over 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2018-03-22
Due date:
% Done:

60%

Estimated time:
Difficulty:

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 (58.8 KB) poo-after.png parent group - proposal mkravec, 2018-03-23 10:00
poo-before.png (174 KB) poo-before.png parent group - now mkravec, 2018-03-23 10:00
Clipboard - March 24, 2020 10_39 AM.png (149 KB) Clipboard - March 24, 2020 10_39 AM.png ilausuch, 2020-03-24 09:40
Clipboard - March 24, 2020 10_40 AM.png (114 KB) Clipboard - March 24, 2020 10_40 AM.png ilausuch, 2020-03-24 09:40
4270
4273
9606
9609

History

#1 Updated by EDiGiacinto over 3 years ago

  • Project changed from openQA Tests to openQA Project

#2 Updated by coolo over 3 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 over 3 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 over 3 years ago

4270
4273

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 almost 3 years 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 almost 3 years 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 over 2 years ago

  • Category changed from 124 to Feature requests

#8 Updated by Xiaojing_liu about 2 years ago

  • Assignee set to Xiaojing_liu

#9 Updated by Xiaojing_liu about 2 years ago

  • Target version changed from Ready to Current Sprint

#10 Updated by Xiaojing_liu about 2 years 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 about 2 years ago

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

#12 Updated by okurz almost 2 years ago

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

#13 Updated by ilausuch over 1 year ago

  • Assignee set to ilausuch

#14 Updated by cdywan over 1 year ago

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

#15 Updated by cdywan over 1 year ago

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

#18 Updated by okurz over 1 year 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 over 1 year ago

#20 Updated by ilausuch over 1 year ago

  • Status changed from In Progress to Resolved

#21 Updated by okurz over 1 year ago

  • Status changed from Resolved to Feedback

Please stick to our ticket workflow. As the PR is still open this can not be Resolved. But as you probably do not invest work anymore right now, "Feedback" is the right status

#22 Updated by ilausuch over 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF