
Key: |
QB-30
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Minor
|
Assignee: |
Robin Shen
|
Reporter: |
Robin Shen
|
Votes: |
5
|
Watchers: |
2
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 06/Mar/06 03:33 PM
Updated: 06/Feb/07 11:33 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
One think I thought it would be nice to have is the ability to push-up/down part of a configuration to a parent/child configuration. E.g. You have defined a repository at a higher level, and you want to push it down to a child configuration. Right now you have to completely redefine the repository, but if you could just push a button and have it automatically copied to a (selected) child config, it would be useful. This concept could be applied to notifier, steps etc. I know that some of the need for redefining steps can be removed by defining variable, using these at the higher level, and just overloading these in the child configuration, but I think the idea is still useful.
|
Description
|
One think I thought it would be nice to have is the ability to push-up/down part of a configuration to a parent/child configuration. E.g. You have defined a repository at a higher level, and you want to push it down to a child configuration. Right now you have to completely redefine the repository, but if you could just push a button and have it automatically copied to a (selected) child config, it would be useful. This concept could be applied to notifier, steps etc. I know that some of the need for redefining steps can be removed by defining variable, using these at the higher level, and just overloading these in the child configuration, but I think the idea is still useful. |
Show » |
|