Task Scope Should not default to 'All Systems'
10
votes
When building a new Task, the default scope should be 'No systems'. To say, Tasks should be Opt in, rather than the default of out.
The current default is risky, especially for new customers, who may accidently push tasks to machines by accident.
This simple change would significantly reduce the risks of errors.
Comments: 1
-
05 Apr, '22
Matthew SteinAgreed. Automation should default to "none" vs all and the admin should have to make selections manually and verify them, even to the point of running a non-execute test to see what systems will be affected by the intended process. Very dangerous in the current mode.