action #42851
closed[functional][y][tools] Implement view for multiple job groups
0%
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¶
- There is a view showing results for multiple job groups
Updated by riafarov over 5 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.
Updated by okurz over 5 years ago
- Project changed from openQA Tests to openQA Project
- Category set to Feature requests
Updated by coolo over 5 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
Updated by okurz over 5 years ago
- Due date set to 2018-11-20
- Target version set to Milestone 20
Updated by okurz over 5 years ago
probably needs a simple change somewhere around https://github.com/os-autoinst/openQA/blob/master/templates/main/index.html.ep#L26
Updated by okurz over 5 years ago
- Related to coordination #40475: [functional][y][saga] Establish YaST team split added
Updated by riafarov over 5 years ago
- Status changed from New to Workable
- Estimated time set to 8.00 h
Updated by oorlov over 5 years ago
- Status changed from In Progress to Feedback
Updated by riafarov over 5 years ago
- Due date changed from 2018-11-20 to 2018-12-04
PR not yet merged.
Updated by okurz over 5 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?