Sorting issues by weight in descending order results in issues without a weight being displayed first

For example https://gitlab.com/gitlab-org/gitlab-ce/issues?assignee_id=&author_id=&milestone_title=&scope=all&sort=weight_desc&state=opened shows issues without a weight first, most likely due to the sorting using "NULLS FIRST" instead of "NULLS LAST".

That's a really annoying bug.

And unfortunately there is also no way of assigning weight to more than one issue at a time,... (I thought of assigning a weight of 1 to all tickets having no weight).

Is this delayed due to #21747 (closed)? @JobV @ClemMakesApps

No it isn't. I actually haven't seen this issue before. This seems to be a backend issue. I'm also going to move this to the enterprise repository since this is an ee feature

/cc @regisF

moved to gitlab-ee#1674