Explain the problem as you see it
I’d like a smoother, more native way to do recurring tasks.
Why is this a problem for you?
It feels bad to push an extra button and always have the native checkbox open and lonely when doing recurring tasks.
Suggest a solution
Please let us trigger commands when a checkbox is checked 
. This would open up a lot of workflows!
2 Comments
Oh interesting idea. Could automatically move my archived tasks into a node!
I'd like this idea for a different reason: I want to be able to "chain" tasks, so that task B becomes "active" once Task A is done. I can add a field to #task where you put the task to be observed. Once "done" is triggered on task A, a command will search all tasks and see if they are observing this task and if so change their status.
The bigger picture is that I only want to see tasks that are relevant for me now. Many tasks can live in a backlog until they become relevant. And this could be automated more. However the only way most task apps allow this is with time, by setting dates. But I want the tasks themselves to be linked. A "done state trigger" would help to build this alternative!