Project

General

Profile

Actions

action #42851

closed

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

Added by riafarov about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
SUSE QA (private) - Milestone 21
Start date:
2018-10-24
Due date:
2018-12-04
% Done:

0%

Estimated time:
8.00 h

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 1 (0 open1 closed)

Related to openQA Tests (public) - coordination #40475: [functional][y][saga] Establish YaST team splitResolvedriafarov2018-10-092019-11-19

Actions
Actions #1

Updated by riafarov about 6 years 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.

Actions #2

Updated by okurz about 6 years ago

  • Project changed from openQA Tests (public) to openQA Project (public)
  • Category set to Feature requests
Actions #3

Updated by coolo about 6 years 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

Actions #4

Updated by riafarov about 6 years ago

  • Description updated (diff)
Actions #5

Updated by riafarov about 6 years ago

  • Parent task deleted (#42191)
Actions #6

Updated by okurz about 6 years ago

  • Due date set to 2018-11-20
  • Target version set to Milestone 20
Actions #7

Updated by okurz about 6 years ago

Actions #8

Updated by okurz about 6 years ago

Actions #9

Updated by riafarov about 6 years ago

  • Status changed from New to Workable
  • Estimated time set to 8.00 h
Actions #10

Updated by oorlov about 6 years ago

  • Status changed from Workable to In Progress
Actions #11

Updated by oorlov about 6 years ago

  • Assignee set to oorlov
Actions #12

Updated by oorlov about 6 years ago

  • Status changed from In Progress to Feedback
Actions #13

Updated by riafarov about 6 years ago

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

PR not yet merged.

Actions #14

Updated by oorlov about 6 years ago

  • Status changed from Feedback to Resolved

PR merged.

Actions #15

Updated by okurz about 6 years 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?

Actions #16

Updated by oorlov about 6 years ago

  • Status changed from Feedback to Resolved

Deployed on OSD.

Actions

Also available in: Atom PDF