Labels/tags not synced via caldav #1274
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#1274
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?
On android I use Tasks 12.7 and davx5 4.2.3.4 to sync tasks with vikunja via caldav.
Labels created in Tasks are not synced to vikunja and vice versa.
Same setup works flawlessly with caldav to nextcloud.
Tried on current demo instance.
This is quite important for me, because I'm using the tasks.org app and want to be able to access my gtd @contexts underway, which are modelled as labels.
My idea would be to use the field CATEGORIES, which is what nextcloud does.
I will try to submit a PR for that, if you don't mind.
While the path Vikunja -> CALDAV seems to be straight forward, the other way around (importing Labels from CALDAV) is more delicate: Should new Categories automatically be created as Labels? And if so, how? (There seems to be an open point in the code about how to handle Labels in Tasks.) What should happen if Categories are missing or empty?
What do you think?
Thanks for the PR!
I think Vikunja should create all categories which don't exist. This is similar to how the frontend handles it right now.