action #42851

[functional][y][tools] Implement view for multiple job groups

Added by riafarov over 1 year ago. Updated over 1 year ago.

Status:ResolvedStart date:24/10/2018
Priority:NormalDue date:04/12/2018
Assignee:oorlov% Done:

0%

Category:Feature requestsEstimated time:8.00 hours
Target version:SUSE QA tests - Milestone 21
Difficulty:
Duration: 30

Description

Motivation

I as a RM and test results reviewer want to see combined view of multiple job groups which are subsets of a broader functionality. Fox example, Functional testing consists of installation and user space application testing. People, who are interested in one of the job groups can have limited group and there is an overview for the bigger scope.

As a test developers, we want to split job groups to smaller and more specific areas, we also need a view which can combine multiple ones.
This is already supported when setting multiple job group ids in the url, e.g.: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=79.1&groupid=129&groupid=110

Acceptance criteria

  1. There is a view showing results for multiple job groups

Related issues

Related to openQA Tests - action #40475: [functional][y][saga] Establish YaST team split Blocked 31/08/2018 21/04/2020

History

#1 Updated by riafarov over 1 year ago

@coolo, could you please provide your feedback on this, e.g. having additional layers of hierarchy, job groups or just putting additional url somewhere.

#2 Updated by okurz over 1 year ago

  • Project changed from openQA Tests to openQA Project
  • Category set to Feature requests

#3 Updated by coolo over 1 year ago

Could you please discuss user stories not features? As you rightfully explained: there is already a view combining job groups. I use that everyday e.g. as I bookmarked
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=49&groupid=55

#4 Updated by riafarov over 1 year ago

  • Description updated (diff)

#5 Updated by riafarov over 1 year ago

  • Parent task deleted (#42191)

#6 Updated by okurz over 1 year ago

  • Due date set to 20/11/2018
  • Target version set to Milestone 20

#7 Updated by okurz over 1 year ago

#8 Updated by okurz over 1 year ago

  • Related to action #40475: [functional][y][saga] Establish YaST team split added

#9 Updated by riafarov over 1 year ago

  • Status changed from New to Workable
  • Estimated time set to 8.00

#10 Updated by oorlov over 1 year ago

  • Status changed from Workable to In Progress

#11 Updated by oorlov over 1 year ago

  • Assignee set to oorlov

#12 Updated by oorlov over 1 year ago

  • Status changed from In Progress to Feedback

#13 Updated by riafarov over 1 year ago

  • Due date changed from 20/11/2018 to 04/12/2018

PR not yet merged.

#14 Updated by oorlov over 1 year ago

  • Status changed from Feedback to Resolved

PR merged.

#15 Updated by okurz over 1 year ago

  • Status changed from Resolved to Feedback
  • Target version changed from Milestone 20 to Milestone 21

I think we still want to have a ticket open until we can verify in production, isn't it?

#16 Updated by oorlov over 1 year ago

  • Status changed from Feedback to Resolved

Deployed on OSD.

Also available in: Atom PDF