<!--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=395633) </details> <!--IssueSummary end--> ### Problem Currently a situation occurs: * in the text of a comment on the source instance there's a mention of a project issue of `TLGA/groupA/projectA#123` gitlab-org/gitlab#23 * the group is migrated to a different target location than on source instance, e.g. `groupA/projectA` Since issues mentioned in the comments are left unchanged during migration, in the migrated comment we see a mention that is not linked OR a link to a different incorrect project. **Clarification**: This is not about linked items, etc. This issue is only about mentions in text fields (issues/comments). **Clarification 2**: This obviously only works for comments, etc. that are within the group that is being migrated. It is not possible to do this for other sub-groups or for later, seperate imports. ### Expected * in the text of a comment on the source instance there's a mention of a project issue of `tlgA/groupA/projectA#123` gitlab-org/gitlab#23 * the project is migrated to a different target location than on source instance, e.g. `groupA/projectA` The mentions are updated to reflect the removal of the top level group (`tlgA`) and now reference `groupB/projectA` without the leading `tlgA`. ### Proposed solution