Ref: https://github.com/opf/openproject/pull/21932

Begin of the insertion### Steps to reproduce

Reproduces with the GitLab integration (the GitHub integration shows the same classEnd of the insertion Begin of the deletion **As** a \[enter roleEnd of the deletion of Begin of the insertionmislinking):End of the insertion Begin of the deletion user\]
**I want to** \[enter objective\]
**so that** \[enter desired result\]End of the deletion

Begin of the insertion1. Connect **two** GitLab repositories (*Repo A*End of the insertion Begin of the deletion **Acceptance criteria**

* <br>


**Technical notes**

* <br>


**PermissionsEnd of the deletion and Begin of the insertion*Repo B*) to the same OpenProject instance.
2. In *Repo A*, open merge request `!5` referencing a work package, e.g. `OP#100`.
3. In *Repo B*, open merge request `!5` (GitLab numbers merge requests per project, soEnd of the insertion Begin of the deletion visibility considerations**

* _To whom isEnd of the deletion this Begin of the deletion feature visible?_

* _WhenEnd of the deletion is Begin of the insertionalso `!5`) referencing a different work package, e.g. `OP#200`.
4. Let both `merge_request` webhooks reach OpenProject.End of the insertion Begin of the deletion it not visible?_


**Translation considerations**End of the deletion

Begin of the insertion### What is the buggy behavior?

A webhook for *Repo B*'s `!5` matchesEnd of the insertion Begin of the deletion * _Key termsEnd of the deletion and Begin of the insertionoverwrites the record created for *Repo A*'s `!5`, because the lookup matches on the per-project merge request number (GitLab's internal ID, `iid`), which is `5`End of the insertion Begin of the deletion phrasesEnd of the deletion in Begin of the insertionboth repositories. Work packages then link to a merge request fromEnd of the insertion the Begin of the insertionwrong repository — e.g. `#100` shows *Repo B*'s merge request — and the link flips back and forth as each repository's webhooks arrive. The same affects issues, pipelines and comments. There is no error; the linking is silently wrong.End of the insertion Begin of the deletion key languages_&nbsp;


**Out of scope**End of the deletion

Begin of the insertion### What is the expected behavior?

Each merge request, pull request and issue is identified by its unique webhook URL rather than a number that repeats across repositories. *Repo A*'s `!5` links onlyEnd of the insertion Begin of the deletion * <br>


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the insertion`#100`, *Repo B*'s `!5` links onlyEnd of the insertion Begin of the deletion include all teams necessaryEnd of the deletion to Begin of the insertion`#200`, and pipelines/comments attach to the correct repository's record.

### Environment

Server-side bug in the GitHub/GitLab integration modules — independentEnd of the insertion Begin of the deletion be informedEnd of the deletion of Begin of the insertioninstallation type, browser, OS and language. Present in all current versions whenever more than one repository is connected; reproduced onEnd of the insertion the Begin of the insertionlatest `dev`.
End of the insertion Begin of the deletion changes._End of the deletion