[EX-63] recurrence for dependent tasks

[taskwarrior]

Saša Janiška on 2013-09-18T06:09:53Z says:

Sometime ago I asked on the mailing list and was advised to submit ticket...

I'd like that TW can do the following: let's say there is a task (maintask) which occurs monthly and depends on two other tasks (task1, task2) and I'd like that each month TW would generate a new set of tasks with appropriate deps, e.g. maintask' which is next month's occurence of maintask and task1' & task2' which
are next month's occurences of task1 and task2 respectively?

So, the TW should show something like:

maintask dep:task1, task2 due:somedate recur:1month maintask' dep:task1', task2' due:somedate+1month recur:1month

Paul replied on the list that it's not easy feature and

"There might have to be restrictions, such as maintask having the same recurrence period as task1 and task2."

which is fine with me and it would be improvement in any case.

Sincerely,
Gour

[taskwarrior]

Migrated metadata:

Created: 2013-09-18T06:09:53Z
Modified: 2015-03-14T15:37:41Z

[jcrben]

this seems similar to #178

also possibly helped by https://github.com/JensErat/task-relative-recur but probably not

[madduck]

Unfortunately, the task-relative-recur plugin suggested by @jcrben doesn't address the problem herein, as well as mentioned in #178.

It's unfortunately non-trivial to determine the dependency for sub-task B on creation, because it cannot be taken for granted that at the time B is created, exactly one instance of A exists (there might be more), and there also exists no pointers from parent tasks to their offspring (only from offspring to parents).

I've thought about this a while some weeks ago, and I came to the conclusion that probably the best way to solve this is by allowing tasks to be nested. So you'd have one parent task that consists of three subtasks, and then a child with three subtasks is spawned, and when all three of them are completed, then the child is considered completed. Potentially, a new sibling could be spawned earlier. But the important thing is that I think the subtasks need to remain grouped, e.g. parent task 64 spawns child 65 with tasks 65.1, 65.2, and 65.3, and when 66 is spawned it gets 66.{1,2,3} etc.

[djmitche]

@carmiac has proposed a major revision to recurrence support in https://github.com/carmiac/taskchampion/blob/798cec2b40f13c420ef6358e4d99b251e58249de/docs/src/iterative-tasks.md. If you're following this issue, please have a look and comment in GothenburgBitFactory/taskchampion#729.