Skip to content

when sorting issues by nearest due date, issues without due date should be sorted ascending #35267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

confusedsushi
Copy link
Contributor

When sorting issues and pull requests by the nearest due date, the issues and PRs without a due date are currently sorted descending by their creation date. This seems counter intuitive to me. When sorting by nearest due date I want to see the issues/PRs in the order they should be worked on. For issues/PRs without a due date that order should be first come first served rather than last come first served.

This PR now changes the ordering of issues/PRs which don't have a due date to ascending by their creation date. So that the oldest is shown first and the newest last.

This now also makes the sort order nearest due date a true opposite to farthest due date. At farthest due date the newest is shown first and the oldest last.


Sponsored by Kithara Software GmbH

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Aug 13, 2025
@github-actions github-actions bot added the modifies/go Pull requests that update Go code label Aug 13, 2025
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Aug 14, 2025
@lunny lunny added this to the 1.25.0 milestone Aug 14, 2025
@lunny lunny added the type/enhancement An improvement of existing functionality label Aug 14, 2025
@6543 6543 requested a review from delvh August 18, 2025 10:57
@6543
Copy link
Member

6543 commented Aug 18, 2025

I could have a conflict of interest reviewing this - might you wana review it instead ? - thx :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm/need 1 This PR needs approval from one additional maintainer to be merged. modifies/go Pull requests that update Go code type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants