Support time in Tasks

[hukadev]

Hello,

On the web, I have this task:

After running 'Import events and tasks from Google', I get this markdown output:

---
title: Web 2
completed: false
status: needsAction
googleId: Y2ZodVl0dUh6STRKTVR2aQ
tasklist: "@default"
due: 2026-09-10
position: "00000000000000000000"
---

It would be great if the import could include the time as well (not just the date)

[Cordedmink2]

working on it now :)

[Cordedmink2]

This was generated by AI during triage.

Thanks for the report, and for the screenshot — it turned out to be the important part.

Google Tasks has two separate fields that both get called "due". The Deadline is a date with no time, and it's the only one the Tasks API exposes. The time in your screenshot is Start date and time, a different field that Google Calendar renders as a block of reserved time. No Google API can read it — the Tasks API documentation says outright that it isn't possible to read or write a task's time, and the Calendar API has no way to get at it either. So the import can't fetch that 2pm, and that isn't something this plugin can fix.

What it can do, and now will: if you type a time into due yourself — due: 2026-09-10T14:00 — it will stay there. Until now an import quietly overwrote it back to a bare date, which was a genuine bug your issue uncovered. The time also makes the task count as overdue from 2pm rather than from midnight, and if the deadline moves in Google your time moves with it. It won't reach Google, because there's nowhere for it to go.

That's in #8. Leaving this open until it ships.

[Cordedmink2]

This was generated by AI during triage.

This shipped in 0.3.14.

To be clear about what you get, since it isn't quite what you asked for: a time you type into due yourself is now kept — due: 2026-09-10T14:00 survives an import instead of being quietly cut back to 2026-09-10, it rides onto the new date if the deadline moves in Google, and the task counts as overdue from that time rather than from midnight. What still can't happen is importing the time from Google, because no Google API exposes it.

Closing this as done. If the import side matters to you, the thing that would unblock it is Google exposing the task's time through the Calendar API — worth reopening if that ever changes.