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

CalDAV - Sync repeat tasks #442

New Issue
Open
opened 2025-11-01 20:56:16 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:56:16 -05:00
Owner
Copy Link

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

Original issue by dead10ck on 2023-04-02T19:54:12.000Z

When using CalDAV with DAVx and Tasks.org on Android, it seems currently task repetition is not synced at all. New tasks created in Tasks end up on Vikunja, but do not have any repetition set. When repetition is set in Vikunja, they show up in Tasks, but with what appears to be a raw CalDAV property, e.g. FREQ=SECONDLY;INTERVAL=86400. Tasks does seem to still do the right thing and reschedule it correctly, despite the UI issue.

I'm not sure if this is a bug report or a feature request.

Original issue on Gitea

@kolaente commented on 2023-04-02T20:32:10.000Z:

The problem is, Vikunja only supports repeating a task every X seconds. But Tasks.org does not support that mode. Because of that, Vikunja ignores the repeating attribute sent by Tasks.org when syncing it back.

There is an item in the backlog, it's just a lot of work because the reminder model works differently in Vikunja than what Tasks.org assumes.

Related forum threads:

ce72 commented on 2023-04-02T20:38:05.000Z:

Adding to the comment of @konrad: Vikunja does not read RRULE (for repeating tasks) from CalDAV, that's just not implemented.
However, it writes RRULE properties for its own tasks.
This may in part explain your findings in #1460. The current state of CalDAV implementation (referring to the unstable version) is described here: https://vikunja.io/docs/caldav/#supported-properties

dead10ck commented on 2023-04-02T20:44:21.000Z:

I see, so feature request 🙂. Yeah, a recurrence model of a fixed number of seconds does not map well to real calendars. For example, you couldn't even do "every first of the month", because not every month is a fixed number of days.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by dead10ck on 2023-04-02T19:54:12.000Z_ When using CalDAV with DAVx and Tasks.org on Android, it seems currently task repetition is not synced at all. New tasks created in Tasks end up on Vikunja, but do not have any repetition set. When repetition is set in Vikunja, they show up in Tasks, but with what appears to be a raw CalDAV property, e.g. `FREQ=SECONDLY;INTERVAL=86400`. Tasks does seem to still do the right thing and reschedule it correctly, despite the UI issue. I'm not sure if this is a bug report or a feature request. [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1459) --- _**@kolaente** commented on 2023-04-02T20:32:10.000Z_: The problem is, Vikunja only supports repeating a task every X seconds. But Tasks.org does not support that mode. Because of that, Vikunja ignores the repeating attribute sent by Tasks.org when syncing it back. There is an item in the backlog, it's just a lot of work because the reminder model works differently in Vikunja than what Tasks.org assumes. Related forum threads: * https://community.vikunja.io/t/specific-weekdays-repeat-mode/639 * https://community.vikunja.io/t/yearly-repeat-mode/1165 * https://community.vikunja.io/t/more-repeating-intervals/1238/8 * https://community.vikunja.io/t/repeating-interval-for-the-last-day-of-the-month/1159 --- _**ce72** commented on 2023-04-02T20:38:05.000Z_: Adding to the comment of @konrad: Vikunja does not read RRULE (for repeating tasks) from CalDAV, that's just not implemented. However, it writes RRULE properties for its own tasks. This may in part explain your findings in #1460. The current state of CalDAV implementation (referring to the unstable version) is described here: https://vikunja.io/docs/caldav/#supported-properties --- _**dead10ck** commented on 2023-04-02T20:44:21.000Z_: I see, so feature request 🙂. Yeah, a recurrence model of a fixed number of seconds does not map well to real calendars. For example, you couldn't even do "every first of the month", because not every month is a fixed number of days.
GiteaMirror commented 2025-11-01 20:56:16 -05:00
Author
Owner
Copy Link

@xlarin commented on GitHub (Aug 20, 2025):

Hello everyone, I would like to know at what stage this task is?

@xlarin commented on GitHub (Aug 20, 2025): Hello everyone, I would like to know at what stage this task is?
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#442
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?