Make Key Resources part of project template

When you make a project from a template, it seems as though the whole Project Overview page copies over except the Key Resources.

I would like Key Resources to copy over when I make a project from a template that includes resources :slight_smile:

1 Like

Thanks for the feedback @Justine_D, this is something we heard from other customers too and that we will consider for future updates! I’ll update this thread as soon as I have some news on this topic!


This would be a very useful feature.

1 Like

I agree with this suggestion. Many of our users utilize key resources to attached templates of work that is transferable to other projects for use. This feature would be nice so that users are not having to re-link resources to each new project created.

1 Like

Dear Marie,

The idea of Justine_D will be very helpful for us.
Thank you to consider it.

So just wondering if this update has progressed at all. I spent ages pulling together Key Resources for a Template and now they don’t save across. Seems like a simple fix. What’s the status pleas?


This feature would be a game changer for our organization! Please do consider making this update.


Bumping up this feature request, this seems like great idea and I would use it right away.

1 Like

Backing up this feature request, this would be a huge time saver for our team.

1 Like


I agree, this would be extremely useful as my division have 4x project types which require different project templates, and different ‘key resources’.

1 Like

Bumping this thread! The logic on Project Templates’ Overview pages is super wonky!

How we’ll collaborate - this is the field used as the template description in the template chooser (1 line of text, no option to expand in chooser), but other information included in this field (owner of updates, frequency, etc.) seem like they wouldn’t need to be included in template chooser but definitely copied over to new projects

Project roles - should be able to choose whether to A) keep template roles or 2) delete template roles & set project creator as new Owner (currently original template creator is owner of new project iirc)

Key resources - this should 100% be carried over from template to new project, ASAP. To my mind, there is no logical reason why the meat of a project description, scope, background, etc. created from a template would be deleted from template to new project. Without this transferable, I’m tempted to just duplicate the project rather than make it a template (which causes me to lose the adaptive deadlines feature) :expressionless:

Milestones - these autosync, but question: if the project brief in the template had the milestones widget, would the whole project brief be deleted in the new project, or would just the widget remain?

Goals - you could make the case either way. I think, like with Project Roles, you should be able to choose whether goals transfer from template to new project.

I agree, this is a great feature request because it allows consistency and relevant / contextualized information for the templates!

I think my team would use this to keep our service agreement template in so that our conference planners have quick access to what we are agreeing to for the specific ops package we’re doing.

Alternatively (bandaid for now), I think it’d work to have a task(s) with the relevant file(s) attached in the template. This could be an actual task to “review this key resource” or a reference task. This works until more files come… but that is another conversation.