Add functionality to create dependencies
Add functionality to link tasks with dependencies. One the upper level task is complete the tasks that are dependent on it would become active and notify those task owners.
Russell Aldridge commented
This is a must for any decent planning software. Please get on it.
It would be great if the sub-task could have its own fields, e.g. due date, assigned to, time to completion (hours), etc.
Sergio Nesbitt commented
Dependency linking would be a huge update, please do it and give us this ability. Would be easier to sell.
Hey Microsoft, simple dependency functionality ahs been request as far back as 2016. what's the status on this? In the works? being ignored? Buy Microsoft project? Would be nice to know as this is a simple feature that has been outstanding for quite some time now.
Once the child tasks are completed the parent task has a percentage of how many has been completed.
This would go hand in hand with
Yes, please. And the ability to add due dates to each dependency.
Very much needed
Dependencies please - This has to be built into any project planning tool. Even if you could add additional functionality to create bucket subcategories visually that would be a good start. List them in a navigable tree structure etc. You could then build a dependency stack of tasks by sub bucket initially. Given current functionality that shouldn't be too much work.... should it? :)
Can you please add Task linking or a process flow functionality.
Maarten Dekkers commented
Simply referencing to another task would be sufficient.
Lisa Murmann commented
Probably more see dependencies as described in the gant chart post - to finish this major milestone we need each of "x" subtasks with their own assignees and timelines completed - you should be able to filter and report only on major/parent tasks to make status reporting easy. so a build out of current checklist functionality - I like the idea further down that you could promote a checklist item to a child task...
Thomas Henkelmann commented
I would not try to duplicate functionality that exists in Project Online or Project Professional i.e. build a schedule with predecessors and successors. A simple "this task belongs to..." with a list or maybe even only one other tasks would already help a lot. And it could be integrated into the promotion of checklist items: when you promote a checklist item to a new task it could automatically inherit "I belong to my former task".
Jakub Havel commented
As for task dependency it would be useful to integrate it to checklists – right now the checklist feature is not that useful without notifications.
If checklists in tasks would notify workers and get individual deadlines, that'd be awesome, because the task itself would express the task definition and process including deadline (of the whole task) and checklist items would express individual steps. Maybe it would be awesome to add possibility to assign cheklist item to certain person?
So in the end it would be more than great to transform checklists into sub-tasks with its own people assigned, deadline set and notifications available 😊.
explanation of notifications:
– notify person assigned to following sub-task, that he/she can start working on it
– notify "everyone" about progress on the task
this is a very important feature that I'd like to be added.
Deb Walther commented
I use this when I created my old SharePoint Project Sites via a Task list. I'm lost without it.
Michael Bongard commented
This would be a very important feature. Its present omission precludes use of Planner for serious, "big-ticket" projects. Please implement!
I think this would aid in the development of a Gantt chart view as well. Overall would given planner a much greater level of added flexibility and value if teams need to plan long term.
This would be much needed to bring MS Planner forward into more applicable project management tool; also to be able to add custom fields as you can do with Trello.
Please allow dependencies, its a no brainer for management of projects.
Anwar Mahmood commented
subtasks and dependencies would enable work breakdown structure (WBS) - (https://en.wikipedia.org/wiki/Work_breakdown_structure). This is a fundamental approach to complex project management.
frankly, it's strange that I have to explain and justify this!
Also, there are many suggestions including the word "dependency"; they are probably for the same thing, but because they are separate suggestions, they don't have a single suggestion with a high number of votes. Please remediate that too!