This is the third regression we found after upgrading the "Pipeline: Multibranch" plugin from 2.9.2 to 2.14

In version 2.9.2, jobs got automatically deleted once the remote branch got deleted and thus disappear from the branch list.

Since version 2.14 those jobs are not deleted but rather changed to "disabled" and stay on the branch list.

We would like the have the option to configure the original behavior. We did not find any such option on the configuration page.