mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 19:15:48 +03:00
[GH-ISSUE #430] CalDav Tasks - Handle Subtasks #881
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#881
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @LSeelig on GitHub (Aug 30, 2024).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/430
I am a novice both to this software and to outlook and caldav, so the following might be incorrect:
RELATED-TOfor facilitating subtasks.When I add subtasks to my CalDAV tasks, these subtasks are just synced into Outlook as ordinary tasks, causing clutter and confusion. Would it already be possible to (or possible to implement)
a. Prevent the syncing to Outlook of tasks that have a UID in the
RELATED-TO(subtasks)b. In addition, append the names of the subtasks to the description of the parent task (the UID in
RELATED-TO)?I would imagine B would require some logic to sync and update properly, but A would hopefully be more realistic. Either way, either would be an appreciated advanced option, if not a default.