| Key: |
QB-1643
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Arkady Itkin
|
| Votes: |
7
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 27/May/13 04:24 PM
Updated: 13/Jan/17 02:02 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
7.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Today to prevent child configuration to inherit some promotion, variable etc. once has to redefine it wit empty value.
It makes sense just to have option like "Do not inherit" on some entity to prevent inheritance by children.
I would do it on both parent and child level.
|
|
Description
|
Today to prevent child configuration to inherit some promotion, variable etc. once has to redefine it wit empty value.
It makes sense just to have option like "Do not inherit" on some entity to prevent inheritance by children.
I would do it on both parent and child level. |
Show » |
|
Allow to stop inheritance chain 
* While we also thought about that, we tried a different approach: because if it should not be available in a child configuration, then it presumably should be defined somewhere else maybe? E.g. we created another configuration that is kind of in parallel, and we access variables from there via scripting.