This post has been closed as a duplicate. All votes have been moved to the original: PARENT/CHILD PROJECTS
Several workfront users have asked about linking projects in Workfront. For example, one project would be developing the theme for a series of other projects, and each of those other projects would be linked to the master project.
I've had several users in our company ask for this feature. We would like to have this capability as portions of our projects are run as mini projects. if we could roll-up the task from one project in another we could have a cleaner process in our projects.
This is an excellent idea - we often have projects that run over several iterations. Splitting them out would allow us to manage the projects more cleanly, not limit us on task numbers but also report on the project overall . Wf does get a little messy and slow once a project contains more than a few hundred tasks.
Along these same lines, I would like to have the ability to move existing projects into a Master project after they have been created or completed. Similar to a campaign but after the fact. How many of us, either forget or don't know to start with, the scope of a project that gets bigger than expected. Sometimes we start out with just a web banner request for a project then with in 2 weeks the ask is for landing pages, flyers, pop on's, posters and emails. As is sits now you cant combine individual jobs into one new "master" project and keep the custom forms. I do know that if you start out with a "master" project you can move issues into that master as tasks and keep the custom form, just not after an issue has been made into a project. Seems like an up-vote is needed.
Completely agree with Samantha. We've had Workfront for almost 3 years now, and now that we have a good workflow established, we'd like to go in and clean up our projects, similar to how Samantha mentioned combining individual jobs into a master project to keep the custom forms.
We are about to implement Workfront here and there are concerns about keeping all of the projects aligned with the initial request. I will be posting this in the community too in order to gain some traction.
If you have one request tied to many projects, why not convert the request issue to Master project and from there use cross project predecessors to parent tasks to tie projects together?
Sometimes our teams want to link past projects just as a reference without necessarily having them dependent on another object. The need is to have a historical reference of a prior deliverable.
We utilize portfolios, programs and naming conventions to help with the above however it seems that maybe a custom form field where the team member could input the prior project number at the project level may be helpful?
I agree with Nick, it would help in historical situations as well. Sometimes projects have cross use-cases and only being able to choose one Program/Portfolio really limits the way we can organize them for future reference.
