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
Overview showing tasks with due dates far in the future rather than near #192
Comments
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? |
Thanks for looking into the issue. I am using MariaDB, LinuxServer flavor. |
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). |
This PR changes the behavoir of sorting tasks. Before, tasks were sorted with null values first. Now, null values are always sorted last which is usually what you want. Partial fix for https://github.com/go-vikunja/frontend/issues/54 Co-authored-by: kolaente <k@knt.li> Reviewed-on: https://kolaente.dev/vikunja/api/pulls/1177
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? |
Yes, it works! Thank you for your promptness! |
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
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.
The text was updated successfully, but these errors were encountered: