Select the pull down from "Create merge request". "Create merge request and branch" is selected.
Enter a "Branch name". We prefix our branch names for example "feature/1234-new-feature".
Click "Create merge request"
Expected:
New branch and MR is created with the prefixed branch name, for example "feature/1234-new-feature".
Actual:
A new branch and MR is created without the prefixed branch name, for example "1234-new-feature".
This problem seems intermittent. I've managed to get the branch name to be created correctly sometimes. But I can't quite find the right timing, field selections, or incantations to cause the branch be created correctly.
Which Group/Project (with full path) is experiencing the issue?
All of the repositories in gitlab.com/etagen-internal (All private repositories.)
Approximate date/time when the error occurred.
2020-03-28 10:00AM PST -- twice for two different issues.
Describe what you were doing right before the issue occurred.
Nothing interesting.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
This issue will be moved to the GitLab issue tracker because it relates to a bug in the product and not specifically a problem with the GitLab.com service
@duane.murphy do you happen to have a branch that is named feature?
I can't reproduce the branch being created with the 1234-new-feature, but I can reproduce this failing if I already have a branch named whatever the prefix I use is (feature in this example)
I also found a bug that prevents us from returning the actual error message, which I will put up a merge request to fix shortly.
I've run into the prefix branch name before. We do not have that problem in this case. We have many many (100's) of branches prefixed with feature/.
In my experience, my entries into the fields are simply ignored. No errors. Just create the branch name and use the target branch that were default.
This may or may not be related, but I also have cases where the "Source (branch or tag)" field is also ignored. )This almost caused a merge into the wrong branch!)
I wonder if this is a frontend problem. Can you provide your browser information? I am seeing an event in our logs from around that time, from you attempting to create the branch and merge request, but there are no slashes in the request. I wonder if somehow, that information is getting stripped before the request is even made.
Probably too late now, but perhaps next time, you can see if your browser console captures any errors that may help diagnose!
That's what I think is happening. The UI seems to change in odd and interesting ways. The branch name will change back, the completion is a little different than other interfaces and doesn't take if I'm not careful.
Chrome on Mac OS
Version 80.0.3987.149 (Official Build) (64-bit)
I don't know if it is related, but from my experience, when creating merge request with different source branch than master, I am getting this problem, that the default branch name is created instead of custom one. These are my findings that seem to be consistent, hope it helps:
When first changing branch name and then source branch, the default branch name is created.
When first changing source branch and then changing branch name, the correct branch name is created.
Tested with Chromium and Firefox, giving same results.
Contributions like this are vital to help make GitLab a better product.
We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.
This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.
Thanks for your contributions to make GitLab better!