Until recently, when creating a new job by copying a multibranch pipeline, the scan would not be triggered until the new job was actually saved. But now the new job incorrectly gets triggered upon copying, before we have an opportunity to change the configuration. This basically makes the "Copy from" feature useless.

For example, we commonly have multiple copies of a multibranch pipeline, each with a different branch name filter applied. So now when we try to copy an existing job, we have to manually kill all the builds that were implicitly triggered. (The issue is compounded because all the aborted builds then show up as failures in Bitbucket.)