Red Hat Bugzilla – Bug 534773
"set all values to" skips over unset properties
Last modified: 2014-11-09 17:48:39 EST
if some properties are set, but some are unset (think of a resource that was just recently added to a cluster), i want to be able to use the "set all values to" functionality to make the value homogeneous again. however, when i tried this, it skipped the properties that were unset. i think we need to do one of the following:
1) make "set all values to" also support the "unset" checkbox, so that the unset concept can separately be applied to the property children, or
2) if we don't support the "unset" checkbox at the "set all values to" level, then i think it is more likely than not that users will want the "set all values to" functionality to set values to properties that were previous "unset"
2) is fixed - r3247. There is a separate JIRA for 1).
I cannot find an example of where #2 would apply.
To verify the fix for 2), click on the Members button for a property that is unset. Then, on the members modal, enter a value in the set-all-values-to input at the top of the modal and click Apply. Verify that all the member inputs get updated with the new value and that they're unset checkboxes become unchecked.
Ok, i misunderstood what the fix was for. This is definitely working. rev3351
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1537
This bug relates to RHQ-1642