<!--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=321449) </details> <!--IssueSummary end--> <!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes In the merge request dashboard there are many search filters you can apply, author, reviewer, deployed-before, etc. I would like to have "Group" and "Project" added to that list. It would be useful to be able to search for these when trying to sort through a very large list of MR's. Project isn't as useful as Group, since project can be searched while in the project, but it's more clicks the right from the dashboard. ### Intended users Anyone who spans multiple groups/projects would benefit. ### Permissions and Security Permissions would only be enforced on the search results level. if the user has no access, don't show it.