Bug 676762

Summary: Schedules in a group context appear duplicitous, ambiguous
Product: [Other] RHQ Project Reporter: Corey Welton <cwelton>
Component: Core UIAssignee: Ian Springer <ian.springer>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0.0CC: ccrouch, ian.springer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 585306, 676752    
Attachments:
Description Flags
screenshot none

Description Corey Welton 2011-02-11 03:48:00 UTC 
Description of problem:
In the a group context, there might be multiple, similar monitoring schedules for resources across a group. As they are 'flattened', it is difficult, if not impossible, to determine which schedule line items refers to which resource in a group.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Install JON and agent on a linux system.  Inventory this system.
2.  Add this resource to a compatible, recursive group called "Linux"
3.  Navigate to $group > Monitoring > Schedules
  
Actual results:
Many apparent duplicate rows.  

Expected results:

Some way to better determine what parent resource this schedule line item belongs to?  Maybe in a tooltip?

Additional info:
See forthcoming screenshot
Comment 1 Corey Welton 2011-02-11 03:50:29 UTC 
Created attachment 478175 [details]
screenshot
Comment 2 Ian Springer 2011-02-15 15:50:06 UTC 
The issue here is that schedules for all recursive/implicit members are being displayed. We should only show the schedules for the top-level/explicit members.
Comment 3 Ian Springer 2011-02-15 21:13:33 UTC 
Fixed in master via commit 66626bd.
Comment 4 Corey Welton 2011-03-01 14:34:26 UTC 
Verified.
Comment 5 Corey Welton 2011-05-24 01:13:35 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 6 Corey Welton 2011-05-24 01:13:35 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 7 Corey Welton 2011-05-24 01:13:38 UTC 
Bookkeeping - closing bug - fixed in recent release.