This has actually been asked before in
However, the feature itself has not actually been launched, or at least I disagree with the statement that it has been launched, and I can’t comment in that post to say so.
The request is for the ‘check if’ condition (and without AI involvement) to use relative dates rather than the static dates that surely nobody would ever add to a rule unless they wanted to spend all their time editing the rule… I don’t want to check if the task is due before the 9th of October, I want to check if the task is due before tomorrow.
This is not the same as using the rule trigger that has tasks approaching their due date; I want the rule to trigger as soon as the task is added to the section, then assess when the due date is, and then it can decide properly what to do about it. In this case I don’t want to use the overnight ‘approaching’ triggers.
Basically, since the ‘check if’ field does not use relative dates, and that’s the feature request, I don’t agree that the feature can be marked as shipped, and so I am requesting it again.
Rules need relative dates throughout, or they are unmanageable. I haven’t yet thought of a use case where a static date could be useful at all. It just seems obvious to get this actually shipped, and not have to use AI to recreate the functionality at great computing expense.