<!--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=339221) </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. --> GitLab currently supports [closing a Jira issue](https://docs.gitlab.com/ee/integration/jira/issues.html#close-jira-issues-in-gitlab) when a merge request is merged to a [default branch](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/project/repository/branches/default.md). A customer is currently requesting to have the feature extended to a non-default branch so that the Jira issue can be closed using the `Closes` keyword [Zendesk Ticket](https://gitlab.zendesk.com/agent/tickets/225558) (Internal Only). <!-- 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. -->