Get AI summaries of any video or article — Sign up free
Project Management In Obsidian: NEW (and it's awesome) thumbnail

Project Management In Obsidian: NEW (and it's awesome)

5 min read

Based on Obsidian Explained (No Code Required)'s video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Install Task Notes and configure a dedicated tasks folder plus a separate archive folder to keep completed work organized.

Briefing

A single Obsidian plugin—Task Notes—aims to replace a patchwork of task managers by combining agenda views, calendar time-blocking, time tracking, and a built-in Pomodoro timer in one workflow. The pitch is practical: instead of juggling separate tools for tasks, scheduling, and focus sessions, users can tag notes as tasks, drag them onto a calendar, track how long work actually takes, and see that time roll up into statistics.

Setup starts with installing Task Notes and configuring where task files live. Tasks default to a dedicated folder (task notes/tasks), with completed items moved into a separate archive folder to keep the workspace tidy. The plugin identifies task notes using a tag (the “task” tag), avoiding more complex property-based approaches. To prevent accidental interference with templates, the templates folder is excluded so completed tasks don’t cause template notes to appear as done. Interaction behavior is tuned so single-click edits a task while double-click opens the note.

The configuration also defines how task status and color coding work. Statuses map to a simple lifecycle: to-do (red), doing (yellow), and done (green), plus an extra “archived” state shown in black. Priority is kept minimal (high/normal/low), and the creator avoids adding extra custom fields to keep the system lightweight. Defaults matter: new tasks start as to-do with normal priority, and the “context” concept is used to represent where work belongs (e.g., home vs. work, or different client channels). Contexts are left flexible rather than forced onto every task via defaults that would later require cleanup.

Calendar behavior is tuned for planning rather than browsing. The default calendar view is weekly (not monthly), with Sunday as the first day and week numbers enabled. The calendar shows scheduled tasks and due dates, and it supports time entries so time logging stays visible. Time blocking is enabled so tasks can be dragged onto specific time slots. For Pomodoro alerts, notifications are routed to the system level (not just in-app) so timers still notify when focus moves to other apps.

Once configured, Task Notes exposes multiple views through the command palette: an agenda view, a Kanban-style board (“conbon” in the transcript), advanced calendar views, and statistics. Natural-language entry lets users create tasks quickly—typing “due Friday” and an estimate like “4 hours” automatically parses dates and durations. Tasks can appear in multiple calendar locations when they have multiple scheduled instances, and status changes propagate across views (dragging a card to doing or done updates the agenda and board).

Time tracking and Pomodoro are integrated into the same task system. Starting time tracking ties the timer to a specific task, and the elapsed time then feeds into task and project statistics. The interface supports both a front-and-center timer and a sidebar timer, with a blue indicator showing when tracking is active. The workflow is positioned as a replacement for older Obsidian plugins (tasks, reminders, and a deprecated projects plugin), consolidating task management, scheduling, focus sessions, and reporting into one place. The transcript also mentions optional integration with Morgan for further filtering, though it’s treated as advanced and not required for the core setup.

Cornell Notes

Task Notes for Obsidian consolidates project-style task management into one plugin: agenda and calendar views, Kanban-style status boards, time blocking, time tracking, and a built-in Pomodoro timer. Tasks are recognized via a simple “task” tag, stored in a dedicated folder with an archive folder for completed work. Statuses (to-do/doing/done plus archived) and minimal priorities drive consistent color coding across views. Calendar settings emphasize weekly planning, show due/scheduled dates and time entries, and enable drag-and-drop time blocks. Time tracking attaches to specific tasks and rolls into statistics, helping users compare estimated effort with actual time spent—useful for client billing and planning efficiency.

How does Task Notes decide which notes are tasks, and why does that matter for filtering and templates?

Task Notes treats a note as a task when it contains a specific tag—“task” in the setup described. That tag-based approach lets the plugin filter and display only task notes without relying on more complex properties. Templates are excluded from the plugin’s scope so template notes don’t accidentally appear as completed tasks when task completion triggers view updates.

What’s the difference between due date and scheduled date in this workflow, and how is it used?

The transcript draws a distinction: the due date is the day something must be delivered/finished (e.g., to a client), while the scheduled date is the day work is planned to happen. The creator sets due dates by default but leaves scheduled dates empty because most tasks are planned for the future rather than worked on immediately.

How do contexts function in place of “projects,” and how does filtering work afterward?

Contexts act like a lightweight project system. Instead of a separate projects plugin, the creator uses contexts such as “YouTube,” “personal,” or “work” to group tasks by where they belong (clients/channels). Later, filters can restrict views to only one context (e.g., show only YouTube tasks). Saved views then let switching between context-specific calendars/boards.

What does time blocking change about task planning in Task Notes?

Time blocking enables drag-and-drop scheduling on the calendar. Tasks can be placed into specific time slots, and the calendar reflects those blocks. The plugin also supports creating time blocks (even when not tied to a task), though the creator says they don’t personally use that feature much.

How does time tracking connect to tasks, and what does it produce for later review?

Starting time tracking selects the task being worked on (e.g., “record this video”). A timer runs while work is happening, and the elapsed time is recorded against that task. The lower-right tracking indicator and the statistics view then show totals (e.g., time tracked for tasks/projects during the week), supporting better estimates and client billing clarity.

What Pomodoro-related settings are adjusted to make timers reliable during real work?

The setup increases alert sound volume to 100 so the Pomodoro beep isn’t missed over music. It also enables system-level notifications rather than in-app notifications, so alerts still arrive when the user is working in other apps (like a browser or design tools) instead of staying inside Obsidian.

Review Questions

  1. When would you use a context filter versus relying on the default “all tasks” view, and what does saving a filtered view accomplish?
  2. How should you decide between setting a due date and setting a scheduled date for a task?
  3. What information from time tracking is later used in statistics, and how does that help with planning or billing?

Key Points

  1. 1

    Install Task Notes and configure a dedicated tasks folder plus a separate archive folder to keep completed work organized.

  2. 2

    Use the “task” tag to mark task notes, and exclude the templates folder so templates don’t get treated as completed tasks.

  3. 3

    Set simple statuses (to-do/doing/done) plus an “archived” state so color-coded task state stays consistent across views.

  4. 4

    Enable weekly calendar defaults and time blocking so tasks can be dragged onto specific time slots and planned at a glance.

  5. 5

    Use contexts (e.g., YouTube vs. personal) as the primary grouping mechanism, then apply filters to switch between focused task sets.

  6. 6

    Turn on system-level notifications and increase alert volume so Pomodoro cues still work when switching to other apps.

  7. 7

    Start time tracking against a specific task to feed task/project statistics and compare estimates with actual effort.

Highlights

Task Notes combines agenda views, calendar time blocking, time tracking, and a Pomodoro timer in one Obsidian plugin—aimed at replacing multiple separate plugins.
A tag-based system (“task” tag) determines which notes become tasks, while excluding templates prevents template notes from being misclassified.
Contexts act as a lightweight alternative to projects: filter and save views to jump between client/channel task sets.
Time tracking is tied to the active task and later surfaces in statistics, supporting better estimation and client billing decisions.

Topics

  • Task Notes Setup
  • Obsidian Task Tagging
  • Time Blocking
  • Pomodoro Timer
  • Time Tracking Statistics

Mentioned