Filter exclude for "super-items"

obsidian-tasks-group / obsidian-tasks

Task management for the Obsidian knowledge base.

https://publish.obsidian.md/tasks/

MIT License

2.48k stars 230 forks source link

Filter exclude for "super-items" #1634

Open Orgams opened 1 year ago

Orgams commented 1 year ago

⚠️ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description

Add a new filter option which could be called "exclude super-items" which only displays tasks that are unfinished leaves in a "tree" of tasks (list of points and sub-points).

If all the leaves of a branch are finished the common spot "becomes a leaf" to be displayed.

✔️ Solution

When I have a stain I divide it into sub-tasks, so it's the smallest stain that I have to do first. Once all the subtasks are done it is useful to see the grouping task to confirm that it is finished. I can have more nesting level.

example :

path includes 1_Inbox/Recette crèpes
not done
exclude super-items

❓ Alternatives

No response

📝 Additional Context

No response

claremacrae commented 1 year ago

Thank you! This is a very nice write-up of that answers a lot of the questions asked in the highly-up-voted #60.

Just to set expectations, implementing this would require a total re-design of the plugin's code, and so it is unlikely to happen in the immediately foreseeable future. but I would love to see it done at some point.

claremacrae commented 10 months ago

In view of this size of the backlog for this project, and the demotivating effect of a very long backlog on volunteer energy levels, I'm going through a slow process of reviewing tasks for things that are one or more of the following:

unlikely to be realistically achievable, from the design of the current code, and the planned future refactorings
not sufficiently high priority to a broad community of users, based on the feedback I receive from a variety of sources
do not fit the core purpose of the Tasks plugin
are better covered by a different plugin - to share the development and maintenance effort

So I'm marking this one as 'not planned'. This doesn't mean 'won't fix' - it means not likely to be done in the foreseeable future.

Orgams commented 5 months ago

Hello,

Thank you in advance for your wonderful work!!! Then I just realized that an id and depends on id system has been added and it addresses the problem very well!

merci encore

claremacrae commented 5 months ago

I’m delighted to hear that the dependencies mechanism is working for you.

As it happens, work has now started on adding support for nested tasks. So I’m reopening this as we will eventually reach a point where this becomes possible.

claremacrae commented 5 months ago

/CC @ilandikov for info…

claremacrae commented 2 weeks ago

Is the new show tree instruction in Tasks sufficient for you @Orgams - just released in Tasks 7.12.0.

See the documentation to find out how it works, and how to enable it either in individual queries... or if you wish, add it to your Global Query to turn it on by default.

This rendering step is the first in a series of steps to fully support nested tasks in Tasks - it is already really very useful.