New Issue form- Revert milestone sort order to earliest-to-latest

Summary

In GitLab version 13.4+, Milestones in the issue creation form seem to be sorted in a latest-due to earliest-due order, with the Milestone with the latest due date appearing on the top of the list. In older versions (such as on 12.0), the sort order is earliest-due to latest-due, with the Milestone with the earliest due date appearing on the top of the list. The latter makes more sense as teams typically be working on the earliest-due milestones first.

Customer feedbac:

After upgrade to 13.4.1, order of milestones in Assign Milestone drop down menu on issues page changed from earliest-to-latest to latest-to-earliest. This kills productivity. Please revert this change or allow to configure this option. I consider this a regression.

Steps to reproduce

On a pre-13.4 version and post-13.4 version:

1. Create a new project
2. Create a handful of new milestones within the project with various due dates
3. Create a new issue
4. Select Milestones and observe the order they are displayed.

What is the current bug behavior?

Milestones in the issue creation form seem to be sorted in a latest-due to earliest-due order, with the Milestone with the latest due date appearing on the top of the list.

What is the expected correct behavior?

Milestones in the issue creation are sorted in a latest-due to earliest-due order, with the Milestone with the latest due date appearing on the top of the list.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:		Ubuntu 18.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.6.6p146
Gem Version:	2.7.10
Bundler Version:1.17.3
Rake Version:	12.3.3
Redis Version:	5.0.9
Git Version:	2.28.0
Sidekiq Version:5.2.9
Go Version:	unknown

GitLab information
Version:	13.4.0-ee
Revision:	e70802d39ca
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	11.9
URL:		http://shem-stack8-gitlab.sr.gitlab.support
HTTP Clone URL:	http://shem-stack8-gitlab.sr.gitlab.support/some-group/some-project.git
SSH Clone URL:	git@shem-stack8-gitlab.sr.gitlab.support:some-group/some-project.git
Elasticsearch:	no
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers:

GitLab Shell
Version:	13.7.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell
Git:		/opt/gitlab/embedded/bin/git

Results of GitLab application Check

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.7.0 ? ... OK (13.7.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
1/1 ... yes
6/2 ... yes
2/3 ... yes
2/4 ... yes
6/5 ... yes
16/6 ... yes
16/7 ... yes
1/8 ... yes
1/9 ... yes
1/10 ... yes
19/11 ... yes
Redis version >= 4.0.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.6)
Git version >= 2.24.0 ? ... yes (2.28.0)
Git user has default SSH configuration? ... yes
Active users: ... 6
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... no
  Try fixing it:
  Please migrate all projects to hashed storage
  as legacy storage is deprecated in 13.0 and support will be removed in 14.0.
  For more information see:
  doc/administration/repository_storage_types.md
Elasticsearch version 6.x - 7.x? ... skipped (elasticsearch is disabled)

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished