Bug 961194

Summary: group should be unconditionally displayed on the job page
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: web UIAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: Nick Coghlan <ncoghlan>
Severity: unspecified Docs Contact:
Priority: high    
Version: developCC: asaha, dcallagh, llim, qwan, rglasz, rmancy
Target Milestone: 0.13Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-25 06:25:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Callaghan 2013-05-09 05:15:51 UTC 
Currently if a job does not have a group, the "Group" field is not displayed at all. This may be confusing for users. The "Group" field should always be displayed, just empty if no group is defined.

It may also be worth rearranging the fields near the top of this table to use space more effectively (e.g. Group and CC in the same row, or Group and CC moved into a fourth column alongside Owner and Job Id).
Comment 1 Dan Callaghan 2013-05-22 01:43:41 UTC 
On Gerrit: http://gerrit.beaker-project.org/1960
Comment 3 Nick Coghlan 2013-05-27 06:52:55 UTC 
Verified that the group field is shown regardless of whether or not the job is associated with a specific group, and that the field is empty in the latter case.
Comment 5 Amit Saha 2013-06-25 06:25:15 UTC 
Beaker 0.13.1 has been released.