Take milestone due date into account when sorting issues #6405

New Issue

GiteaMirror · 2025-11-02T06:54:56-06:00

GiteaMirror commented

2025-11-02 06:54:56 -06:00

Originally created by @locnide on GitHub (Nov 28, 2020).

When we sort issues by "Nearest due date" or "Farthest due date", only issues due dates are taken into account.
I think it would be nice to take the milestone due date into account.

Maybe it could be implemented in the following way : when the milestone due date is further than the issue due date, the later is taken into account, and if the milestone due date is nearer, then the milestone is taken into account for sorting.

I've tried an implementation in this commit : 126d3caece and can make a PR if this issue is accepted.

My use case: when I'm looking for the next issue to work on, I go in the issue tab, look at assigned issues and sort by "Nearest due date". But when due dates have been set using milestones, I don't see them and have to look in each milestone manually.

Originally created by @locnide on GitHub (Nov 28, 2020). When we sort issues by "Nearest due date" or "Farthest due date", only issues due dates are taken into account. I think it would be nice to take the milestone due date into account. Maybe it could be implemented in the following way : when the milestone due date is further than the issue due date, the later is taken into account, and if the milestone due date is nearer, then the milestone is taken into account for sorting. I've tried an implementation in this commit : https://github.com/koalp/gitea/commit/126d3caecedc0deed9dbd8cc0d6dff4cdba2e0e9 and can make a PR if this issue is accepted. *My use case: when I'm looking for the next issue to work on, I go in the issue tab, look at assigned issues and sort by "Nearest due date". But when due dates have been set using milestones, I don't see them and have to look in each milestone manually.*

GiteaMirror added the type/enhancement label 2025-11-02 06:54:56 -06:00

GiteaMirror closed this issue

2025-11-02 06:54:56 -06:00

GiteaMirror commented

2025-11-02 06:54:57 -06:00

@noerw commented on GitHub (Dec 22, 2020):

@koalp Nice, please send a PR!

edit: could you check if your change fixes #13395 too?

@noerw commented on GitHub (Dec 22, 2020): @koalp Nice, please send a PR! edit: could you check if your change fixes #13395 too?

GiteaMirror commented

2025-11-02 06:54:57 -06:00

@locnide commented on GitHub (Feb 3, 2021):

edit: could you check if your change fixes #13395 too?

I couldn't reproduce the issue : I tried to create a lot of issue with the same due date (with a due date with a due past by less than a day, and with random names), but the issues where sorted according to their number.

@locnide commented on GitHub (Feb 3, 2021): > edit: could you check if your change fixes #13395 too? I couldn't reproduce the issue : I tried to create a lot of issue with the same due date (with a due date with a due past by less than a day, and with random names), but the issues where sorted according to their number.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6405