Order milestone issues by position ascending in api
What does this MR do?
Fixes order by position ascending in :id/milestones/:milestone_id/issues
api endpoint.
Why was this MR needed?
To return issues for a specific milestone in the same order with the web UI.
Does this MR meet the acceptance criteria?
-
Changelog entry added - [n/a ] Documentation created/updated
-
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #28847 (closed)