The GitLab for Jira plugin, installed manually on Jira Cloud, does not link merge requests from forks when the branch names in the fork and origin are identical.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
The GitLab for Jira plugin does not link merge requests (MRs) from forks when the branch names in the fork and origin are identical.
I have the GitLab for Jira plugin installed on my Jira Cloud instance, following the instructions from Install the GitLab for Jira Cloud app manually. The GitLab instance is self-managed.
My workflow involves developers creating code in their forks and submitting merge requests to the origin repository.
I encountered an issue where, if the branch on the fork and the branch on the origin have the same name, the MR from fork:branch to origin:branch does not appear in Jira. However, if the branch names are different, the MR is correctly displayed in the related Jira issue.
Steps to reproduce
- Have a branch named main in the origin repository.
- Create a branch named main in the fork repository.
- Commit and push changes to fork:main with a message referencing a Jira issue, for example, XYZ-123
- Create a merge request (MR) from fork:main to origin:main.
What is the current bug behavior?
- At https://XXX.atlassian.net/browse/XYZ-123 I dont see created MR
What is the expected correct behavior?
- At https://XXX.atlassian.net/browse/XYZ-123 I see created MR