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]

We'd really love to see this move from "Not Planned" back into an active / considered status. We've run into several situations where this presents a dead end and we need to create a workaround. There should be an option for parent / child projects to operate much like parent / child tasks. While rolling into a "program" is the common response, that doesn't solve the reporting issue as you can't report on programs together with projects. So we need to create manual fields to try and link projects or create dummy "summary" projects to house the rolled up data, financial or otherwise.

[#3]

Yes, please revive this! I just posted a similar idea yesterday. Our organization is in great need to being able to link projects that need to track together.

[#4]

Use case:

if you have a direct mail piece that has several pieces such as a letter, envelope, buck slip, return envelope.

We would like a way to group those as a way to keep timelines on the same track by linking them to one another.

This would allow traffic and project managers to make sure adjustments happen to all pieces, and so other team members are aware of what all is included in a campaign.

[#5]

This would be incredible for our marketing campaigns! That way each deliverable/team can have their own workflows without having to work in a very busy single project or jerry-rigging the projects together.

[#6]

This would be great. The functionality of the W/F Program object is too weak for our purposes, so we have to create a Program Planning and Control Project. We would love to classify Projects within the Program as child projects or the program project. EIther that or beef up the functionality of the Program by adding some of the Project functionality.

[#7]

This would be great. The team wants to receive one request in the queue with a set of custom fields and documents that apply at the campaign level but we need to resolve this request in to multiple projects to complete each deliverable. Each of the sub project resolving objects should have visibility to the master project custom fields and documents. The main request shouldn't be resolved until all sub projects are resolved. Any workaround we've tried so far is requires duplication of data, significant overhead to set up the connections/views or makes it difficult for the team to navigate a complex single project schedule.

[#8]

@Anna Astaryan - can we get an update on this? It is very clear this a huge need for many organizations!

[#9]

Campaign relationship like this would be huge for our creative services projects... bring this back to life!

[#10]

Just jumping in on the thread to say that this is a must! We have so many projects within our campaigns (programs) that should be talking to eachother but can't. Also, the ability to save projects as templates, since many of our campaigns are duplicates and contain all the same projects within. Hope this is functionality that can be added.. as our team is currently having to use different tools to get this done!

[#11]

Said differently, I envision having a series of ideas that define a 5-year strategic road map for each program from which tactical projects could be executed as timing and resources become available.