Do not delete the parent when you delete the last child!
I may have a project or program where I have not determined any more next steps, but I am not ready to close out. If I delete the last child, the parent goes away and then I forget about the project for a while. I can't afford to do that!
Thanks!
Fixed on production, there is an option in Profile=>Customize to enable this behaviour
-
arvjut commented
Option to disable "Close parent task when the last child is closed" does not work on Mobile UI.
-
Raj Patel commented
Works for me as well. Thanks very much.
-
OneLessTask commented
Works so far for me. Very nice improvement. Thank you.
-
Charles commented
I like the idea of putting a property on each node that allows me to lock it open. Then I can choose which nodes will or won't auto-close. Take it a step further and let me set the default value for new nodes. By list, even.
-
OneLessTask commented
In my previous post, I was trying to use HTML entities to show the paragraph tag. It should be <P>.
-
OneLessTask commented
I have a temporary work-around while the "fairies" ponder a permanent solution. If you create a task and just put a paragraph tag in the description (<p>), it will show a blank line. I move that line to the end of the project and create any new project tasks below the project title (shift+enter) or above the blank line (alt+enter). This will work for me until I get a user preference checkbox to clear parent tasks when completing the last item.
Hope this helps.
-
S M Sabri Ismail commented
I agree with Bjarke Ebert and Vadim Echim, regarding closing the parent task myself.
-
Bjarke Ebert commented
I agree that closing the last subtask should not close the task.
Additionally, as Vadim Echim points out, the application should not take away the satisfaction of closing the parent task youself ;-)) -
Raj Patel commented
I found a temporary work around. If you move the last sub-task out from under the parent (shift-tab) then cancel it, the parent stays alive.
-
sbatishchev commented
Saw your Twitter request to vote on that. I am actually voting for this change. I use Checkvist as GDT organizer. I have "Inbox" as a list, and "On the internet", "At home" as top level tasks (otherwise my list of lists will be huge). I really don't want "At home" to be constantly crossed out and moved to the bottom. Also it happens quite a bit that I create a project (in "Projects" list) and creat 3-5 most important subprojects under it (kind of not what David Allen suggests, but some of my projects are just big otherwise). Again, when the last subproject is crossed out, it usually means that more needs to be created (or just that all main things are done), not that entire project is done.
-
Vadim Echim commented
I support this reuqest - it's a real problem - completing the last subtask, automatically completes (crosses out) the parent task. The completion of a parent task (which is project for me), should be a controlled action, as it gives also satisfaction of completing the project :)
-
Tyson commented
I agree on this. I encounter this problem many times and usually it means I have to recreate the parent task in order to keep it on my list.
-
Raj Patel commented
Closing out the last child doesn't mean the task is done, just that all current action items for it have been completed. This is especially true for me as I have several long term projects.
-
Jacob commented
We constantly struggle with this, so we just leave subtasks open, even if they are completed. Sometimes, depending on the level of the task in the hierarchy, it is valuable to not have any subtasks at a particular time. But if we EVER had a subtask at any point, we would have to delete it instead of closing it out in order to keep the parent task from closing out.