Tasks

How to Use Tasks

Create tasks as normal Markdown checkboxes and append date emojis: 📅 for due, ⏳ for scheduled, 🔺/🔼/🔽 for priority.

Build a dashboard by adding a fenced code block with the language `tasks` and one filter per line. The plugin renders a live, interactive list you can check off directly.

When Tasks Adds Value

Tasks suits people who capture actions in the notes where work is discussed but review them from central dashboards. It is especially useful for recurring and date-based work. If one short checklist in one note is enough, core Markdown checkboxes are easier and avoid plugin-specific syntax.

Example: A Focused Weekly Dashboard

Put this query in a planning note. It excludes completed items, selects tasks due before next week, sorts by due date, groups by source file, and limits the output. Clicking a result checkbox updates the original task in its source note.

not done
due before next week
sort by due
group by filename
limit 25

Common Mistakes and Boundaries

• Queries interpret metadata written in supported task formats; a date in ordinary prose is not automatically a due date.
• Filter large-vault queries by path, tag, or date before adding complex grouping and sorting.
• Test whether a recurrence should advance from its scheduled date or from completion before using it widely.
• Tasks is not a multi-user assignment system; shared-vault ownership and edit conflicts need separate conventions.

Repository Screenshots & Visual Preview

Rich preview screenshots and visual assets extracted directly from the official GitHub repository for Tasks:

An official Tasks example in which a query note gathers actionable items from across the vault.

Sources and Documentation

This guide was checked against the creator's repository and primary documentation.

• Tasks user guide
• Tasks query filters
• Tasks source repository