updating created projects after a template is edited

English Forum Tips and Tricks
1

Hello all,

If you update a template after a project is already made, is there an easier way to apply the edits to the preexisting projects? Other than manually adding them? We have many projects and are frequently updating our templates.

Thanks,

2 Likes
2

Hi @Melissa_Schank ,

What are you trying to edit - task names/descriptions or available fields?

If it’s the latter, you can try bundles. If it’s the former, I am not aware of a way to do this currently.

1 Like
3

Another option might be to split the templates in phases.

You’ll have more templates, so you’ll need more time setting up projects, but you’ll trade that for being quicker in phasing out the outdated templates.

Which is more important to you?

Also, for individual tasks bundles and task templates to spread tasks to add or replace existing tasks. I think you need people to add them manually though.

1 Like
4

@Melissa_Schank,

In addition to the good replies above…

Bundles is an Enterprise feature that you can read about; if it’s available to you, it will address exactly your request to update Sections, Custom Fields, Rules, and Task Templates (but not Tasks) in already-existing projects.

If you don’t have access to that, there are workarounds like using a project to specify in a single source the custom fields and rules that all your projects need, and then multi-homing (add to multiple projects) your projects tasks to include this “common” project; then you have only one place to make updates.

Thanks,

Larry

1 Like
5

Hi - I am experiencing a similar issue related to task/task templates not updating with the appropriate edits in my bundle. They will “save” in the bundle after I “apply” edits, but not be reflected on the project plan my bundle is attached to.

I am able to see edits and updates related to section names but not the tasks themselves.

6

@Liz_Cowley - welcome to the forum! Can you describe what you’re trying to do? Bundles won’t affect individual task names/descriptions, just field options, project section names, and rules.

7

Thanks for your help, Stephen.

I am trying to create a robust project plan that can be easily updated and replicated through a master project template. So, if a single task needs to be edited or updated to reflect an improved process, I could update in a singular place (ie bundle) and then see it updated across various projects (20+).

From your statement, are you saying bundles don’t include tasks/task templates which is why I can’t bulk update in my testing environment?

Thanks again.
Liz

8

@Liz_Cowley - task templates can be controlled by bundles, but this won’t affect existing tasks created from those templates (only those instantiated after the changes are published). Task templates basically just allow you to standardize the creating of new tasks in projects.

Similarly, project templates won’t push changes to tasks in already-created projects. Bundles can add fields to existing projects, but they won’t set the values on those fields for existing tasks.

AFAIK, there’s not an easy way to publish mass changes to existing tasks in existing projects. It’s generally best practice to do most of that design thinking up front if possible (obviously this can be difficult), especially for waterfall projects. Bundles are very useful for more agile projects that represent ongoing processes of work coming in/out (they are also useful for standardizing instantiation and maintenance of waterfall projects).

1 Like