Filter tasks by higher-level tag

[johnghill]

Coming from Logseq, which is a slightly different block-based philosophy, I like to enter meeting notes (and tasks) in my daily journal, and then surface them using Queries within dynamic project pages. This means my daily note will contain headings for each meeting I attend on that day, with associated tasks indented beneath those headings.

For example (outliner plugin enabled):

# Daily Note
## Meeting of #project/org/A
	- Agenda
		- Torture
	- Meeting notes 
		- [ ] John to do this action #action/todo
		- [ ] John to circulate these minutes #action/report
## Meeting of #project/org/B
	- Agenda
		- Different type of torture
	- Meeting notes 
		- [ ] John to do this action #action/todo
		- [ ] John to circulate these minutes #action/report

I would like to surface tasks on their relevant project pages (project/org/A and project/org/B) and sort them by action tag (#action/todo or #action/report)

For example, the dynamic project page for project/org/A might look like this:

# Query: All REPORT tasks

```tasks
not done
tags include #action/report
```

My question is this: how can I ensure that only #project/org/A tasks are returned by this task query?

Note that #project/org/A does not appear inline with the task, but is indicated by the hierarchy within which the task is located. I could add an additional project tag to each task line, but that would be cumbersome and cluttered.

[claremacrae]

Note that #project/org/A does not appear inline with the task, but is indicated by the hierarchy within which the task is located. I could add an additional project tag to each task line, but that would be cumbersome and cluttered.

I am not exactly sure that I understand the detail of what you are asking for, but in case you don't already know:

• Tasks only searches the properties on the task lines themselves
• The only exception to this is that it's possible to use dates in file names to infer scheduled date

There are already requests for tags and other values to be read from YAML/frontmatter/properties, but that is unlikely to happen any time soon.

So your best bet is to use dataview's facilities to generate your task queries:

• Find tasks in notes with particular tag

[claremacrae]

I think I'm stuck on the meaning of "higher-level tag" - but if you can do it with string calculations, then you can also write a custom filter. There's a variety of examples in Tags section of the Filters page.

[johnghill]

In the example shown, the tag #project/org/A is located at a higher level (hierarchically) than #action/todo. I am not sure if this distinction is meaningful in Obsidian but it matters a lot in Logseq (where hierarchical relationships are inherited).

## Meeting of #project/org/A
	- Agenda
		- Torture
	- Meeting notes 
		- [ ] John to do this action #action/todo
		- [ ] John to circulate these minutes #action/report

[claremacrae]

In the example shown, the tag #project/org/A is located at a higher level (hierarchically) than #action/todo. I am not sure if this distinction is meaningful in Obsidian but it matters a lot in Logseq (where hierarchical relationships are inherited).

## Meeting of #project/org/A
	- Agenda
		- Torture
	- Meeting notes 
		- [ ] John to do this action #action/todo
		- [ ] John to circulate these minutes #action/report

Thanks, but I don't know Logseq, and don't have time to spend learning other systems in order to do support for Tasks.

In Tasks terms, with that example above, both the tasks would be found by:

```tasks
heading includes #project/org/A
```

[johnghill]

Thank you @claremacrae , your suggestion of including a heading search is very helpful.

[claremacrae]

Meeting of #project/org/A

You can also do heading searches, if the tag is always in the heading immediately before the tasks...