github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-07 12:37:14 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Upcoming sort "show tasks without date" should prioritize priority #671

New Issue
Open
opened 2025-11-01 21:01:33 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-01 21:01:33 -05:00
Owner
Copy Link

Originally created by @tachyonFlux on GitHub (Oct 24, 2025).

Description

The Upcoming page sorting for tasks without a due date seems to sort by last changed tasks. Instead I think it would be best to sort the list by due date, then by priority setting (DO NOW, Urgent, High, etc) and then by last changed.

I make a lot of routines that have due dates but not priority and then I also make a lot of tasks that have no due date but have a priority set. I want all of these tasks sorted at the top of a single page which can be the "Upcoming" page.

Which alternatives did you consider using instead?

I considered making a custom filter as a work around, but it feels to me that this is a natural way to sort the Upcoming page.

Originally created by @tachyonFlux on GitHub (Oct 24, 2025). ### Description The Upcoming page sorting for tasks without a due date seems to sort by last changed tasks. Instead I think it would be best to sort the list by due date, then by priority setting (DO NOW, Urgent, High, etc) and then by last changed. I make a lot of routines that have due dates but not priority and then I also make a lot of tasks that have no due date but have a priority set. I want all of these tasks sorted at the top of a single page which can be the "Upcoming" page. ### Which alternatives did you consider using instead? I considered making a custom filter as a work around, but it feels to me that this is a natural way to sort the Upcoming page.
GiteaMirror commented 2025-11-01 21:01:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 31, 2025):

Upcoming sorts by due date (tasks due soon or overdue appear first), then all tasks without a due date after that, in order of creation.

@kolaente commented on GitHub (Oct 31, 2025): Upcoming sorts by due date (tasks due soon or overdue appear first), then all tasks without a due date after that, in order of creation.
GiteaMirror commented 2025-11-01 21:01:34 -05:00
Author
Owner
Copy Link

@JoeJoeTV commented on GitHub (Nov 1, 2025):

I would also like to have a feature at least similar to this. I often have tasks that don't necessarily have a specific due date, but are more urgent than other tasks, so their priority is set accordingly. How a view where I could view tasks with due dates and also the most important (see priority) tasks without due dates, would be perfrect and seems intuitive to me.

@JoeJoeTV commented on GitHub (Nov 1, 2025): I would also like to have a feature at least similar to this. I often have tasks that don't necessarily have a specific due date, but are more urgent than other tasks, so their priority is set accordingly. How a view where I could view tasks with due dates and also the most important (see priority) tasks without due dates, would be perfrect and seems intuitive to me.
GiteaMirror commented 2025-11-01 21:01:34 -05:00
Author
Owner
Copy Link

@tachyonFlux commented on GitHub (Nov 1, 2025):

I still think this should be built-in. But as a work around I made the following custom filter and called it "Important" virtual project:

done = false && (priority > 1 || dueDate < now+1d)

@tachyonFlux commented on GitHub (Nov 1, 2025): I still think this should be built-in. But as a work around I made the following custom filter and called it "Important" virtual project: `done = false && (priority > 1 || dueDate < now+1d)`
GiteaMirror commented 2025-11-01 21:01:34 -05:00
Author
Owner
Copy Link

@JoeJoeTV commented on GitHub (Nov 1, 2025):

I still think this should be built-in. But as a work around I made the following custom filter and called it "Important" virtual project:

done = false && (priority > 1 || dueDate < now+1d)

This solves part of the problem, but one still has to decice what priority level to use and I also would still like the sorting behaviour, so I agree that this should be a feature.

@JoeJoeTV commented on GitHub (Nov 1, 2025): > I still think this should be built-in. But as a work around I made the following custom filter and called it "Important" virtual project: > > `done = false && (priority > 1 || dueDate < now+1d)` This solves part of the problem, but one still has to decice what priority level to use and I also would still like the sorting behaviour, so I agree that this should be a feature.
GiteaMirror commented 2025-11-01 21:01:34 -05:00
Author
Owner
Copy Link

@JoeJoeTV commented on GitHub (Nov 1, 2025):

Maybe it could also be solved by adding an option to have a specific sort order for virtual projects/filters.

@JoeJoeTV commented on GitHub (Nov 1, 2025): Maybe it could also be solved by adding an option to have a specific sort order for virtual projects/filters.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#671
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?