<!-- 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. --> Several customers have recently requested the ability to easily see how many merge requests a particular user has merged in a particular period of time. While it's possible to collect this data from the Events API (`/users/:user_id/events?target_type=merge_request&action=merged`), having similar functionality in the Merge Request API would be more predictable, especially since we already have filters for other similar parameters (reviewer_id, approver_ids, author_id, etc.). The proposal here would be to add another filter parameter to the `/merge_requests` endpoint, so that this works: ``` /merge_requests?merge_user_id=:user_id&scope=all ``` <!-- 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. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->