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?
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.
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.
Verified behavior is as specified in previous comment. rev3351
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1535 This bug is related to RHQ-1538