Thank you for raising this: the current plugin is tightly coupled at the moment with the Jenkinsfile pipelines, which are tried to a single repository.
I believe your use-case would still make sense if a top-level repository (i.e. the super-project) would be used as common collector of all changes across repositories. Then the top-level repository could have a Jenkinsfile associated and that could get the subprojects tied to a topic.
I wonder if this is supported now, do you have any updates about this topic?
Thanks in advance.
Edit#1: I've also changed the ticket priority to be blocker, as in my team we're working with this paradigm mentioned in the ticket description and we want to add the Jenkins verification functionality to the sub-module code review. And this is crucial for us to move on.
I believe this is more a problem on the multi-branch pipeline concept in Jenkins: where would the Jenkinsfile be stored? one repo? both? Where would you fetch the pipelines from?