<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=479155) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Currently, it's possible to set a default template on the source branch: https://docs.gitlab.com/ee/user/project/description_templates.html#create-a-merge-request-template This feature proposal aims to introduce an automated system for selecting merge templates based on the target branch specified in a merge request. The goal is to streamline the merge request process by reducing manual intervention and ensuring the appropriate template is applied based on the target branch. Currently, users need to manually select the appropriate merge template when creating a merge request. The proposal is to implement a feature that allows users to define a list of merge templates, each associated with specific target branches. When a user creates a merge request, the appropriate template will be selected based on the target branch of the merge request. For example, a customer has a template named `release_template` that should be used for any merge requests targeting the `release` branch. When a user initiates a merge request with the target branch set to `release`, the `release_template` will be automatically selected. This came up in a [zendesk ticket](https://gitlab.zendesk.com/agent/tickets/551996) - internal only PM to mention: @gweaver <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->