mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-03 00:46:57 -05:00
Task only shows with "Show overdue tasks" #542
Labels
No labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
question
security
support
upstream issue
waiting for reply
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vikunja-go-vikunja#542
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @C-Otto on GitHub (Aug 3, 2025).
Description
I just created a new task with a due date two minutes in the future. This task does not show up in the "Upcoming" list, even though it is indeed upcoming. It only shows when I also select the "Show overdue tasks" checkbox, then with a text "Due in 1 minute".
I assume that this might be related to time zone shenanigans. My server uses the defaults (UTC), while my user account uses Europe/Berlin (currently UTC+2).
Vikunja Version
v0.24.6
Browser and version
Firefox 129.0.1 (64-bit)
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
@kolaente commented on GitHub (Aug 3, 2025):
Since you mentioned you can't reproduce it on the demo, your idea seems to be correct, the demo runs on
Europe/Berlinas well.@mechanarchy commented on GitHub (Oct 4, 2025):
I find the same behaviour, whereby tasks that are due in the future (typically today at 5PM) do not appear in my Upcoming page without ticking the "show overdue tasks" checkbox. In my case this is severely exacerbated by the fact that my timezone is UTC+10, so in practicality nearly every task that is due 'today' will not appear due to the large disparity.
Australia/Sydneyvikunja/vikunja:0.24.6) is running with configservice.timezone: Australia/SydneyUTCAustralia/Sydney@kolaente commented on GitHub (Oct 6, 2025):
Is this still reproducible with the latest unstable builds?
@C-Otto commented on GitHub (Jan 27, 2026):
No, this seems to be fixed. Thank you!