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

due today ends at 15:00 #428

New Issue
Open
opened 2025-11-01 20:56:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 20:56:06 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by zhzy0077 on 2023-01-23T05:44:08.000Z

Description

TZ: Asia/Shanghai, not sure if relevent

  1. Go to a list
  2. Enter today test item
  3. It shows ends at 15:00 today.

Expected: Should it be 00:00 tomorrow?

Vikunja Frontend Version

0.20.2

Vikunja API Version

0.20.1

Browser and version

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

图片
图片

Original issue on Gitea

@kolaente commented on 2023-01-24T15:55:41.000Z:

If you don't provide a date when creating a new task it will use the nearest date, similar to the date picker. In your case you seem to have created the task after 12:00 and before 15:00, hence Vikunja picked 15:00 as the time.

dpschen commented on 2023-01-24T20:42:14.000Z:

I am also confused by this. Shouldn't this pick midnight as due date for today?

zhzy0077 commented on 2023-01-26T17:00:25.000Z:

If you don't provide a date when creating a new task it will use the nearest date, similar to the date picker. In your case you seem to have created the task after 12:00 and before 15:00, hence Vikunja picked 15:00 as the time.

TBH I don't get it.

  1. I provided a date by saying 'today xxxx'
  2. When I created a task between 12:00 and 15:00, isn't the nearest date tomorrow 00:00?

@kolaente commented on 2023-01-27T11:42:33.000Z:

When I created a task between 12:00 and 15:00, isn't the nearest date tomorrow 00:00?

The way it is currently implemented, no. Vikunja looks for the next time in three-hour intervals (excluding night).

dpschen commented on 2023-01-27T14:25:29.000Z:

Vikunja looks for the next time in three-hour intervals (excluding night).

I guess this is what is confusing me.

If I write 'today' what I would mean personally is that that task should be done 'any time today' meaning the due date should be either at midnight or even a bit later since 'my day' – in the sense of my being-awake time – usually ends after midnight.

If I write 'in the next few hours' the current setting would be fine. Maybe even for 'now'. I wouldn't expect the due date to include an hour if I didn't define one.

@kolaente commented on 2023-01-27T15:00:35.000Z:

I think this returns to the discussion we had in https://kolaente.dev/vikunja/frontend/issues/809.

I wouldn't expect the due date to include an hour if I didn't define one.

The issue is the api expects to save the due date with a time. Hence we need to pick one when the user does not provide one.

dpschen commented on 2023-01-27T15:49:05.000Z:

I think this returns to the discussion we had in #809.

You are right! For a quick fix I think that change would improve UX a lot. We should really rebase and merge https://kolaente.dev/vikunja/frontend/pulls/1378 .
The latter only fixes the view part though.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by zhzy0077 on 2023-01-23T05:44:08.000Z_ ### Description TZ: Asia/Shanghai, not sure if relevent 1. Go to a list 2. Enter *today test item* 3. It shows ends at 15:00 today. Expected: Should it be 00:00 tomorrow? ### Vikunja Frontend Version 0.20.2 ### Vikunja API Version 0.20.1 ### Browser and version Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![图片](/attachments/6d8c2e85-d047-4e0c-aabe-53324873b333) ![图片](/attachments/b6b99a74-067e-444b-897f-fb710eefef83) [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/2005) --- _**@kolaente** commented on 2023-01-24T15:55:41.000Z_: If you don't provide a date when creating a new task it will use the nearest date, similar to the date picker. In your case you seem to have created the task after 12:00 and before 15:00, hence Vikunja picked 15:00 as the time. --- _**dpschen** commented on 2023-01-24T20:42:14.000Z_: I am also confused by this. Shouldn't this pick midnight as due date for today? --- _**zhzy0077** commented on 2023-01-26T17:00:25.000Z_: > If you don't provide a date when creating a new task it will use the nearest date, similar to the date picker. In your case you seem to have created the task after 12:00 and before 15:00, hence Vikunja picked 15:00 as the time. TBH I don't get it. 1. I provided a date by saying 'today xxxx' 2. When I created a task between 12:00 and 15:00, isn't the nearest date tomorrow 00:00? --- _**@kolaente** commented on 2023-01-27T11:42:33.000Z_: > When I created a task between 12:00 and 15:00, isn't the nearest date tomorrow 00:00? The way it is currently implemented, no. Vikunja looks for the next time in three-hour intervals (excluding night). --- _**dpschen** commented on 2023-01-27T14:25:29.000Z_: > Vikunja looks for the next time in three-hour intervals (excluding night). I guess this is what is confusing me. If I write 'today' what I would mean personally is that that task should be done 'any time today' meaning the due date should be either at midnight or even a bit later since 'my day' – in the sense of my being-awake time – usually ends after midnight. If I write 'in the next few hours' the current setting would be fine. Maybe even for 'now'. I wouldn't expect the due date to include an hour if I didn't define one. --- _**@kolaente** commented on 2023-01-27T15:00:35.000Z_: I think this returns to the discussion we had in https://kolaente.dev/vikunja/frontend/issues/809. > I wouldn't expect the due date to include an hour if I didn't define one. The issue is the api expects to save the due date with a time. Hence we need to pick one when the user does not provide one. --- _**dpschen** commented on 2023-01-27T15:49:05.000Z_: > I think this returns to the discussion we had in #809. You are right! For a quick fix I think that change would improve UX a lot. We should really rebase and merge https://kolaente.dev/vikunja/frontend/pulls/1378 . The latter only fixes the view part though.
GiteaMirror added the kind/bug label 2025-11-01 20:56:06 -05:00
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 kind/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#428
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?