<!--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=221036) </details> <!--IssueSummary end--> ### Problem to solve We develop using more than one release branch. When we merge into the `master` branch, using the [Closing issues automatically](https://gitlab.comelz.com/help/user/project/issues/managing_issues.html#closing-issues-automatically) feature, the issue is automatically closed. But when we merge into a different branch (usually a protected branch for each supported release) the issue is not closed. ### Intended users Both developers, TL or PM, adds a burden to manually update some issue is some case and not others. ### User experience goal Offer a coherent behavior for users using more than one release branch. ### Proposal Add an option to close any issue merged into a **protected branch**, not only the default one. ### Documentation Update this page: https://gitlab.comelz.com/help/user/project/issues/managing_issues.html#closing-issues-automatically