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

[GH-ISSUE #16] Due time is reset when due day is changed #5822

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

Originally created by @svigneau on GitHub (Jan 2, 2022).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/16

When changing the due day of a task, the due time is automatically reset (typically to 12 pm) instead of remaining as previously set. It would be more natural if the due day could be changed without affecting the due time. A user case would be someone trying to reschedule a task due today in the evening (say 7 pm) to another day at the same time in the evening (7 pm). I am using the latest Vijunja version (0.18.2) on Cloudron.

Originally created by @svigneau on GitHub (Jan 2, 2022). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/16 When changing the due day of a task, the due time is automatically reset (typically to 12 pm) instead of remaining as previously set. It would be more natural if the due day could be changed without affecting the due time. A user case would be someone trying to reschedule a task due today in the evening (say 7 pm) to another day at the same time in the evening (7 pm). I am using the latest Vijunja version (0.18.2) on Cloudron.
GiteaMirror added the bug label 2026-04-20 16:09:31 -05:00
GiteaMirror commented 2026-04-20 16:09:34 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 9, 2022):

Fixed in https://kolaente.dev/vikunja/frontend/pulls/1336 - please check with the next unstable build once the CI released it. (should take ~30min).

Closing this as resolved, feel free to ping if you have other issues or questions.

<!-- gh-comment-id:1008269269 --> @kolaente commented on GitHub (Jan 9, 2022): Fixed in https://kolaente.dev/vikunja/frontend/pulls/1336 - please check with the next unstable build once the CI released it. (should take ~30min). Closing this as resolved, feel free to ping if you have other issues or questions.
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#5822
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?