Subtask - subtasks intelligence
Note: The original description was edited by Fredcamp staff
Possible hints we can provide here such as:
- closing a task when all subtasks are completed
- closing subtasks when a task is closed
- changing start due dates for subtasks when higher level (sub)task is changed to match deadlines for a parent task.
Ideal implementation will be to show a prompt once and if you say 'Yes' Freedcamp will start doing this action every time.
You can go to Settings somewhere in Tasks and change these prompts to stop doing auto changes or ask you every time.
Neal Thomas
shared this idea
-
Mike
commented
Our issue is that if someone moves over a task to complete, the subtasks don't automatically register as complete. It ends up being messy as far as tracking if a task is truly complete.
-
Anonymous
commented
I would agree with Neal here. Subtasks are used with the Task as a container, and hence all the 3 suggestions from Neal are valid.
-
@Neal - even here at Freedcamp this is not the case. We start a task often and add subtasks later to branch out while a top-level task is still NOT a container and should not be closed but a signal for an assignee (say developer) that specification (subtask), design (subtask) are completed and he/she can continue doing top-level task.
-
Neal Thomas
commented
I don't think it needs to be a subsystem. When you create a subtask it becomes "parts" of task. So when the "parts" are complete the task should be complete. There doesn't need to be prompts because when a user created the subtask it will know when the subtasks are complete to mark the task complete.
