Retroactively apply Templates everywhere it was used after editing the master template
future
George
From Support: It would be nice if edits to our Views applied to previous versions. This would prevent us from needing to update hundreds of Templates manually in a larger organization.
Log In
Lily Chan
Thank you so much for sharing your feedback and highlighting the importance of this feature! We absolutely recognize how valuable this request is to our users and the impact it could have.
Right now, our team is laser focused on improving the quality and reliability of template application, as well as supporting subfolders - that infamous feature request 😊. These are our top priorities at the moment to ensure a smoother experience for everyone.
Once we’ve made significant progress in these areas, we’ll return to scoping out this feature request. We appreciate your patience and understanding, and we’re committed to keeping you updated as things evolve. Your input truly helps us shape our roadmap—thank you for being part of our community!
Lily Chan
Merged in a post:
Update "Update Template" Functionality
Eliza Quaglino
When creating templates, we often go through and update large amounts of the tasks that our templates are based on all at once. We then have to go through and update the templates attached. Instead of having to open the task, click "update template," search for the template attached to the task that we are already in, and then go through the process that way, the Update Template button should be updated to make it so that any changes made to the task AFTER the last time it was saved are applied to the template automatically; no need to search for the right template, check settings or anything like that. This makes the process of updating templates much more efficient.
Lily Chan
Merged in a post:
Feature Suggestion: Bulk Update & Tracking for View Templates
D
Dice
Current Challenge:
When we create a view template with specific custom fields and filters, we often apply it to multiple list views across our workspace. However, if we later update the template (for example, by changing custom fields or filters), there is no way to automatically update all the views where this template was previously applied. We have to manually re-apply the updated template to each view, which is time-consuming and error-prone.
Proposed Solution:
When a view template is applied to a view, ClickUp should keep a log of all locations (lists/views) where the template has been used.
After updating a template, users should be able to see a list of all views where the template is applied.
Users should have the option to select specific views or select all, and then apply the updated template to those views in bulk.
This would ensure consistency and save significant manual effort whenever templates are updated.
Benefits:
Saves time and reduces manual work.
Ensures all views using a template stay consistent after updates.
Provides better visibility and management of template usage across the workspace.
Lily Chan
Thank you for taking the time to share your feedback Dice! I'll merge this into an existing feature request we have for this functionality.
Lily Chan
future
Lily Chan
Merged in a post:
Templates: Inherit template changes for existing tasks/lists/docs etc.
James Guitard
Currently, when I update a list template (for example) any existing lists that have that template applied will NOT be updated to match the changes made to the template. They use only the structure of views/fields/etc. at the time they were created.
I want the option to update 1 template, and have those changes apply to all objects that use that template (for all template types).
Lily Chan
Merged in a post:
Apply template updates to existing instances
M
Modern Entities
When you update a template in any part of the hierarchy, have the option to update all existing instances that use that template.
Any concerns about data safety could be handled by having any fields that are removed simply be hidden from the list view, but still be accessible when clicking into the item. Therefore you could choose to reintroduce the hidden field and still have all the data there, because the data still exists.
Lily Chan
Thank you so much for sharing your feedback and highlighting the importance of this feature! We absolutely recognize how valuable this request is to our users and the impact it could have.
Right now, our team is laser focused on improving the quality and reliability of template application, as well as supporting subfolders - that infamous feature request 😊. These are our top priorities at the moment to ensure a smoother experience for everyone.
Once we’ve made significant progress in these areas, we’ll return to scoping out this feature request. We appreciate your patience and understanding, and we’re committed to keeping you updated as things evolve. Your input truly helps us shape our roadmap—thank you for being part of our community!
Michael
That's better than the Safari plugin news I guess Lily Chan!
Justin Price
We definitely need this for our business. This feature would obviously need the ability to create linked and unlinked copies from templates so we can control which copies are impacted by a template change.
Lily Chan
Merged in a post:
Recursive Application of Template
Josh Rivera
It would be great to if after updating an existing template, those changes can be applied to all the spaces that had previously used that template by only applying the items that have changed.
Lily Chan
Merged in a post:
Change template for all locations where it is used
Roberts Dzenis
When You update an template, all locations, for example folder, you've created from this template before doesn't updates, so You need to go trough every location and make updates manualy.
It would be good to have option.
After template update: "Do You want to make this changes to all locations this template is used?" Y/N?
Load More
→