Skip to content

Tasks ​

A task is a to-do written wherever the work came up: in a meeting's notes, a journal, a spec. It stays there. Nothing is copied to a list somewhere else; the lists are views over the to-dos where they were written, so ticking one anywhere ticks it everywhere.

Type [ ] at the start of a line, or choose To-do from /, and you have a task.

A task's details ​

Press the box to tick a task, or use Ctrl Enter (Cmd Enter on a Mac), or Mark done in the block menu.

Everything else lives in the task bar. Open it from Due date, priority, assignee… in the block menu, or by pressing one of the chips at the end of a task's line:

FieldWhat it says
Duethe day it must be done by. Only this makes a task overdue
Startsthe day it can be started
Week or monthwhen you plan to do it, without picking a day: This week, Next week, This month, Next month
Priorityhigh, medium, low, or normal
Stateto do, doing, waiting, or cancelled
Assigneeanybody in the workspace. Left empty, a task is for the first person @-named in it
Repeata rule such as every weekday. See repeating tasks

Each field shows as a chip on the line. A date that has passed is red, and one due today or tomorrow is amber, by your own calendar. Every change is an ordinary edit: it is recorded, attributed to you, and undone like typing.

In Markdown ​

The fields are written as Dataview's inline fields at the end of the line, so Obsidian and other tools read the same thing:

md
- [ ] Send the report to finance [due:: 2026-11-06] [priority:: high]

On a page written as Markdown, typing a field sets it. Only fields at the very end of a to-do's line are read, and only with values the field takes. [due:: soon] stays words, and so do brackets that happen to look like a field in the middle of a sentence.

My tasks ​

My tasks, in the sidebar and the command palette, lists your tasks in sections:

  • Overdue, Today, This week, This month, Later and No date;
  • Waiting on somebody;
  • Done in the last week.

Your tasks are the ones assigned to you, and the ones you wrote that are not anybody else's. Everybody's shows the whole workspace's instead. Each row says which page the task is on, when it was written and, once ticked, when it was done. Those two times come from the log, so they are true even if the task has moved since. Open a row to go to the task on its page. Tick it here and it is ticked there.

A task appears only if you may open its page. A task on a page in the trash is not listed.

On your journal ​

A journal opens with one line: 2 due today · 1 overdue, or Nothing due today. Press it to see the tasks and tick them from there. Today's journal includes what is overdue. A journal for another day shows what was due on that day. That line also leads to the week's and the month's note.

Weekly and monthly notes ​

A week's note (2026-W43) and a month's note (2026-10) are pages like a journal, made the first time you open them. Open them from the journal's line, or from This week's note and This month's note in the palette. Weeks are ISO weeks, starting on Monday.

A note's line lists the tasks planned for that week or month, or due in it. In the timeline, writing on a note at another time says filed under Week 43, 2026, as writing in an old journal does.

Repeating tasks ​

Give a task a Repeat rule and it comes back after you tick it:

  • every day, every weekday
  • every week, every 2 weeks, every week on Friday
  • every month, every month on 15
  • every year

Ticking a repeating task does not tick it. It moves its dates on to the next occurrence, skipping any that have already passed, and writes [last:: …] with the day you did it. It stays one task on one line. When each occurrence was done is kept in the log, so an update can say done 3 times and name the days.

A rule the bar cannot read is refused there, with examples. In Markdown it stays words.

Task lists ​

Choose Task list (/tasks) to put a list of tasks on any page. A task list is a fence holding a query, and the tasks are drawn live beneath it:

md
```tasks
not done
under this page
this week
```
LineLists
not done, done, allopen tasks (the default), finished ones, or both
mine, everybodyyours, or everybody's (the default, since a page has many readers)
on this page, under this pagethis page only, or this page and every page beneath it
this week, last week, next month, 2026-W43, 2026-11a period
overdue, no date, waitingone section only
includes …tasks whose words include these
in the last 7 dayshow far back finished tasks go
oldest firstopen longest first, each saying for how many days
calendara month, Monday first, each task on its due day (else its planned day)

A line the list does not understand is said back above it, never silently ignored. Ticking a task in a list ticks it where it was written, and the list asks again. Because the query is plain text in a fence, the page exports as valid Markdown, and Obsidian's Tasks plugin reads not done, done and description includes the same way.

On a page written as Markdown, a task list shows as its fence and is not drawn yet.

Reviews ​

The built-in Weekly review and Monthly review templates start with From the log: task lists of what was finished, what slipped past its due date, what has been open longest, and what was written and never planned. They are worked out when the page is opened, from the log, so nobody has to remember what happened.

Taskflows: steps under a task ​

Indent to-dos under a task and they become its steps. A task with steps is a Taskflow.

  • The task's line shows how far it has got: 1 of 3 · now: Legal review. Press it to go to the current step, which is the first step neither ticked nor cancelled.
  • When the steps before yours are done, your step is next reaches your inbox, once.
  • Ticking the task with steps still open leaves them as they are, shown with a dashed box as left open. Nothing is ticked on anybody's behalf. Tick the rest and Cancel the rest in the block menu finish them in one edit, yours.

My tasks and the journal's line show the same progress. Pressing it opens the page at the current step.

Drafting your update ​

Draft my update, in My tasks, gathers what happened for a period: this week, last week, or since your last update. All of it comes from the log, never from a model:

  • Done: tasks and steps you finished, including each occurrence of a repeating task;
  • Moved on: your Taskflows that advanced;
  • Slipped: due in the period and still open;
  • Stalled: a current step that has not moved for a week;
  • Waiting and New;
  • Written: the pages you wrote in;
  • Decided: the decision records decided.

Each line opens where it happened. Make the draft page writes it as a page under your own Updates page, each line a link to the task itself, never a copy. Nothing is sent; edit it, then share it however your team does. Next time, since my last update starts where this one ended.

In your calendar ​

Settings → Calendar feed of your tasks makes an address your calendar app can subscribe to: your open tasks with a day, each as an all-day event on its due day, or else its planned day, and marked as free time. The address holds a read-only key that works only for this feed. It is listed with your other keys, so you can revoke it there.

A workspace can refuse calendar feeds of its members' tasks in its settings. Feeds already made stop working too.

Tasks and the assistant ​

The assistant can list your tasks, add one and tick one, asking you first unless you have told it not to. Outside agents can list tasks through the MCP server and tick them over the API.

Coming from Logseq ​

Importing a Logseq graph reads DEADLINE: as the due date and DOING, NOW, WAITING and CANCELED as the task's state.

Not built yet ​

Changing one occurrence of a repeating task on its own, done tasks in the calendar feed, a repeating task as a recurring calendar event, a morning email of what is due, and a calendar layout for database views.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.