filter and group by YAML frontmatter property

[midas0441]

Hi,
I'd like to filter and group my tasks by Project or Area. I use YAML frontmatter to specify proj and area. Does Tasks have a query to filter/group by frontmatter? To take it up a notch, Of course, it would be even more powerful if individual tasks could be written with user-specific inline properties for proj, area, or whatever else the user wants. If these features do not exist, is it in the foreseeable feature roadmap for Tasks?

[claremacrae]

Hi @midas0441, thanks for using Tasks and for the question...

I'd like to filter and group my tasks by Project or Area. I use YAML frontmatter to specify proj and area. Does Tasks have a query to filter/group by frontmatter?

No it doesn't. I recommend using the GitHub search feature in a project... it allows search by area, like Issues and Discussions.

Here are the results for YAML, where you can see existing requests, and up-vote any open ones....

https://github.com/search?q=repo%3Aobsidian-tasks-group%2Fobsidian-tasks+yaml&type=issues

https://github.com/search?q=repo%3Aobsidian-tasks-group%2Fobsidian-tasks+yaml&type=discussions

You can repeat the search for Frontmatter - you might find more tickets to up-vote.

(In Issues, use 👍 to up-vote)

To take it up a notch, Of course, it would be even more powerful if individual tasks could be written with user-specific inline properties for proj, area, or whatever else the user wants. If these features do not exist, is it in the foreseeable feature roadmap for Tasks?

I have read that several times and do not understand what it means. Please provide some example markdown that shows what your inputs would be, and what feature you would like from Tasks. Thanks.

[midas0441]

Thanks for clarifying that filtering/grouping by frontmatter property is not available.

By inline property, I'm referring to a feature of Dataview. For example, a task such as:

• sample task (proj::example)

has an inline property (proj) whose value is example.

[claremacrae]

I think that is likely covered by:

• Custom user defined key::value pairs with custom emoji to be added to the auto-suggest menu and to be used in queries #1507