Tasks with inline comments %% ... %% are ignored in date-related queries (due on, due before, etc.) #3684
-
|
When a task line contains an inline comment using the Markdown syntax %% ... %%, the Tasks plugin fails to properly recognize the date field (📅 YYYY-MM-DD) on that line. As a result, those tasks don’t appear in queries involving date filters — such as due on, due before, or due after — even though they still appear in other types of queries like path, status, or tag. This becomes a problem when another plugin automatically adds data in that format, such as a Todoist Sync plugin that appends a unique ID like:
Even though this is a valid Markdown task, the line is ignored only in date-based queries because of the inline comment. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes, I'm afraid this is a known limitation of Tasks currently. Putting any text after Tasks emoji or dataview fields prevents the fields from being read. It's documented in several places in the user guide, the most detailed being in What do I need to know about the order of items in a task? and the following section. We are already tracking this ordering limitation in issue #1505. Please do up-vote that with 👍. Thanks. |
Beta Was this translation helpful? Give feedback.
Yes, I'm afraid this is a known limitation of Tasks currently.
Putting any text after Tasks emoji or dataview fields prevents the fields from being read.
It's documented in several places in the user guide, the most detailed being in What do I need to know about the order of items in a task? and the following section.
We are already tracking this ordering limitation in issue #1505. Please do up-vote that with 👍. Thanks.