<!--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=24740) </details> <!--IssueSummary end--> ### Problem to solve When a project is managed through issues, it is often very complicated to get a hold of what issues had been fixed since the last and the current release. ### Further details The goal is to make it easier for projects with a long time inbetween releases, or for projects für just a view developers, to manage a changelog by providing them with a list of closed issues. ### Proposal Jira and YouTrack already have this feature. They create a changelog based on the Issues closed since a release. That is very helpful if you have a lot of issues to fix and need a changelog listing all of them. So my proposal is, that Gitlab shoud log which issues where closed and provide a changelog based on the title of the issue, the id of the issue as well as ordering them by label. The labes then should also have a flag to allow them to be used to group the changelog. Format (Markdown): ```markdown **Bug** * [#29](https://gitlab.atvg-studios.at/atvg-studios/ATVG-CAD/issues/29) Cant change Password ``` ### What does success look like, and how can we measure that? A good way to measure success is by compering Gitlab with Jira's and YouTrack's implementation. ### Links / references Documentation of Jira: https://confluence.atlassian.com/adminjiraserver071/creating-release-notes-802592502.html Documentation of YouTrack: https://www.jetbrains.com/help/youtrack/incloud/Create-Release-Notes.html ---- **Quick note**: I requiest that this will be a CE feature, if it will be a feature.