obsidian-tasks-syntaxlisted

# Creating Tasks ## Task Format Setting The Tasks plugin has two mutually exclusive ways to write metadata on a task line, chosen in **Settings → Tasks → Task Format**: - **Tasks Emoji Format** (default) — emoji signifiers, positional. Covered below. - **Dataview Format** — inline fields (`[key:: value]`), read by both Tasks and the Dataview plugin. Check which one a vault uses before writing a task line — check `taskFormat` in the Tasks plugin's `data.json` (`"emoji"` or `"dataview"`), or ask the user. Writing emoji signifiers into a vault set to Dataview format (or vice versa) means Tasks won't parse the metadata at all. ## Task Line Format — Tasks Emoji Format ```markdown - [ ] Task description 🔼 🔁 every week 🛫 2025-01-01 ⏳ 2025-01-05 📅 2025-01-10 ``` Order matters: description first, then priority, then recurrence, then dates. The Tasks plugin parses emoji signifiers by position — putting them out of order can cause misreads. Dates are always `YYYY-MM-DD` — natural language like "tomorrow" is not recognized on task lines (it only works in query blocks). ## Task Line Format — Dataview Format ```markdown - [ ] Task description [priority:: medium] [repeat:: every week] [start:: 2025-01-01] [scheduled:: 2025-01-05] [due:: 2025-01-10] ``` Fields are matched by name, not position — order does not matter. Each field is its own `[key:: value]` bracket; don't combine several keys inside one bracket. Dates are still always `YYYY-MM-DD`. **Emoji → Dataview field name: