Allow a task (eg mow-lawn) depend on another (eg buy-fuel). The dependent task is hidden until the first task is done. This will reduce clutter, and allow some structuring of tasks.
Neil Rogers commented
This seems to be a basic function of task management. All tasks can not be done at the same time, some require other tasks to be completed first and all tasks are not always done by the same person (so the built in sub task feature would not work).
"I use Wunderlist to help me build homes" Wow! That's pretty intense. I thought a project of that scale would use something more robust out of the box with gantt charts and what not.
I've often thought about developing my own task management software because Wunderlist has so many things right but so many things missing.
This is one of those things that makes me scratch my head... Dependent tasks are constantly popping up and the only way to show for this is using a task's todolist. The problem with this is that you can't SEE any of this at a glance.
A combination of a task list manager like Wunderlist and Trello/Kan Ban board would be very powerful.
I would actually opt to not hide the tasks in waiting... but to have them flagged somehow as not available to work on yet. That way I can easily see the tasks that I CAN do, but also which tasks are being held up by certain members of our team.
This sounds like subtasks which initself are nested tasks for the main to do.
A subtask should have it's own asignement possibility and due date where the due date for a subtask could be a fixed date or depending on the previous subtaks.
I use Wunderlist to help me build homes where task dependencies are crucial. This would take Wunderlist to the next level. Please add this feature. Let us know if you're considering it please?
Matthew Petty commented
Just a link from one task to another would be a start. I want to be able to see straightaway what needs to be done first. It's like in bug trackers, where one issue is blocking others.
Miriam Schoon commented
Requesting this feature is why I'm here in the first place, thank you for suggesting it, you obviously have my votes now :)
To the Wunderlist team, please, please, please, please incorporate this.
A lot of the other suggestions are great, but this is the only thing I can think of that would actually make my Wunderlist-life so much more structured and easier :)
But I want to be able to see the tasks in some form.
Aldo Vieira commented
Here is my version:
Some tasks are related in a way such that task B can't be started before task A is done. For example if B is "make scrambled eggs" and A is "buy eggs". Let's call B a "waiting task" and A a "trigger task". B can have several trigger tasks.
Looking through a to-dolist to figure out which tasks to do next is a challenging job. Your eyes will have to read a lot of tasks of different priorities, and some of which can't be started since they are waiting tasks.
What if you could drag one task on top of another to mark it as a waiting task. Then, this task would appear slightly hidden behind the task it's waiting for. Maybe the stack of waiting tasks behind a trigger task could look like a card stack.
By tapping the expand button on the trigger task, the waiting task appears indented below it. You can now drag and drop the waiting task on it's other trigger tasks. A copy of the waiting task will be slightly hidden behind each of the undone trigger tasks. When a trigger task is done, the waiting task will appear only behind it's other trigger tasks. Finally, ít will become a regular task in the to-do list.
To be even more advanced, waiting tasks can also be trigger tasks for other tasks.
What would we gain from this? Not having to consider (irrelevant) waiting tasks every time we look for things to do. A tidier to-do list helping you to do the right things first. A more effective app.
Adam Bradley commented
Subtasks (with sequence) along with the ability to set dependencies between major tasks would be awesome! Especially useful when I have lots of larger tasks that have a common sub-task which isn't my speciality and I want to assign it to someone else.
Ken Udle commented
This would be excellent for situations where I have an idea for a project but am not yet ready to decide on start end dates.
I agree that it is better to hide dependent tasks or have the option of showing them as dim, faded, grey or something to distinguish them when scanning through the list. If dependent tasks have a date attached, the date should update either automagically or a dialog should ask if you want to move back dependent tasks. This could happen without adding clutter to the user interface. Although dialogs are temporal clutter, I guess. :)
I don't understand why this feature is so hard to find in task managers. I don't want to see some tasks until the task they depend upon is complete. How hard is that?
I don't want them to be subtasks as that's completely backwards to me, but I don't think dependency should care if it's a main task or a subtask. It should be independent of hierarchy. "Don't show this task until this other task is complete, regardless of where/what it is."
I've tried so many task managers and none of them have this simple concept. Hiveminder has it, but is not usable for me (and appears to be dead anyway). Wunderlist is perfect in nearly every other way except for this.
I agree with David: dependent tasks should not be shown as subtasks. The main point of this idea is to reduce number of visible tasks by hiding those tasks which are not doable until something happens (In this case until some other task is done).
David Chelimsky commented
I love the idea of dependent tasks, but I don't think they should be shown as subs of the "main" task (at least not in the current implementation of subtasks, which only appear when you have the Detail view open and don't support attributes like due dates, notes, etc) or hide the dependent task. Both of those UI choices make assumptions about the relationship between tasks that I don't think play out all the time. For example, imagine I'm planning an event that involves hiring a band. I want to have the band booked by a certain date, but I want to be sure to check out three bands that were recommended to me. In this case I'd want all four tasks (check out band 1, 2, 3, and hire a band) visible at all times in order to give me a better sense of their relationship and what remains to be done.
They would be showed as sub-tasks of main tasks