Include the default "Closes" information when using an MR description template from the project or group-level configuration

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

It will be possible (or always the case) to include the "Closes" (issue) information in an MR description when using a group- or project-level MR description template.

What happens now (incorrect behavior):

• Put an MR description template in .gitlab/merge_request_templates
• Create an Issue
• Create an MR from the Issue using the "Create MR from this Issue" button - the MR description has "Closes" and the issue number
• Go to the MR and choose your MR description template

"Closes" and the issue number disappears. We'd like to be able to keep the issue reference.

Current state:

Intended users

User experience goal

Proposal

One of the following:

1. "Closes" and the issue number stays in the description, at the end after the template
2. There is some template language that allows us to include "Closes" and the issue number in the template
3. We can choose a template when first creating the MR, so that "Closes" and the issue number can be included automatically at the end - this is how it works with the "default" merge request template.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

What is the buyer persona for this feature?

• Alex - The Application Development Manager
• Dakota - The Application Development Director
• Erin - The Application Development Executive
• Kennedy - the Infrastructure Engineering Director
• Casey - the Release and Change Management Director

Is this a cross-stage feature?

Yes. It connects Create with Plan, in a way that impacts Value Stream Analytics.

Links / references

/cc @danielgruesso @cupini

Requested by a 200-user Premium customer