Skip to content

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?

What are the relevant issue numbers?

Closes #28847 (closed)

Merge request reports