Skip to content

Ordering by Milestone due filters issues

Ordering by Milestone due sooner/later ("milestone sort") filters issues without a milestone, which can let users feel like disappearing issues without a milestone.

Solutions

2 options are found in my mind:

  1. Filtering should be removed during sort.
  2. Filtering should be notified to a user on Web UI.

Discussion is following:

Solution 1 (!3872 (merged))

Model should be changed with outer join, not inner join

  • Pro: Consistency on Issues API with any sorting will be revived.
  • Con: Performance will be worse.

Solution 2 (discarded)

  • Pro: API is not necessary to change so that there is no performance degradation.
  • Con: API with milestone sort will be still inconsistent.

Case

In GitLab CE 8.5.4, as well as on GitLab.com (as of 2016-03-10), this case is found, but I thinks it has been found in the earlier versions.