Obsidian Tasks Community Plugin Series, Part 1 - Global Task Filter

Obsidian’s Tasks plugin can automatically turn specific checkbox items into “real” tasks—if a single setting called the Global Task Filter is configured correctly. That global hashtag (and its related emoji) determines which checkboxes get indexed by task queries, which then controls what appears in task lists and dashboards. Getting this right early prevents the common frustration of seeing some items show up in queries while other checkboxes—seemingly similar—stay invisible.

The walkthrough begins by installing and enabling the Tasks community plugin in a fresh Obsidian vault. The key step is setting the Global Task Filter: any checkbox item that includes the chosen hashtag (the example uses “#task”) is treated as a task across the vault. The creator keeps other options at defaults for now—such as leaving preset/status/date behavior unchanged—so the demonstration can focus on how the global filter works. A second important toggle is “remove global filter from description.” When this is off, the hashtag remains visible in task text; when it’s on, the hashtag is stripped from the rendered task description after indexing.

To show the difference, the transcript creates two kinds of items: plain checklist entries (typed as normal checkboxes without the hashtag) and tasks (checkboxes that include the hashtag). Only the hashtagged items appear when a basic Tasks query is created using a fenced code block labeled “tasks.” The simplest query returns the three tasks created with the global hashtag, while the plain checklist items do not appear—because they lack the global filter marker.

Next, the “remove global filter from description” option is turned on, requiring an Obsidian restart. After restarting, the same tasks query no longer displays the hashtag in the results, even though the tasks still exist and are still indexed. This gives a cleaner visual presentation without changing which items qualify as tasks.

The demonstration then addresses what happens when the global hashtag itself changes. After switching the global filter away from “#task,” the existing tasks disappear from the query because they still contain the old hashtag. Adding a new checkbox using the updated hashtag makes it appear again. The practical takeaway: the global filter is effectively a gatekeeper for task discovery, so changing it can hide previously created tasks unless they’re updated or recreated.

Finally, the transcript shows two ways to create tasks: manually typing the global hashtag into a checkbox, and using the Tasks modal from the command palette (“create or edit task”), which inserts the hashtag automatically and supports richer fields like due dates, priorities, recurrence, statuses, and dependency-style “before/after” relationships. The overall message is that the global task filter should be chosen deliberately, because it shapes how tasks are recognized, displayed, and managed—whether the plan is to keep the same vault or evolve the system without migrating everything.