Bug 534778 (RHQ-1541)

Summary:	unchecking "unset" at the aggregate leaves drill-down properties read-only
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:	high
Version:	1.2	CC:	ccrouch, dajohnso
Target Milestone:	---	Keywords:	SubBug
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1541
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 20:09:00 UTC

steps to reproduce:

* edit from group config
* find some property that is currently "unset" at the aggregate
* uncheck that, notice that the value space becomes editable at the aggregate
* click the corresponding members button

expected results:

* all individual properties are editable

actual results:

* all individual properties are still read-only, as if the drill-down component wasn't notified that "unset" was unchecked at the aggregate level

Comment 1 Ian Springer 2009-02-12 21:06:00 UTC

This one's going to be fairly complicated. Coordinating the unset controls between the main page and the modal panel is complicated because of the JavaScript that is rendered to initialize the unset checkboxes.

Comment 2 Ian Springer 2009-02-27 22:39:02 UTC

I must have fixed this at some point in the past week. I'm not sure exactly which revision(s) fixed it, but it is working as of r3143.

Comment 3 Jeff Weiss 2009-03-11 15:44:42 UTC

Fixed, rev3351

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

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1541