Allow Custom Issue Tracker to parse issue id as two fields

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Problem to solve

The current logic of Custom Issue Tracker does not allow to mention issues from two different projects.

Target audience

Any developer who wants to mention different projects's issues in one merge request/comment via Custom Issue Tracker.

Further details

There is a number of cases when I need to refer PROJECT1-111 and PROJECT2-222 in one merge request in PROJECT1 repository. With Custom Issue Tracker I can link PROJECT1 issues only, cause the hyperlink "PROJECT2-222" will literally lead to PROJECT1-222. This is because of the way GitLab parses the url to issue: https://customissuetracker.com/project-name/:id.

Proposal

Add an ability to parse id as a pair of PROJECT-internal_id, optionally with delimiter choosing. With that, both links like https://customissuetracker.com/issues/PROJECT1-111 and https://customissuetracker.com/issues/PROJECT2-222 will be valid in one comment.

What does success look like, and how can we measure that?

Links to issues from different projects are valid in one commentary.

Links / references

Edited Jun 27, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading