Push project template updates to existing projects

In ClickUp you can have templates at the:

  • Workspace level
  • Project Level
  • List Level
  • Task Level
  • Subtask Level
  • Checklist Level

Once you update a template, if you decide you want to update an existing list item (from the above list), you can do so from that item’s options menu—you can then merge current progress with the new updated template.

image

And yes, I’m hard on Asana because I know they’re better. They have more resources, a team full of stellar developers, and they’re public. If an upstart like ClickUp can pull this off in a matter of weeks—I know Asana’s capable of it too.

That being said, I do think that just because they can implement a feature, doesn’t always mean they should or will.

The product team at ClickUp is very different from the Product team at Asana. ClickUp prides itself on having a public roadmap (Canny board), listening to customers desires, and acting/iterating on them swiftly…and sometimes that’s a detriment as it inevitably introduces bugs and other unforeseen consequences.

1 Like

HI all, thanks for taking the time to provide this feedback!

As mentioned by @Phil_Seeman, there is an existing thread on this topic so I’ve gone ahead and merged this post with that one to consolidate feedback! :slight_smile:

I’ll loop back in on this post should there be any updates to this feature :slight_smile:

:rotating_light: Don’t forget to add your vote by clicking the “Vote” button at the top of the page if you would like to see this feature added to Asana!

If you merge, does ClickUp overwrite all values in the current task with those from the template (even if you’ve modified those values in the current task since you made it from the template)? If so, does it show you both values so you can see what you’re about to potentially overwrite?

You can choose what gets brought in from the new template. If you want to update things like the description, dependencies, custom fields, tags, and time estimates, etc., then you can select those and it will update those alone.

It’s ultimately up to you what you want to import in—suppose you’ve already been working on a checklist, you can either import the new checklist or just keep the old one as is and use the new template for future items. Note on checklists, you can have multiple checklists inside of each task (but you’re limited to one “set” of subtasks).

In Asana, it would be nice to update things like dependencies, tags, custom fields, and such. I’d reserve updating “templates” from updated subtasks and descriptions and other “in progress” items within a task since that would cause confusion—this could be alleviated by having a global template library though.

Asana could implement that the way ClickUp has as well — when saving a template in ClickUp you can choose who has access to that template. Also, when saving a template in ClickUp, you’re given the option of what items you want to be updated in the templated version in the template library.

Hope that makes sense @Phil_Seeman!

3 Likes

There is an order of magnitude between ClickUp size and Asana size. You don’t code a feature the same way for millions of users :sweat_smile: so basically i’d say the bigger you get the slower you usually get :confused:

Thanks for the explanation!

1 Like

From a product feedback standpoint—sure. From a development standpoint, that’s why SOLID principles are critical.

1 Like

Our company has a project template we use for all our clients, which in turn has template tasks within that project. Every time we need to make an update to the template task, we have to then go into every single project manually to update the template tasks there as well.

It would be nice to have the template tasks be just like the custom fields - where if you change the template task in one place it changes everywhere.

Thanks for sharing your feedback with us, @Lauren_Madsen! We already have a thread on this topic so I’ve gone ahead and merged your post with When modifying template tasks, propagate changes out to existing descendant tasks to consilidate votes.

Downvote! Although I see where you are going with the efficiency gains.

Not necessarily the complexity of implementation from a functional standpoint, although there is, but rather from a practical one, this is a nightmare.

Those 20 projects are in flight, but in different stages of flight. Pushing an update for a section let’s call Week 2 when projects are already in Week 4 and those upstream tasks are already completed would create HAVOC!

Then there are the people not understanding the downstream implications and are click happy with any popup and again, HAVOC.

Oh, I was just making changes to the template for you to review. I thought the Apply to All projects was to apply to all new projects

Yes, that will happen.

I think a better implementation would to allow the project owner (and only the project owner) to PULL any changes from a template into their project with a screen showing you a before / after of what the changes will do. Do this in the project details section. (Refresh from Template with checkbox options of what you want to pull)

As Bastien mentioned, the current state of Asana would probably not even allow for a pull request.

1 Like

I’ve tried to work with custom project templates but if I then make a change to the template, it isn’t applied to those projects that use it.

If I have 75 projects, how can I make a customisation (like adding a new column) and apply this to all 75 projects?

Hi @zigojacko, while this feature isn’t available at this time, hopefully it’s something our Product team can implement in the future

We do have an existing thread for this feature request in the #productfeedback category so I’ve gone ahead and merged your post with the existing one to consolidate feedback.

I’ll keep you posted and let you know if I have any updates :slight_smile:

Hello Team Asana,

I hoped to check if it were to possible that when one adds new custom fields or rules, they can be automatically and easily added to existing projects and templates.

Our use-case for Asana is as follows:
The Asana Teams are set as products and services that our company offers and within each team, clients are created as projects. So if a client has several of our products and/or services they will appear in the all the relevant teams.

What that means is our projects (500+) remain “live” as long is the client is active. There is no start and end date for projects.

All our projects/clients use the same template with the board view as default. The template uses the following sections: To-do , In-progress, Customer-Follow-up and Completed. This is for all our projects/clients. So any custom field or rule is the same across the 500+ projects we now have.

** We started using Asana a month ago.

The challenge we have is, we developed new rules and custom rules and fields after the initial on-boarding process and we want these new rules and fields populated across all our 500+ projects as they use the same template. This is currently not possible. At least as far as I can tell. One is only able to update rules and custom fields per project which obviously will not scale.

Is there a way to do this or its a feature that will need to be added?

Thank you.

Hi @Frank_Dzaramba, thanks for providing this feedback :slight_smile:

We do have an existing thread for this feature request in the #productfeedback category so I’ve gone ahead and merged your post with the existing one to consolidate feedback.

I’ll keep you posted and let you know if I have any updates :slight_smile: