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 (closed)
Screenshots (if relevant)
Not relevant.
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the style guides -
Branch has no merge conflicts with master
(if you do - rebase it please) -
Squashed related commits together