CalDAV - Sync repeat tasks #1459
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1459
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
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.
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:
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
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.