When a multibranch pipeline job is cloned it gets scanned immediately - even before the job configuration is saved. As a result builds may be kicked off that would of otherwise been ignored after the user had a chance to modify the git branch configuration such as changing the branch include filter.

Expected Behavior
New job is not scanned until after the configuration is applied/saved.

Actual Behavior
A scan is started and new builds are launched before the user has a chance to modify the job configuration.

Steps to Reproduce

1. Create a multibranch pipeline job with some branches. Run a scan and let builds complete.
2. Clone the job that was created above. Do not click save.
3. In another tab look at the build queue and agent build executor status. Observe builds are being immediately launched.