<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=460201) </details> <!--IssueSummary end--> ### Proposal As discussed [here](https://gitlab.com/gitlab-org/security-products/analyzers/report/-/issues/17#note_1891148484), we'd like to use the `Create issue to resolve thread` option when reviewing merge requests, however, we don't want to use the project's issue tracker, but instead use the [gitlab-org/gitlab issue tracker](https://gitlab.com/gitlab-org/gitlab/-/issues). The purpose of this issue is to add a new project configuration option, possibly at the following path: ```shell . └── Settings/ └── General/ └── Visibility, project features, permissions/ └── Issues/ └── Use another project's issue tracker ``` This option should allow us to specify another GitLab project's issue tracker, which will be used when creating issues via the `resolve thread into follow-up issue` in merge request comments: {width=40%}