Filter by task type rather than just done/not done

[sashinexists]

I've been using different types of tasks in my vault that at the moment I have no way of aggregating using Obsidian Tasks. Would be awesome if I could.

Here is a screenshot of what I mean:

It would be really great if it were possible to filter based on what's in between the [ ] so I could list for example Only priority tasks

[claremacrae]

Thank you for logging this.

For info, here is some discussion about how this is being done in the Dataview plugin. There’s a lot of useful information there.

blacksmithgu/obsidian-dataview#812

[sytone]

I have a pending PR where I am playing with this to allow more than just the done [x] and ToDo [ ] states. I have a few hard coded in there but it should really be driven by the user outside a standard set.

@sashinexists do you have a markdown version of all the tasks you are showing in the screen shot so I can understand them more with use cases?

[sashinexists]

Yup, here is my .md file with the documentation, it's the same as what's there.

# Task Management
An aggregated list of tasks can be found in [[Tasks]].
Tasks are represented in simple checkboxes like this:
- [-] To create one of these type `-[ ]`

When tasks are done they are checked like this:
- [x] This is a completed task
	- [i]  To create a completed tasks type `-[x]`

Tasks can have statuses other than checked or unchecked.

These include:
- [>] Forwarded (moved somewhere else)
- [-] Abandoned
- [i] Info: Not a task in of itself but information about one
- [?] Question: A question that I need to resolve, a potential problem
- [!] Priority Task
- [/] Partially complete
- [b] To buy: An item I want to buy, or a task that I need to buy something to complete
	- [i] To create this “to buy” checkbox you type `-[b]` not `-[$]`
- [g] Shopping List: This will be used for your groceries
	- [i] To create this checkbox type `-[g]` not `-[$]`

The way I use these, they are scattered throughout the vault. At the moment they are just all listed if they are not done, I don't have a more sophisticated way of aggregating and displaying them.

[sytone]

Ok, I can work with this, do you have a state transition map as well? Thinking about the way to iterate through the different states and a set of maps (perhaps configurable) would be good. That way when you click on the task depending on the initial state it could intelligently cycle to the next one rather than going through them all.

For example

Default Transision:
- [ ] ->  - [-] -> - [>] -> - [/] -> - [x] -> - [ ]

Other Transistions:
- [b] -> - [x]
- [g] -> - [x]
- [?] -> - [x]
- [!] -> - [x]
- [i] -> - [x]

[claremacrae]

See also issue #2 which has related material.

[claremacrae]

This was just released, in Tasks 1.23.0 🎉
https://github.com/obsidian-tasks-group/obsidian-tasks/releases/tag/1.23.0
See the links in that release page for copious docs and tips.

The new filtering options for statuses are documented here:
https://obsidian-tasks-group.github.io/obsidian-tasks/queries/filters/#filters-for-task-statuses

[rollingtatoo]

If this still can be of any help:
https://forum.obsidian.md/t/get-task-type-in-dataviewjs/54311/5