Consider heading sub-levels for task finding #1167
Closed
Replies: 2 comments 1 reply
-
Hi, thanks for the idea. It's a popular one - it has been asked for a few times before. There are some good suggestions in #209. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Marking as duplicate of #209, just to reduce the volume of things to track. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've noticed that when using the "heading" filter, it only returns tasks which are into such heading level, but doesn't include the tasks which could exist at sub-headers of the queried one.
I think you could add a setting to allow including all tasks at sub-headers of the queried one. Even such a setting could specify the relative depth of subheaders to take into account to return as a result of the query.
This would be quite useful for those (like me) who tend to distribute tasks along files structured using different heading levels.
Best regards
Beta Was this translation helpful? Give feedback.
All reactions