Update the target branch after the target project changed in a new Merge Request
Summary
The target branch is not updated when the target project is changed in a new Merge Request.
Steps to reproduce
Prerequisite
- Prepare two project in different namespaces: the original and its forked.
- One project has
dummy
branch as default branch while the other hasmaster
branch as default branch.
Steps
- Access to New Merge Request page like https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/new .
- Change Target Project from the selected to other.
- You can't get the appropriate branch (that is default branch) for the new Target Project in
Target Branch
due to unchanged from the branch default to the project previously selected.
Expected behavior
Always update the target branch after the target project changed in a new Merge Request
Actual behavior
The target branch is always unchanged even after the target project changed in a New Merge Request.
Relevant logs and/or screenshots
target-branch-selection-in-mr-from-forked-project-gitlab
Output of checks
This bug happens on GitLab.com as well as GitLab 8.15.
Possible fixes
Force update the target branch when the target project is changed in a New Merge Request.
Edited by 🤖 GitLab Bot 🤖