<!--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=389184) </details> <!--IssueSummary end--> ## Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> As a Gitlab user, I want the issues referenced by a commit be made available to changelog template data so I can include related issues to a release changelog. The template data for the changelog generation endpoint (https://docs.gitlab.com/ee/api/repositories.html#template-data) includes many useful variables such as commit author or the MR that introduced the change, which are very helpful. But for some workflows it would be especially helpful to get the issues closed by that same commit so that it can be included in the changelog. ## 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. --> Add a `issue.reference` variable to the template data for changelog generation. <!-- Please add a label for the type of feature as per https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification -->