Write access over CalDAV
Open
@grnd-alt is already working on this.
Since Mar 30, 2026.
1. to develop
enhancement
feature: dav
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Split off from https://github.com/nextcloud/deck/issues/15 so we have individual issues to track:
Current plan from the discussion below:
| Deck | CalDAV | Tasks |
|---|---|---|
| Board | VCALENDAR |
List |
| Stack | VTODO without RELATED-TO property |
Root-Task |
| Card | VTODO with RELATED-TO (UUID of the Root-Task / Stack) |
Subtask |
| Tags | CATEGORIES or custom implementation (Nextcloud tagging system) |
Currently uses CATEGORIES, integration with Nextcloud tags would be better, see https://github.com/nextcloud/tasks/issues/89 |
| Assigned users | ATTENDEE or custom implementation |
ATTENDEE or custom implementation, see https://github.com/nextcloud/tasks/issues/72 |
| Recurring stacks & cards | RRULE |
Recurring tasks & subtasks, see https://github.com/nextcloud/tasks/issues/34 |
| Attachments | ATTACH or custom implementation |
ATTACH or custom implementation, see https://github.com/nextcloud/tasks/issues/91 |
Tags, assigning users, attachments and recurrence is not supported by Tasks yet either, but it would make much sense to implement these features. And if we see that it is not really possible to implement this with pure CalDAV I would be open to implement it without syncing it via CalDAV and have it only available in the webinterface. This would still be better than not having it at all in Tasks and would not limit Deck.
- ✔️ Expose deck boards as VCALENDAR, try to map as much data from deck to the VTODO (read only access)
- ✅ Allow updating VCALENDAR entries, try to map as much as possible from vtodo to the deck database and store the rest as plain vtodo data, so we can still push it out over CalDAV (write access)
- ✅ Deck data could be moved to the DAV backend.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.