BigW Consortium Gitlab
Sensible state specific default sort order for issues and merge requests ## What does this MR do? It provides more sensible default sort order for issues and merge requests based on the following table: | type | state | default sort order | |----------------|--------|--------------------| | issues | open | last created | | issues | closed | last updated | | issues | all | last created | | merge requests | open | last created | | merge requests | merged | last updated | | merge requests | closed | last updated | | merge requests | all | last created | ## Are there points in the code the reviewer needs to double check? All the bits where `id_desc` was changed to `created_desc`. I hope it's okay, It makes more sense in my opinion. ## Why was this MR needed? Prior to this MR the issues and merge request were sorted based on `id_desc` by default. This MR aims to make the interface more user-friendly by providing state specific sorting defaults most users would expect. ## What are the relevant issue numbers? See #15064 See merge request !5453
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
_closed_by_box.html.haml | Loading commit data... | |
_discussion.html.haml | Loading commit data... | |
_form.html.haml | Loading commit data... | |
_head.html.haml | Loading commit data... | |
_issue.html.haml | Loading commit data... | |
_issue_by_email.html.haml | Loading commit data... | |
_issues.html.haml | Loading commit data... | |
_merge_requests.html.haml | Loading commit data... | |
_new_branch.html.haml | Loading commit data... | |
_related_branches.html.haml | Loading commit data... | |
edit.html.haml | Loading commit data... | |
index.atom.builder | Loading commit data... | |
index.html.haml | Loading commit data... | |
new.html.haml | Loading commit data... | |
show.html.haml | Loading commit data... |