Handle merge requests that cannot be closed in the MR homepage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

Provide a filtering or a workaround to exclude merge requests that users don't want to see in their MR homepage even though they are the author/assignee on it.

Problem

There are scenarios where users are unable to close their merge requests so it ends up cluttering up their MR homepage and thus making the count and page unusable.

Existing authored MRs may never be closed

@marcel.amirault A separate issue is that I sometimes create test MRs to validate issues, but I want to keep them open so that others who are reading through old issues can still access the test MR. For example, this MR is demonstrating pipelines with specific edge case job names. It's for a related issue that has not been completed yet, but it's still going to be worked on eventually. I don't want to close it, but am not working on it and will not be assigning anyone to it. It wouldn't be all that annoying if I could set Draft: and have that ignored in the list, but that doesn't work (I already have a few drafts showing up in the list).

Cannot close read-only MRs

From @thiagocsf #547449 (comment 2557753462)

I can't close this merge request: https://gitlab.com/devsecops-pipeline-proposals/deploy-on-tag/-/merge_requests/8

How do I remove it from my list of MRs? https://gitlab.com/dashboard/merge_requests

I've tried removing the extra users so it's under the limit, but apparently this goes on a queue and can take a while.

I happened to have permissions to do this. What happens to users who don't? Will they be stuck with some MRs on their queue?

Other scenarios

• @eduardobonet MRs for technical reviews (no the MRs used by a candidate, but the MR used to generate the interview challenge)
• @eduardobonet MRs that I created, but have been taken over by other people