[TW-232] More informative recurrance messages
Aikido Guy on 2011-03-24T14:14:48Z says:
> task add "Pay bills" project:Blah due:yesterday recur:2weeks > Created task 50.
I expect a new task that has a due date of yesterday (March 23rd) and another task that will occur 2 weeks after yesterday's task (April 6th). After some fiddling, I can determine that yesterday's task is 51 and the task in 2 weeks is task 52. Neither of them have ID's that are the same as task reported to me (i.e. 50). For me, I would prefer that I did not need to perform this "fiddling". When I created the task above, it would have been nice if task informed me what it was doing right away so that I am aware of what is happening "behind the scenes".
Something like:
> task add "Pay bills" project:Blah due:yesterday recur:2weeks > Created task 50 as the main task for accounting purposes. > Spawned task 51 from 50 since that is the first task for you to complete. > Spawned task 52 from 50 since it also occurs within the recurrence period.
I don't care about the future tasks popping up into my task list automatically. I am just concerned that it is difficult to track what task has done this first time that I have added a recurring task. Especially for a new user like me, I get confused easily and such a set of messages would help me to understand more clearly.
Migrated metadata:
Created: 2011-03-24T14:14:48Z
Modified: 2015-09-01T23:44:06Z
Bryce Harrington on 2011-05-06T08:00:46Z says:
Ditto. The lack of feedback makes recurring tasks a bit mysterious.
Extra verbosity would be nice also when marking tasks done, something like:
task done 51 Completed 51 'Pay bills'. Marked 1 task as done. Next instance of 'Pay bills' is task 52 and will occur April 6th.
Paul Beckingham on 2012-02-03T04:55:14Z says:
Deferring. There is likely to be an overhaul of recurring tasks soon, and don't want to mess with it until then.