[Feature Request] Tasks created in Yuvomi lack CalDAV reminder list assignment (breaking two-way sync)

[BradNut]

Feature Request / Gap Discovery: Task creation should support CalDAV reminder list assignment (like Calendar events do)

Summary

While investigating CalDAV task sync with Synology + DAVx⁵, I discovered that Yuvomi supports two-way CalDAV sync for tasks only when they're already on the server. Tasks created within Yuvomi remain local-only because there's no mechanism to assign them to a CalDAV-linked reminder list.

This appears to be a functional gap: Calendar event creation in Yuvomi includes a "Sync to CalDAV" dropdown, but Task creation lacks an equivalent "Sync to Reminder List" selector.

---

Environment

Component	Value
Yuvomi Version	v1.87.0
Platform	Android (reproducible on Web)
CalDAV Server	Synology DSM Calendar (https://<name>.synology.me:5001/caldav/)
Related Apps	Tasks.org + DAVx⁵ for cross-client verification

---

Investigation Findings

What Works ✅

• Tasks created externally (Tasks.org → DAVx⁵ → Synology) sync into Yuvomi correctly
• Tasks arriving in the Inbox reminder list display properly in Yuvomi
• Edits to externally-created tasks in Yuvomi sync back to Synology successfully
• Calendar event creation has a working "Sync to CalDAV" selector

What Doesn't Work ❌

• Tasks created within Yuvomi have no UI option to assign them to the CalDAV reminder list
• Created tasks remain local-only; they never appear on Synology or other CalDAV clients
• No error message is shown — sync simply skips outbound task creation

---

Configuration Detail

From Settings → Sync → Reminder sync:

Synology Calendar Connected https://.synology.me:5001/caldav/ 1 reminder list enabled Last sync: 08/07/2026 2:02 AM

Inbox → Tasks

---

Expected UX (Based on Calendar Event Pattern)

Currently, when creating a Calendar event in Yuvomi, you see:
Event Title: ________________ Date/Time: ________________ Sync to CalDAV: [▼ Select calendar ▼] ← Working selector

For Task creation, we'd expect similar parity:

Task Title: ________________ Due Date: ________________ Priority: ________________ Sync to Reminder List: [▼ Select list ▼] ← Currently missing

---

Why This Matters

1. Bidirectional sync expectation: Users assume CalDAV-connected apps work in both directions
2. Feature parity inconsistency: Calendar events already implement this pattern
3. Workflow disruption: Users must create tasks externally to have them sync into Yuvomi

---

Proposed Solutions (Open to Suggestions)

Option	Description
A. Add reminder list selector	Mirror the Calendar event "Sync to CalDAV" dropdown for Tasks
B. Auto-assign to default list	Route all new tasks to the first enabled CalDAV reminder list automatically
C. Post-creation reassignment	Allow editing existing local tasks to move them to a CalDAV list
D. Hybrid approach	Default auto-assignment + override selector for power users

---

Request for Maintainers

Could someone from the team confirm:

1. Is this a known limitation or gap in the current task sync flow?
2. Was the Calendar event sync selector pattern intentionally not replicated for Tasks?

---

Additional Context

• Issue [Bug] Tasks don't get displayed properly #671 was reportedly fixed in v1.78.1 regarding task sync visibility
• This issue is distinct: it's about task creation → outbound sync, not task display
• Same CalDAV credentials work bidirectionally with Tasks.org + DAVx⁵ (no server-side limitation)

---

Thanks for building Yuvomi! Happy to provide more details, logs, or test proposed fixes if helpful.

[Semoxea]

Also some stuff i've noticed:
Subtasks are only visible after clicking on the main task, that's highly inconvenient. Also there's no display of due dates on the task UI itself, so you don't get a nice overview over overdue tasks just by looking at the task dashboard. Also a sync all button on the
top of the task dashboard would be nice. I also am slowly getting discouraged from opening issues regarding features that just aren't implemented properly due to most of the code originating from claude. It's like noone even tested the functionality before merging into a new version. I get that it's open source, and essentially a hobby project, but it is just exhausting to never really be able to use the application as I would like to (as i find the concept really great)

[Shadow999007]

That's also something I noticed with pretty much the same setup, except radicale as the CalDAV-server. I hope this will be addressed soon, as it is quite an important feature for everyday use. Especially with the WebUI explicitly stating "Sync with Tasks or Shopping in both directions.", I would really consider the lack of this feature a bug.

[ulsklyc]

Thank you for this one. It is the most precise report I have had in a while, and both of your questions have the same uncomfortable answer: yes, and yes.

Is it a known limitation? It is, and the code says so out loud. server/services/caldav-todo-outbound.js:17 carries this comment: a move between lists is deliberately absent, because unlike an event a task carries no selectable target, and "for the same reason nothing goes out that was created here". So outbound sync for tasks was scoped to mirrored tasks on purpose, and your investigation reconstructed that boundary exactly, including the part that makes it worse: nothing is reported as skipped. Silence is the wrong way to communicate a limit.

Was the calendar pattern intentionally not replicated? Also yes, and that was the mistake. The reason recorded at the time was that a task has no natural target list. That reason no longer holds: calendar_default_target per person shipped in v1.79.0 with #620, and it is exactly the mechanism your option D describes. The precedent I argued did not exist had been in the codebase for weeks.

@Shadow999007 puts the decisive point better than I would have: the UI states that Tasks and Shopping sync "in both directions". Measured against that sentence this is not a missing feature, it is a defect. A promise in the interface is part of the product, and half of a promise is not a smaller promise, it is a wrong one. So this gets fixed in the direction of your option D: a per-person default target list following the #620 pattern, plus an override in the task dialog, and option C for the tasks that already exist locally, since without it every task created before the fix stays invisible forever.

@Semoxea, your comment deserves a straight answer rather than a defensive one, so let me split it into the parts I can check.

Two of your three examples do not reproduce on v1.87.0, the version reported here. Due dates are rendered on the task card itself, in the meta row next to priority and tags (renderDueDate in public/pages/tasks.js, present in the v1.87.0 tag). Subtasks are not behind opening the task either: a progress bar on the card expands them in place. Your underlying complaint about that one still stands, though, because expanding is a click and a collapsed count is not an overview. If your build genuinely shows no due dates, that is a different bug and I would like the version and a screenshot, because then something is broken that I believe to be working.

Your third example is simply correct: there is no sync button in tasks, and no way to trigger one.

On the larger point, I am not going to argue with you. This project is written with heavy AI assistance, I am one person, and this report is a good illustration of what that costs: the gap you found is not an oversight, it is a decision that was written down in a source comment and never made it into the interface, where the opposite sentence stayed on screen. The lesson I am taking from your comment is narrower than "test more" and more actionable: a feature that exists by half has to say which half, in the UI, not in a comment. That applies to this sync and to anything else where I scoped something down late.

Thanks for pushing back, and thanks for offering to test. I will take you up on that when there is something to try.

[ulsklyc]

Shipped in v2.7.0.

It went in as your option D, with option C alongside it, because without C every task created before the fix would have stayed invisible forever:

• The task dialog has a "sync target" field, the same one the event dialog has had since Default CalDAV calendar for family events #620.
• A personal default lives in Settings → Personal → Task defaults. Deliberately personal: which reminder lists the household mirrors at all is an admin decision, which of them your new tasks go to is yours.
• An existing local task can be given a target when you edit it, so the backlog you already typed in is not stranded.
• The upload runs right after saving and again on every sync run.

Only lists the household enabled for tasks are offered. A list mapped to Shopping would have sent a task out and brought it back as a shopping item, so it is filtered out in the route and again in the sync service.

Three things I would rather write down than have you discover:

• Subtasks are not uploaded. As standalone VTODOs they would sit beside their parent as equals, and the relationship that makes them subtasks would be gone. RELATED-TO exists in the format, but the inbound does not read it yet, so the round trip would hand them back as loose tasks.
• A task that has already been uploaded cannot be moved to another list. That was true before this change and still is: a task belongs to the list it came from.
• A task without a target stays local, exactly as every task did until now. Nothing starts syncing because of this release.

@Shadow999007, your framing is the one that decided the shape of this. The interface said "in both directions" while half of it was missing, and measured against that sentence this was not a missing feature, it was a defect. That is also why it went out as a whole rather than in pieces.

@Semoxea, three claims, and they deserve individual answers rather than a blanket apology:

• Due dates on task cards: these do render, in the meta row next to priority and tags, and they did in v1.87.0 too - I checked the tagged source rather than trusting my memory. If your build genuinely shows none, that is a separate bug and I would like your version and a screenshot, because then something I believe to be working is broken.
• Subtasks behind a click: not behind opening the task - a progress bar on the card expands them in place. Your underlying point stands, though: a collapsed count is not an overview. There is a household setting, Settings → Modules → Module options, that starts them expanded.
• No sync button in tasks: correct, and still correct after this release. Syncing runs on its interval and after each change; a manual trigger is not there.

On the larger point I said I would take the narrower lesson from it rather than promise to test more: a feature that exists by half has to say which half, in the interface, not in a source comment. This release is that lesson applied to the case you and @BradNut found. Thank you both - the report was precise enough that the fix needed no guesswork.

[BradNut]

Thank you @ulsklyc for the clear and detailed responses. Loving the application and this back and further is what makes it great. 🙂

[Shadow999007]

Yeah, I've never seen an app where a requested feature gets implemented so quickly, huge respect.