Write access over CalDAV

[juliusknorr]

Split off from #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 nextcloud/tasks#89
Assigned users	ATTENDEE or custom implementation	ATTENDEE or custom implementation, see nextcloud/tasks#72
Recurring stacks & cards	RRULE	Recurring tasks & subtasks, see nextcloud/tasks#34
Attachments	ATTACH or custom implementation	ATTACH or custom implementation, see nextcloud/tasks#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.

1. ✔️ Expose deck boards as VCALENDAR, try to map as much data from deck to the VTODO (read only access)
2. ✅ 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)
3. ✅ Deck data could be moved to the DAV backend.

[tensau]

Is it realistic that this issue could be solved with the 1.3.0 release?

[tomdereub]

Hi, in the first post was this proposal : #15 (comment), about removing stack as root-task and putting it as category. I find it much better than the actual behaviour, what do you think ?

[devvv4ever]

Hey guys,

did you have a look at VJOURNAL for some things that could be related to Decks functionality? Basically these are To-dos/Tasks without a progress or end date. Maybe it fits your needs somewhere in the Deck universe and can be used this way without interfering with VTODOs. VJOURNAL also has the RELATED-TO field available making it possible to link them in-between VTODOs and VEVENTs. https://tools.ietf.org/html/rfc5545#section-3.6.3

At the DAVx5 side we want to provide synchronization for VJOURNAL in the future together with a supporting app since this can also be synchronized using CalDAV.

[Ruthalas]

This issue seems to lack a available developer.
If it was added to a tool such as issuehunt, I'd be glad to donate to fund someone's time to work on this.
Having this functionality would be very useful to me.

(Thank you for the time and effort already invested in this app!)

[simonjaq]

This issue seems to lack a available developer.
If it was added to a tool such as issuehunt, I'd be glad to donate to fund someone's time to work on this.
Having this functionality would be very useful to me.

(Thank you for the time and effort already invested in this app!)

@Ruthalas
I'm also eagerly waiting for this and hoping to move all my to-do lists do the great Deck app once this is implemented.

I was wondering if in the meantime it is easier to develop a small script, which could run on the server and sync selected calDAV task lists with Deck. I looked into it and I think it shouldn't be a problem to connect calDAV tasks with the Deck API. With my very limited Python skills it would still be a challenge but I guess an experienced developer could get this done very quickly.

[tcitworld]

Basic public calendar write API has been added in nextcloud/server#29188

[juliusknorr]

Thanks for the hint, however the deck implementation currently exposes its own calendars to the users calendar home with nextcloud/server#19196. Might still be nice if at some point we need to write entries to the existing user calendars.

[djagoo]

This would solve all our problems. Right now we are using Tasks to manage our projects but we want to use a kanban style board without loosing the ability to manage our tasks in the Android todo app via caldav. So for now we are moving all tasks to vikunja because it has write access to the caldav ressource.