History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-54
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Robin Shen
Reporter: Robin Shen
Votes: 6
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Display effective configuration property values when browsing when editing

Created: 16/Mar/06 02:47 AM   Updated: 25/Jun/10 09:37 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
 
This issue is duplicated by:
QB-157 Display inherited elements (steps, bu... Major Resolved


 Description  « Hide
I created some configurations tree. Like this:
root
department1
project1
product1
productline1
continouos
QA
release
productline2
continouos
QA
release
....
I share some objects (Builders, Variables, Repositories etc.) among configurations in the tree. I've found that it's very difficult to determine which property values have dose shared objects. For instance if I set variable debug=true in the root I cannot see this fact in child configurations. I should go back throug the tree to find last value I set to the variable. The same with almost everything.
Possible solutions:
1. I should see all effective object property values for every object in current configuration during browsing. If I try to edit some object I should have edit fields disabled and effective property value specified. Near from the field (let's say on the right side of edit box) I should have checkbox "Inhired parent value" checked. If i like to change the value I should cleare checkbox and specify new value.
This solution is more complicated to implement but seems like more clear and intuitive.
2. I should see all effective object property values for all objects in current configuration using some special report "Effective configuration's settings".
This solution is more easy to implement and it is quite enough for me.

Thanx
_________________
Mikhail Yakushkov (aka Mike Eshva)

 All   Comments   Work Log   Change History      Sort Order:
Chad Boyd [05/Oct/06 11:33 AM]
I think what I want is related to the above comment. Let's say you have a configuration named "config1" under the root configuration. In the root configuration you've defined a property "foo" and have given it the value "bar". When you trigger the build for "config1" it would be nice to see the property "foo=bar" in the "Override variables" text area so you would know that this property existed and what the current value of the property is in case you wanted to change it. As it is now, you would have to already know that there is a property named "foo" in order to override it.

Robin Shen [25/Jun/10 09:37 AM]
All inherited settings will be displayed in child configurations in 3.0