### Problem to solve There is a current limitation within GitLab preventing multiple open Merge Requests from the same source branch. In many cases it doesn't make sense to allow multiple MRs from the same source since both would be attempts at merging the same commits, however as a product, GitLab provides a lot of functionality on top of Source Control that could benefit from separation. ### Intended users gitlab-ce~9335216 #### Possible usecases As a user, I want to keep reviews and discussions on the same code diff separate and isolated between teams ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal Remove validation preventing the opening of multiple MRs from a given source branch ### Permissions and Security No change to existing MR permissions ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> Users are allowed to open multiple MRs to separate discussion or dismissal from a given source branch. ### Links / references