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

[GH-ISSUE #246] Upcoming "Today" not showing expected tasks #6006

New Issue
Closed
opened 2026-04-20 16:31:31 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:31:31 -05:00
Owner
Copy Link

Originally created by @Kevinizevbigie on GitHub (Apr 4, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/246

Description

In the Upcoming section, when I choose to see jobs by "today" the boxes become:

from: now/d to:now/d+1d

No jobs are shown.

1day

When I set the date range to two day, I get the expected list of jobs that are due within one day.

from: now/d to:now/d+2d

2 days

The demo instance does not show this behavior. I suspect it might be something to do with timezone.

My timezone is asia/bangkok

Vikunja Version

v0.23.0

Browser and version

Firefox 119.0

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Kevinizevbigie on GitHub (Apr 4, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/246 ### Description In the Upcoming section, when I choose to see jobs by "today" the boxes become: `from: now/d` `to:now/d+1d` No jobs are shown. ![1day](https://github.com/go-vikunja/vikunja/assets/71597180/38fca18b-81b0-43c2-ab5d-23c02b01118d) When I set the date range to two day, I get the expected list of jobs that are due within one day. `from: now/d` `to:now/d+2d` ![2 days](https://github.com/go-vikunja/vikunja/assets/71597180/4e3f4aa4-a234-4ca3-a149-ed32b3301b65) The demo instance does not show this behavior. I suspect it might be something to do with timezone. My timezone is asia/bangkok ### Vikunja Version v0.23.0 ### Browser and version Firefox 119.0 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:31:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 5, 2024):

Yeah this looks like a time zone problem. The relative time used the time zone the server runs in, not the one of the user.
There have been changes so that it uses the user's configured time zone in that case - given how you weren't able to reproduce it on try, I guess that confirms this.

Please check with the next release (once that's released) or the latest unstable build. I'll close this now, ping again if you have issues with either the latest unstable build or the next release.

<!-- gh-comment-id:2039878170 --> @kolaente commented on GitHub (Apr 5, 2024): Yeah this looks like a time zone problem. The relative time used the time zone the server runs in, not the one of the user. There have been changes so that it uses the user's configured time zone in that case - given how you weren't able to reproduce it on try, I guess that confirms this. Please check with the next release (once that's released) or the latest unstable build. I'll close this now, ping again if you have issues with either the latest unstable build or the next release.
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#6006
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?