I have a Multibranch project with multiple branch sources:
repo1 (having XXX branch)
repo2 (having XXX branch)
repo3 (having XXX branch)
I have 'include branches' property set to: XXX
When branch indexing gets triggered it scans repo by repo.
1st run is always fine as it is a brand new pipeline so it gets triggered anyway.
2nd run:
I pushed a change to XXX branch in repo2. This is how scanning looks like:
repo1
Met criteria
No changes detected in XXX (still at a9d6eac10fcd2c070a6bef80b1340139852d8947)
repo2
Met criteria
Ignoring duplicate branch project XXX
repo3
Met criteria
Ignoring duplicate branch project XXX
= job doesn't get triggered

When we work on a feature which involves changes in different git repos we create branches with the same name across all git repos.
We'd like to be able to trigger a build on any change to any of those branches (repos). I'd see it as a on/off feature 'react on each branch source change' and if it'd be ON then:
for each source branch
– if criteria met (XXX branch found)
---- if changes found (hash changed)
------ plan to trigger a new build
---- fi
– fi
done
Just do not ignore scanning for changes in 1st+n source branches when criterias are met for the 1st source branch.
If a change will be found across all source branches it should end up with only 1 build of course.

This feature would really make Mulitbranch pipeline work the way we need.
That's the only behaviour we miss to get our CD to work.