Created this issue because an email was sent to the authors, to no avail (two addresses bounced, please also consider updating the contact details at https://plugins.jenkins.io/rebuild).

Our Jenkins (v 2.32.3) is successfully configured to run a job upon a GitLab merge request.
 
However, when we hit the Rebuild button of such a job (in our example job 55), a different branch (i.e. master) is being built (for job 56)

one would expect that at least the merge request SHA1 would be re-used.
 
the screen shots also show different build input information.
 
 
Maybe we are misunderstanding the purpose of the plugin?
 
(I've highlighted the associated commits if that can help - it mainly shows that the rebuild uses the master branch).
  | | * 7f2cb10 (LAH-533-jk-merges) test
| | * 6040553 test
| | * 07f7bff test
| | * 7d99599 LAH-533 JK branch
| |/  
|/|   
* |   fc4cbc0 Merge branch 'LAH-532-fix-test-suites' into 'master'
|\ \  
| * | 7bcf795 optional arguments are not required by default.
| * | b6efac2 (tag: job/55) Fixed ansible tests.
| * | 29ef9a6 Rename doc to docs
|/ /  
* |   9072bf5 (tag: job/56) Merge branch 'LAH-531-TP-merge' into 'master'
|\ \  
| * \   2936294 Merge branch 'LAH-343-vm-ip' into LAH-531-TP-merge
| |\ \