|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 20/Jan/15 12:56 PM
Updated: 20/Jan/15 12:56 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
6.0.4
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
All
|
|
|
In the current implementation, when a step is disabled it becomes a local (override) instance automatically (presumably so disabling in one configuration does not affect another). It would be better if the enabled state of a step were made independent of inheritance. Now, the user needs to remember to delete the override when re-enabling a disabled step if the inherited step is desired. It would be better if inheritance were not affected.
|
|
Description
|
In the current implementation, when a step is disabled it becomes a local (override) instance automatically (presumably so disabling in one configuration does not affect another). It would be better if the enabled state of a step were made independent of inheritance. Now, the user needs to remember to delete the override when re-enabling a disabled step if the inherited step is desired. It would be better if inheritance were not affected. |
Show » |
| There are no entries against this issue.
|
|
Improvement
Open
Major
Enabled/Disabled state of a step should be made independent of inheritance 