Parent/Child Projects

[#1]

I apologize if this is duplicate but I did not see it anywhere. We have a need to create parent projects that would live between the Program level and the current project level. While I understand that the work could be completed in one project using parent/child tasks we have many departments that would prefer to have their projects tracked separately. There would be many child projects which would roll up to many parent projects and into ONE program.

I saw some talk about this on the Global forum but that was it. Please help me vote up this feature request!

Thanks!!

Michael

[#2]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#3]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#4]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#5]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#6]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#7]

100% - this is a huge need for us. We have too many projects that split out in multiple directions. We have to split them into separate projects from the beginning. Would be good to see this and potentially, even have the tasks that are relevant to all the child projects still be associated to the parent.

This would also be good to show projects are related. We have clients we do a "needs assessment" for where we do all of that under one project...and that needs assessment might result in a few separate projects. We could track all the projects under one umbrella this way.

[#8]

Would like and use this but would also like it to be a) something that can be copied/moved; b) able to set as recurring or cyclical. We have several of these types that are quarterly or annual which would be fantastic to set and repeat.

[#9]

Not sure if this will help, but this would really help our Marketing Team.

Our Scenario:

Project A = Campaign with many supporting tasks; (Lead by Jane)

Project B = Dev Cycle for Deliverable (Lead by Bob)

Jane creates a project in WF to track and manage an upcoming marketing campaigns. (Project A) She creates a task in this project to have a webpage developed and assigns it to Bob, who leads the digital team.

Bob gets notified of the task assigned by Jane in Project A and he creates his own project to manage the development of the webpage (Project B). As development progresses on project B, the % completed changes to 50%.

For Jane to be aware of this progress, relative to her campaign (Project A), Bob needs to manually update the task in Project A to match his progress of Project B. Jane could always go to Bob's project, but this seem like added effort.

If Bob were able to RELATE his Project B to the task Jane created in Project A - and the system updated the Project A Task item to match that of the progress % Project B - well Jane could simply review her Project A and know eactly where Bob is in the development of the webpage. And to aid Jane in her efforts to manage a complex campaign, she clicks on the Task from Project A and is immediately directed over to Project B where she can review and contribute.

I have a dream... Workfront, let's make it a reality for everyone! Any updates?

[#10]

Not sure if this will help, but this would really help our Marketing Team.

Our Scenario:

Project A = Campaign with many supporting tasks; (Lead by Jane)

Project B = Dev Cycle for Deliverable (Lead by Bob)

Jane creates a project in WF to track and manage an upcoming marketing campaigns. (Project A) She creates a task in this project to have a webpage developed and assigns it to Bob, who leads the digital team.

Bob gets notified of the task assigned by Jane in Project A and he creates his own project to manage the development of the webpage (Project B). As development progresses on project B, the % completed changes to 50%.

For Jane to be aware of this progress, relative to her campaign (Project A), Bob needs to manually update the task in Project A to match his progress of Project B. Jane could always go to Bob's project, but this seem like added effort.

If Bob were able to RELATE his Project B to the task Jane created in Project A - and the system updated the Project A Task item to match that of the progress % Project B - well Jane could simply review her Project A and know eactly where Bob is in the development of the webpage. And to aid Jane in her efforts to manage a complex campaign, she clicks on the Task from Project A and is immediately directed over to Project B where she can review and contribute.

I have a dream... Workfront, let's make it a reality for everyone! Any updates?

[#11]

The Home Depot has this exact same scenario that we are trying to solve for. (credit to Chris Canada - I borrowed your scenario and tweaked it)

We would also like to be part of the team to talk through different scenarios with the product team if there are spots available!

Our Scenario:

Project A = Campaign with many supporting tasks; (Lead by Jane)

Project B = Studio task that support completion of project A (Lead by Bob)

Jane creates a project in WF to track and manage an upcoming marketing campaigns. (Project A) She creates a task in this project to have a webpage developed and assigns it to Bob, who leads the digital team.

Bob gets notified of the task assigned by Jane in Project A and he creates his own project to manage the studio tasks that complete the creative (Project B). As studio tasks progresses on project B, the % completed changes to 50%.

For Jane to be aware of this progress, relative to her campaign (Project A), Bob needs to manually update the task in Project A to match his progress of Project B. Jane could always go to Bob's project, but this seem like added effort.

If Bob were able to RELATE his Project B to the task Jane created in Project A - and the system updated the Project A Task item to match that of the progress % Project B - well Jane could simply review her Project A and know exactly where Bob is in the development of the webpage. And to aid Jane in her efforts to manage a complex campaign, she clicks on the Task from Project A and is immediately directed over to Project B where she can review and contribute.