-
New Feature
-
Resolution: Fixed
-
Minor
-
None
When i create a new job by using "Copy existing job", the copy is active and can potentially run, while I'm still busy changing it on the Configure page.
That can cause unwanted effects, for example if that job manipulates external resources, which will now happen twice.
Expected:
The copy should be disabled till I first save it from the configuration screen.