Workfront Research Survey: Parent/Child Projects

We're getting lots of responses. Keep them coming, please! 🙂

I really hope this becomes a feature and is implemented soon because as a program manager at an engineering company, we often have to create secondary projects per requests for PCNs (project change notice). Since there is no way to connect the two projects, we have to comment in the second project that it's part of a bigger project, which you can see leaves room for error and confusion.

Thanks Elissa,

We have a Parent Project solution that allows automatic unique sequential numbering of projects in a hierarchical manner, in that a new Project can be “deemed” a child of an existing project. The resulting pattern of Project Numbers looks like this (and can be tailored to suit):

Project 12753

Project 12753-001

Project 12753-002

Project 12753-002-001

Project 12753-002-002

Project 12753-003

etc.

By storing the relationship in this fashion, users can then create native Workfront reports to sort and aggregate these Parent Child Projects as required.

For a slightly different usecase, we also have a Multi-Copy Project solution, whereby a user can navigate to an initial Parent Project (eg with the right structure, custom data, docs, etc), enter the number of copies they’d like, then click the Copy button to generate them, each with a unique sequential suffix (eg -001, -002, etc) similar to the above.

If you are interested in either of these particular approaches, I invite you to email me at doug.denhoed@atappstore.com

Regards,

Doug