Bug 534771 (RHQ-1535)

Summary:	"unset" checkbox is checked if ANY of the properties are unset
Product:	[Other] RHQ Project	Reporter:	Joseph Marques <jmarques>
Component:	Configuration	Assignee:	Ian Springer <ian.springer>
Status:	CLOSED NEXTRELEASE	QA Contact:	Jeff Weiss <jweiss>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.2	CC:	ccrouch, dajohnso
Target Milestone:	---	Keywords:	SubBug
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1535
Whiteboard:
Fixed In Version:	1.2	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:	534605

Description Joseph Marques 2009-02-11 19:39:00 UTC

i guess this issue is up for debate.  what should the logic be if some of the properties are unset, but not all of them.  obviously if all of them are unset, then the aggregate should be unset.  likewise, if all properties have values, then the "unset" checkbox should be grayed out for the aggregate.  but if some are unset while others have values, should we also say "Member Values Differ" in the unset column too?

Comment 1 Joseph Marques 2009-02-11 20:02:31 UTC

another consequence of this is that when the member values are different, the unset checkbox on the aggregate does nothing.  ideally, i'd like the unset checkbox to clear all of the properties regardless of whether some or all of them have current values set on them.

Comment 2 Ian Springer 2009-02-12 14:33:40 UTC

r3025 deselects and disables the unset checkbox on the main page for properties whose members have differing values. So, for now, if you want to unset all member values on a property that currently has differing member values, you have to go to the drill-down page to do it. 

Enabling the unset checkbox on the main page would not be trivial, since, when the member values differ, there is no input control or EL expression associated with the property. I think this is something we can revisit post 1.2. Joe, if you disagree, you can re-open, but I would at least change the priority to Minor.

Comment 3 Jeff Weiss 2009-03-12 17:48:55 UTC

Verified behavior is as specified in previous comment.  rev3351

Comment 4 Red Hat Bugzilla 2009-11-10 20:35:07 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1535
This bug is related to RHQ-1538