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

Gantt Chart does not correctly respect end time #2235

New Issue
Closed
opened 2026-03-22 13:58:30 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-03-22 13:58:30 -05:00
Owner
Copy Link

Originally created by @lambi21 on GitHub (Jun 3, 2025).

Description

The Gantt chart does not correctly handle end dates for tasks that end on 23:59:59.
In essence, the gantt chart only displays a task of taking one day, if the end date is actually the following day at 23:59:59.
e.g.:
Adding a new task in the gantt view, the date range at first seems fine
Image
when switching to table view, the end date is different (note the time):
Image

This is especially visible when adding tasks that should happen on one day from 00:00:00 until 23:59:59 of the same day. These appear in the gantt chart only on the line between the two days:

Image

Image

Vikunja Version

0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @lambi21 on GitHub (Jun 3, 2025). ### Description The Gantt chart does not correctly handle end dates for tasks that end on 23:59:59. In essence, the gantt chart only displays a task of taking one day, if the end date is actually the following day at 23:59:59. e.g.: Adding a new task in the gantt view, the date range at first seems fine ![Image](https://github.com/user-attachments/assets/59c6fdb7-11f7-4882-8567-a52b16d4667f) when switching to table view, the end date is different (note the time): ![Image](https://github.com/user-attachments/assets/2bc9be9a-6d2e-4983-9247-97e4ba3dd27a) This is especially visible when adding tasks that should happen on one day from 00:00:00 until 23:59:59 of the same day. These appear in the gantt chart only on the line between the two days: ![Image](https://github.com/user-attachments/assets/7b70cc92-e611-4556-8935-c47935bd6283) ![Image](https://github.com/user-attachments/assets/24b64897-2586-4920-86c6-cf9cc53a12ab) ### Vikunja Version 0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the area/gantt label 2026-03-22 13:58:30 -05:00
GiteaMirror commented 2026-03-22 13:58:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 3, 2025):

Do you think this could be solved by rounding to the nearest full day instead?

@kolaente commented on GitHub (Jun 3, 2025): Do you think this could be solved by rounding to the nearest full day instead?
GiteaMirror commented 2026-03-22 13:58:31 -05:00
Author
Owner
Copy Link

@avatar1024 commented on GitHub (Jun 4, 2025):

Do you think this could be solved by rounding to the nearest full day instead?

And it would solved this too, no?: https://github.com/go-vikunja/vikunja/issues/527

@avatar1024 commented on GitHub (Jun 4, 2025): > Do you think this could be solved by rounding to the nearest full day instead? And it would solved this too, no?: https://github.com/go-vikunja/vikunja/issues/527
GiteaMirror commented 2026-03-22 13:58:31 -05:00
Author
Owner
Copy Link

@lambi21 commented on GitHub (Jun 4, 2025):

Do you think this could be solved by rounding to the nearest full day instead?

Can't really tell, I don't know how the gantt library you are using works. From what I've seen on the demo system it might. Will however make it impossible to add intra-day tasks (at least if I understand Your suggestion correctly of always rounding the time to the nearest day). So I assume it would fix the issue for tasks of one day or longer, but will possibly create issues with tasks of less than one day.

@lambi21 commented on GitHub (Jun 4, 2025): > Do you think this could be solved by rounding to the nearest full day instead? Can't really tell, I don't know how the gantt library you are using works. From what I've seen on the demo system it might. Will however make it impossible to add intra-day tasks (at least if I understand Your suggestion correctly of always rounding the time to the nearest day). So I assume it would fix the issue for tasks of one day or longer, but will possibly create issues with tasks of less than one day.
GiteaMirror commented 2026-03-22 13:58:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 5, 2025):

I think it's fine to round to the nearest day, if we're only viewing tasks with a granularity of one day. We should support more, but for the way it's currently implemented, that should be it.

@kolaente commented on GitHub (Jun 5, 2025): I think it's fine to round to the nearest day, if we're only viewing tasks with a granularity of one day. We should support more, but for the way it's currently implemented, that should be it.
GiteaMirror commented 2026-03-22 13:58:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 12, 2025):

This should be fixed now with https://github.com/go-vikunja/vikunja/pull/1001, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Aug 12, 2025): This should be fixed now with https://github.com/go-vikunja/vikunja/pull/1001, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
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 area/gantt
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#2235
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?