Content
share work package with subprojects
Added by John Zaki about 6 years ago
Hello,
I'm new to OP. I work as a manager for an elearning center of a university. Part of the job is to create mooc based courses for the university. Each course passes by certain stages (exactly same stages for each project). So, if I'm to make a diploma of 6 courses, then all the six courses would have same tasks to be done.
What I fancy doing is creating one main project say called Diploma and under that project I want to put all the tasks which are repeated per course. Then they get populated to all the subprojects (project per course). Also, I'm using "versions" and "project backlog" which contains all the tasks to be done repeatedly in the subprojects. I shared it with the "project tree" but the versions go to subprojects "empty" without the tasks created in the main project which means I've to redo them.
I've found a solution which doesn't look optimal which is copying the main project with its versions and tasks, and then the new project is used as a subproject from the main one. Not sure if this is the best solution.
Am I doing it right ? and is there a better solution?
Replies (1)
Copying the main project is what I would recommend for this. The "main project" serves as a "template," without a specific schedule. Making a copy of the main project gives you an "instance," where you can set the dates, tweak the descriptions, add unique subtasks, etc.
In my org, I'm not using "Versions" and "Product Backlog", so I don't fully understand your description
Certainly having to redo things doesn't sound optimal. If you can describe the behavior more specifically, and the behavior that would make the most sense, it might help someone who knows more about these features to shed light on this.
edit -- just wanted to mention: I've encouraged my users to keep the "template" project to a narrower audience than the copied "instances", to cut down on bike-shedding over the template.