Pagination / Better Filters for Merge Requests Page
Description
The Merge Request Pages are kind of difficult to navigate when there are many merge requests. LEx: 40 Merge Requests. Sometimes the "Suggest" filter doesn't pull the intended Request.
The Filters currently Present are by Name, Last Updated and Oldest Updated . Sometimes these make it harder . Most of the cases the Last Updated or Oldest Udpated is more useful that Name.
No easy way to identify What is Merged vs Not Merged . A filter for this would be good. As mentioned in the first point If there are 40 Merge requests it is kind of difficult to filter the one which are merged vs not merged.
Proposal
- Have a Pagination for Merge Request Page where a user can easily navigate back and Forth
- Additional Filter "Merged" vs "Not Merged"
- Remember the last sort
Links / references
Documentation blurb
(Write the start of the documentation of this feature here, include:
- Why should someone use it; what's the underlying problem.
- What is the solution.
- How does someone use this
During implementation, this can then be copied and used as a starter for the documentation.)
Activity
Additional Filter "Merged" vs "Not Merged"
There is an issue for that: #13650 (moved) Filter merge requests that are marked WIP
Remember the last sort
Could you explain this proposal, please?
Is it related to #29248 (moved)?
@rupak What version of GitLab are you using? Merge Requests has been separated by "Open" and "Merged" for quite some time:
I'm not sure how that could be made much clearer
@ @markglenfletcher , @blackst0ne Apologize for the confusion. It was actually Branch Page not Merge Request Page . Should i close this ticket and open a new one for it. Merge Request Page works perfectly.
Edited by username-removed-399435-
Yes please. If you could open a new issue with your thoughts for branches. Though before you do, please read over the following issues first to see if the changes proposed there would meet your needs: