The filters currently include “in: open” and “in: closed”. It seems fine to keep those as they are, but right now, invalidated tasks are buried in the “in: closed” option.
It would be great to have an “in: invalidated” option. It seems to me that this would basically just involve adding an option for `status=2` alongside `status=0` and `status=1|status=2` (pseudocode).
Hello Jordan,
Thanks for the suggestion. At the moment, in:closed condition includes the invalidated tasks, too. If we add in:invalidated, this might add a confusion as in:closed will include both. We probably don’t want to change this, for backward compatibility.
Out of curiosity, what is your scenario, why would you want to search/filter for invalidated tasks?
Kind regards,
KIR
I use “invalidate” for tasks I decide not to do. Occasionally, I will want to look over those decisions to see if there’s anything there that I want to open back up. I don’t like marking things complete unless I actually do them. If you choose not to add it to the webpage, that’s fine; just a suggestion. I am able to get the functionality using the open API.