+ Add Question

Bug: combining multiple date constraints and a label

The result for "(over due, today, no due date) @personal" includes an overdue task that is not labeled @personal.

Most curiously, leaving out "today" and thus only searching for "(over due, no due date) @personal" does not include that task.

Very strange behavior.

All responses

David Trey  staff
Replied on Jul 14, 2013 - 22:55 UTC

Hello Alex,

Although some basic date-based search may not require boolean operators and you can just use a comma between them, please always use these operators for more complex searches like this one.

In this case, the correct formula is:

(overdue | today | no date) & @personal

or a shorter version:

(od | tod | no date) & @personal

Best regards,

Alex Bepple  premium
Replied on Jul 15, 2013 - 05:34 UTC

Thanks, David.

This should be in the help though! And, it should be clear when commas work and when not. Or, for simplicity’s sake, either make commas work like pipes or get rid of them altogether.

Also, something else is going on.

(no date | overdue | today) & @personal

works fine for me. However, your suggestion

(overdue | today | no date) & @personal

produces an empty list. This is most confusing. Boolean operators should be commutative!

Finally, the heading for the search results of

(no date | overdue | today) & @personal


Tasks with no due date & @personal

This is wrong. ;)

David Trey  staff
Replied on Jul 15, 2013 - 11:24 UTC


I've passed the issue with the od, tod, no date search to the developers.

As for the header - we're aware of this issue, but we'll implement an option to save, store and rename favorite searches (just as on mobile) which will show the name of the saved search in the header.

Best regards,