<!--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=385463) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ## Problem MR and issue URL references aren't supported in file-based export-import. When exporting a project that contains issues with "related Merge Request" labels these are not shown on the imported issue. The association exists but the relationship does not appear on the issue from the UI. #### To observe current behaviour 1. Create a project. 1. Create a new branch in the project. 1. Create a new issue in the same project. 1. Create a new MR and in the description of this MR write `"Closes #1"` 1. Export the project 1. Import the project to a new namespace/instance   An example project can be found [here](https://gitlab.com/gitlab-gold/mmora-gold-subgroup/mr-related-import/-/merge_requests/1) ## Proposed solution Issues that had related MRs should show these relations the project had been importer by file export. Desired behavior