Makes sense. Don't change it on my behalf then, I can see how this would benefit teams that plan sprints/milestones way far out.

Could it be a config option for projects for milestone sort order, newest -> oldest or oldest -> newest? It would be nice to customize it.

Here is also the subproject order, I had to archive some projects because the board was too large/cumbersome with them activated. We usually plan 2-3 sprints out, with some tasks moving further out if something blocks them. This ordering really hurts us being able to effectively move or change tasks as needed:

Here's how our main project board looks after the recent change:

We archive milestones so they don't appear on the board anymore.