Hey! On paper, the Obsidian task notes integration is exactly what I've been waiting for, for a long time, but as an Obsidian power user, I haven't been able to fully adopt it yet because a few hardcoded settings currently clash with my workflow.
A bit more customization would completely unlock this feature for me:
Custom YAML mapping: It would be amazing if we could map our own metadata keys and specific values to Morgen's task states. For example, instead of relying on a strict boolean completed field, I'd love to use my existing status key with values like "Inbox" or "Archive" to define completion. Same goes for using duedate instead of due_date.
Alternative Task Name source: I use UIDs for my task file titles, so right now my synced tasks just show up as unreadable numbers in the calendar! Allowing us to pull the task name from a metadata key (like a name YAML field) instead of defaulting to the file title would fix this instantly.
I know custom mapping adds some technical complexity under the hood, but this flexibility would allow power users like me to seamlessly fit the integration into our existing vault structures.
Thanks a lot for the continuous updates! π
Please authenticate to join the conversation.
Open
Feature Request
Desktop
19 days ago

Stefanos Stavridis
Get notified by email when there are changes.
Open
Feature Request
Desktop
19 days ago

Stefanos Stavridis
Get notified by email when there are changes.