Bug 713578 - [Beaker] Job matrix report, multiple job selection in Whiteboard
Summary: [Beaker] Job matrix report, multiple job selection in Whiteboard
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: reports
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL: https://beaker.engineering.redhat.com...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 19:44 UTC by Jeff Burke
Modified: 2019-05-22 13:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-20 06:19:06 UTC


Attachments (Terms of Use)

Description Jeff Burke 2011-06-15 19:44:12 UTC
Description of problem:
 In the Job Matrix Report. I am unable to select multiple jobs.

For example: If you look at the Whiteboard box in this URL:
https://beaker.engineering.redhat.com/matrix/?whiteboard=kernel-2.6.32-131.4.1.el6+KernelTier1+RELEASE&whiteboard_filter=kernel-2.6.32-131.4.1.el6+KernelTier1+RELEASE&toggle_nacks_on=on

 I am limited to a single Whiteboard. "kernel-2.6.32-131.4.1.el6 KernelTier1 RELEASE" but if you look at the list of jobs there are some that look like this:
kernel-2.6.32-131.4.1.el6 KernelTier1 RELEASE [FQDN]
kernel-2.6.32-131.4.1.el6 KernelTier1 RELEASE [Some other data]

 I would like to have multiple selection in the Whiteboard box on the Job Matrix Page

Thanks,
Jeff

Comment 1 Raymond Mancy 2011-08-19 03:23:48 UTC
Currently when you select a whiteboard and it has too many results in it it will return a warning saying 

"Your whiteboard contains x jobs, only x will be used"

If we have multiple whiteboards it may be tricky to clearly identify
which whiteboard may have had too many jobs and how to identify
from which whiteboard we had to cull jobs?

Or does none of this matter ?

Comment 2 Raymond Mancy 2011-08-19 03:50:57 UTC
Never mind, I won't change how it displays this error at all


Note You need to log in before you can comment on or make changes to this bug.