Parent/Child Projects

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

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

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.

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.

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.

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.

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.

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.

This would also be incredibly useful for our org as some projects have many phases that extend for long periods of time or a project that branches out into many sub-projects. Currently there is no way to really organize.

Thank you for the idea and all the feedback. We agree this would be a great functionality to have and we are investigating the possibility of having it but we are not able to provide the timeline on when we will be able to build it, so I will mark this as Not Planned for now. Please continue up-voting and providing your use cases as we will revisit this later.