Is there a GraphQL equivalent of the "closes_issues" API for merge request?


While creating a tool to query information about merge requests and the issues that they close, I have seen performance issues with the /projects/:id/merge_requests/:merge_request_iid/closes_issues API. My tool reads all the issues closes by all the merge requests that a given user has access to, so the total number of API calls required is very large.

I think that this is a similar issue to what was reported in #15027.

Is there a way to use GraphQL to get the same information? I’ve looked at the specification but haven’t been able to find anything there that links merge requests to issues.

Should I create an issue to raise this?