Applying templates to existing files
It would be really handy if we could apply a template after a task file is created. We often have people create task files before decisions are made about next steps. If we then decide to move forward, we have to delete that file and create a new one using a template. It would be much easier if we could just apply the template, thereby adding the subtasks, to the existing task file.
Also, it would be great if, when creating a task from a template, the file name carried over to the subtasks. This happens with project templates, but not task templates.
Yes to all, please!!! We have stories (tasks) submitted daily and assign the templates later after an editorial discussion. The cutting-and-pasting of new subtask names wastes time.
Hi Greg and Jennifer! Thanks for posting this request on the Community, we're really interested in hearing how you manage recurring work and templates now, so this suggestion is definitely helpful.
It's explained pretty well above. Staff adds a story idea (task), which are then decided upon for next steps by editors at a weekly meeting, then we have to go back and add the appropriate subtasks (up to five per task - these are the same five for every task). We add the file name (prefix) so the subtasks don't get lost since they have the same names ("edit story"). We don't want these tasks to be projects where the files names are able to be copied over to the template. I realize that if you applied a template to an existing project there would need to be a way that it wouldn't wipe out any previous subtasks or descriptions. It's a challenge to explain to staff why they can't add a template to an existing task. They think it should be easier. Thanks!
Hi Jennifier, couldn't you just have a template that just contains tasks that you want to become the subtasks of your main story task? By doing that you can duplicate your template (and add the prefix that matches your main story task) to get your "subtasks" and then just drag and drop them into your story task's subtask icon and voila you are done. You now have your original main task with all the prefixed templated subtasks with descriptions attached. This method also won't interfere with any existing data or subtasks that were already attached to the main story task. Hope that helps as what you are requesting would be tricky to do and could lead to data loss and lots of tricky data merges through user error.
Regards
John that could possibly work. We are trying to avoid leaving the task and going to another folder to find the subtasks. We will test it out. Thanks for the idea.
Has this been addressed or solved since this thread from 2017? We are in the deployment process and are working through our request & planning process. Duplicating and renaming the templates is an extra step that becomes more complicated if the original request also includes all of the information we require in custom fields. Looking for ways to streamline our process. Would love some guidance or best practices for workarounds. Thanks!
Hi everyone, just a quick update - there are currently plans to implement adding tasks from Blueprints into existing projects/folders soon. This way, you could put together a template in Blueprints and add it to any existing project/folder you'd like. As soon as I have another update for you, I'll let you know.
Ok so it is has been 18 mos....@hugh what do you consider soon?
Hello Amy Lichtenwalter, thank you for posting and I hope you don't mind me jumping in for Hugh.
Could you please share your use case here, I can try to help to find a possible workaround or a solution for you? Thanks!
Cansu Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online
Cansu Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online
Yes with each round of revisions we do we post this in every single task. It would be great as the tasks that are created via Zapier come into the system as a task could quickly apply the below text vs. having to keep a word doc open and copy and paste in. We will do 250-300 rounds of edits each day. We are a high volume company and during our busy season work around 800 creative projects a the same time. The obvious requests by users which make total sense seem to be dismissed. I have read numerous requests from the last two years where the Wrike teams says "in production" but 18 mos later no updates have taken place.
STARTING FILES (DROPBOX LINK)
CLIENT EDITS:
PASTE YOUR NEW VERSION PAGEPROOF OR WORKFRONT LINK BELOW FOR THE PROOFER
PASTE YOUR NEW VERSON DROPBOX LINK BELOW FOR THE NEXT DESIGNER
Hi Amy Lichtenwalter, thanks for getting back to me. May I ask if you've considered using Request Forms for this setup? You can create a request form to receive all tickets that would launch a project or a task from your template. It could solve the issue of having to recreate tasks or projects. We have a blog article on How to Use Wrike as a Ticketing System if you'd like to learn more about it.
Please let me know if you have any questions 🙋🏻♀️
Cansu Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online
Cansu Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online