|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Jan/10 06:53 PM
Updated: 21/Jan/10 06:53 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Depending on what you're copying it's possible a schedule might fire soon after the copy has completed. As such, you currently would have to disable all the schedules before copying, copy, then re-enable, or, quickly disable them all after the copy has taken place. It might be safer to disable them automatically during the copy.phase, or somehow all that as an option.
|
|
Description
|
Depending on what you're copying it's possible a schedule might fire soon after the copy has completed. As such, you currently would have to disable all the schedules before copying, copy, then re-enable, or, quickly disable them all after the copy has taken place. It might be safer to disable them automatically during the copy.phase, or somehow all that as an option. |
Show » |
| There are no comments yet on this issue.
|
|
Improvement
Open
Minor
When copying configurations (and their children sometimes) it might be useful to disable any schedules