We currently have multiple blueprints that have different duration and tasks based on the type of project we are working on.
About 80% of the tasks remain the same throughout the different blueprints.
The issue is if we want to update a task in the blueprint, we have to update that task on each blueprint every time.
Is there a best way to go about keeping a single blueprint that then feeds the other blueprints? The issue seems to be the dependencies being used across multiple projects. See below for a test example.
Let's say I have (3) Projects: Long, Medium, Short, and then Standard. Standard will be the same for all of the other projects.
Each project is broken up into phases. Phase 1 has different durations and phase 2 and 3 have the same length. I kept the Phase 1 tasks with their respective projects.
I then added Phase 2 and 3 from the Standard Project
This is fine for the Long Project, but in the Medium and Short Projects, there is a lot of lead time between Task 2 and Task 3 (where they are dependent).
When I go to launch a Project like this from a blueprint, I have to then go into the dependency and reenter it in order to "reset" the dependency. Not a big deal for just one task, but we have complex gantt charts that have multiple dependencies and would be difficult to ask the user to do this every time.
Is there a better way to go about sharing the tasks in blueprints?
Please sign in to leave a comment.