<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=365266) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=365266) </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. --> <!-- 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. --> Merge request descriptions can now be pre-filled, either - from commit message/branch name (with issue to be closed and a description from the commit, if available) - from a default merge request template The resolution of https://gitlab.com/gitlab-org/gitlab/-/issues/353548 should change the precedence from the former to the latter. Regardless of the precedence, using a default merge request template now means that the automatically inferred issue number (and description) is lost. As suggested by @fibbo_ch in https://gitlab.com/gitlab-org/gitlab/-/issues/353548#note_934180259, this could be solved by making this available as some variable in the templates, e.g. `${CLOSES_ISSUE}`.