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

Overview showing tasks with due dates far in the future rather than near #52

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

Originally created by @Break-Off on GitHub (May 24, 2022).

Description of the issue

When there are more than 50 tasks with defined due dates in the future, Vikunja will only show the ones that are farther in the future, instead of prioritizing those nearer or overdue.

Steps to reproduce

  1. Create a task with an overdue date
  2. Create a task with a near due date (e.g. tomorrow)
  3. Create 50 tasks with a far due date (e.g. by the end of the year)
  4. Both the overdue and the near due date task will be displaced in the overview, showing only the ones farther in the future.

Expected behavior

Vikunja should prioritize showing those tasks that are either overdue or in the near future, while hiding those that are far in the future.

Originally created by @Break-Off on GitHub (May 24, 2022). ### Description of the issue When there are more than 50 tasks with defined due dates in the future, Vikunja will only show the ones that are farther in the future, instead of prioritizing those nearer or overdue. ### Steps to reproduce 1. Create a task with an overdue date 2. Create a task with a near due date (e.g. tomorrow) 3. Create 50 tasks with a far due date (e.g. by the end of the year) 4. Both the overdue and the near due date task will be displaced in the overview, showing only the ones farther in the future. ### Expected behavior Vikunja should prioritize showing those tasks that are either overdue or in the near future, while hiding those that are far in the future.
GiteaMirror added the bug label 2025-11-01 20:45:33 -05:00
GiteaMirror commented 2025-11-01 20:45:34 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 27, 2022):

I was able to reproduce this in a test. Looks like it is a combination of bugs in the frontend and api.

What database are you using?

@kolaente commented on GitHub (May 27, 2022): I was able to reproduce this in a test. Looks like it is a combination of bugs in the frontend and api. What database are you using?
GiteaMirror commented 2025-11-01 20:45:34 -05:00
Author
Owner
Copy Link

@Break-Off commented on GitHub (May 27, 2022):

Thanks for looking into the issue. I am using MariaDB, LinuxServer flavor.

@Break-Off commented on GitHub (May 27, 2022): Thanks for looking into the issue. I am using [MariaDB, LinuxServer flavor](https://docs.linuxserver.io/images/docker-mariadb).
GiteaMirror commented 2025-11-01 20:45:35 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 28, 2022):

I've put up two PRs which should fix this:

https://kolaente.dev/vikunja/api/pulls/1177

https://kolaente.dev/vikunja/frontend/pulls/1997

I'll ping again once there's a way to test these (right now it's a bit complicated).

@kolaente commented on GitHub (May 28, 2022): I've put up two PRs which should fix this: https://kolaente.dev/vikunja/api/pulls/1177 https://kolaente.dev/vikunja/frontend/pulls/1997 I'll ping again once there's a way to test these (right now it's a bit complicated).
GiteaMirror commented 2025-11-01 20:45:35 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 31, 2022):

There's a test deployment from the frontend pr now: https://1997-fix-due-soon-first--vikunja-frontend-preview.netlify.app/

Could you check if it works as intended on that test instance?

@kolaente commented on GitHub (May 31, 2022): There's a test deployment from the frontend pr now: https://1997-fix-due-soon-first--vikunja-frontend-preview.netlify.app/ Could you check if it works as intended on that test instance?
GiteaMirror commented 2025-11-01 20:45:35 -05:00
Author
Owner
Copy Link

@Break-Off commented on GitHub (May 31, 2022):

Yes, it works! Thank you for your promptness!

@Break-Off commented on GitHub (May 31, 2022): Yes, it works! Thank you for your promptness!
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 bug
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#52
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?