Short : When i want to create a MR from the issue UI and have already the branch created, gitlab create a new branch, and not reuse the already existing branch. Long : I use this simple workflow. - Gitlab : Create issue 'test' - Gitlab : Create branch on it (only branch ; keep default name) '11-test' - Workstation : i create my code on my computer in the branch and push commits when finished - gitlab : i create the MR from issue panel --> he creates a MR but linbked to a new branch created : MR='5-test' new branch='11-test-2' => the MR is linked to a useless branch and my commits are not included in the MR. Current Workaround : I create the MR from the Branch panel/view Here is an example of what is done by default :  Wanted : when we create a branch for the issue (and even not change the default proposed name), we should be able to create the MR with the alredy associated branch. ////////// current test : GitLab Community Edition 11.3.6 gitlab-ce@3c1fdf6b5fd478d395b13b3b40ab3d1de20ed7e1 (Omnibus on Debian 7) Note : i think i had not this problem when starting to test Gitlab some monthes ago, before i create the internal documentation for this workflow like in the "wanted" block. but i can't say when this appears. Note 2 : if not clear, ask more infos (not english native here).