[Feature Request] Prevent issues from being closed by merging linked PRs

I really like how the linked PRs in an issue are listed nicely on the project board as well as in the right side of the issue. It really makes discovering PRs from issues easy.

In my current project, we don’t close issues until they reach production. Also, often we have multiple PRs which fix an issues (in multiple repositories). In such cases I do not want the issue to be autmatically closed, currently I just re-open them. This is not ideal because I could forget to re-open the issue and also this workflow causes a lot of notification noise in my team.

It would be nice if this could somehow be configured, or if there was another keyword (instaed of fixes, closes, etc.) to signify that a PR only partially fixes an issue and the issue and the issue must not be closed auotmatically even after the PR is merged.


Hi @akshaymankar,

Thanks for this feedback! We’re always working to improve GitHub, and we consider every suggestion we receive. I’ve located an existing “feature request” for disabling the auto-close issues feature and added your voice to it.

Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Was this solved? I’ve the same problem and I would like to know if this feature request was applied or where can I see this feature request.

I really expect this feature as it is one primary use case where developer fix has to be verified by QA


This should be made with another keyword like for instance ‘Linked to #123

You can link issues without using an auto-close keyword. Just use org/repo#issue_number Ex: OWASP/OWASP-VWAD#1

I guess technically you won’t see them in that little “Linked issues” area in the PRs but you’ll still see the reference in the PR message and in the Issue history/log.

Hi @andreagriffiths11,

Can you provide a link to the existing feature request?


1 Like

Not using a github keyword such as fix is not a viable option if the commit text format is already specified and well established. An option to disable auto-closing would be preferable.

1 Like

Agree, issues should never be closed before a release, since the issue still exist in the latest release, and it can take a long time before a new release with the fix applied is made.

Has there been any progress on this issue?
Can someone please update the feature request link or status?