Preserve Tagging After Project/Task Duplication

Hello --

I would like to request a feature -- During our implementation, our consultant was initially under the impression that this was either a current feature or an old feature, but we tested it and couldn't get it to work as he described.

99% of our work is template-based. We have created several Project templates, and when it's time to start work, we duplicate the appropriate template. We are able to duplicate everything in the templates with one exception: tags into other folders.

What I would like to be able to do is tag a task in a template to a particular folder (Teams, for example). Then when I duplicate that template, in addition to duplicating the Project into my desired location, I want my tagged task to be tagged into Teams as well. It would remove the need for our project leads to tag these tasks manually each time they duplicate a template.

I understand it's a bit of a niche use case, but it'd be great for our project leads.

Thanks for considering!

38
23 comments
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

Hi Bradley, thank you for sharing this on the Community! This is a really good suggestion. In case it helps for some cases, I wanted to mention that Folder tags get duplicated if they are a part of the structure that is being duplicated. This might not work since it would eventually result in several copies of similarly named Folder tags, but I wanted to mention it just in case. :)

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi, We work in the same way so would be very interested if any changes are made to make this possible. We have to currently re-add the folder tags after every duplication and all of our Projects are template based.

 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This gets my vote! The use case is that our projects contain tasks for different products that we sell. We tag those tasks in separate product folders so that the product team(s) know when their products are being utilized and can track status, implementations and other data. 

Currently, when we duplicate a project template (that has the product tagging on tasks) we have to re-tag each task manually to the product after duplication. 

Thanks!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I should also add that I'm moving my enterprise in from another platform (Asana) where tagging is a core feature and used to manage categorization broadly. It's going to be a heavy lift to ask my user to remember to re-tag their tasks after every duplication. Cross-project tags are pretty much a required feature these days in order to manage searching and reporting when your org has hundreds of projects and thousands of tasks.

Thanks again!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi Noel, thanks for sharing your use case here, this really helps our teams understand the feedback and how it might be implemented. This is not on our developer's roadmap at the moment. I have passed on your suggestion to our Product team and if we have an update on this we'll be sure to post it here. 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hello, Same issue here with same need to have the folder tags move over when duplicating a template. Entering everything manually causing my carpal tunnels to flair up. J/K.. But would be an awesome feature to streamline project management..

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I also vote for this!  Here is my use case: I create a general task as template, and several subtasks under it. Each subtask has its own tag, since the subtasks are handled by different team. when new request come in, I just duplicate the template, and those subtasks need to be track by each team as well. Now only can manually re-tag one by one, it's very inconvenience.

If you can not keep all tags by default, at least provide an option to choose.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

Thanks for continuing to share your use cases, everyone! @Yannie that's a good one, I'm just wondering whether it could help to add assignees from different teams to each subtask, and use that as a way of ensuring that different teams are aware of a new request?

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

@Anastasia, add assignee only can resolve the task assignment, but we would like to have a folder to review all the tasks for each team. To have the folder(Tag), we can do some analysis. And also we have many team members in each team, they will pick up the tasks by themselves, decided by capacity/leave/many other reasons, we don't want to have single person to own the tasks at the beginning. 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

Yannie, thanks for clarifying, that's useful to know!

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Yes, please implement that. If a task is marked as "Calendar", its duplicate should show up in the calendar, too. And certainly without duplicating the entire calendar! Means the external folder tag matters.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I would also suggest this for tasks. I have certain tasks in the template that I have tagged in the folder that those tasks should always be in. So upon duplication, it would be great if the tags were to copy over as well.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I would like to see the perservation of folder assignments after duplication of a template structure as well. We also have template based tasks.  I duplicate  that structure  about 45-55 times. I would love that the structure anbd its sub folders would come with their other folder tags and I donlt have to manually add them. ( about 4 sub folders in each of the 45 repeats!!)

 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
When i duplicate my project-template I re-name it and add a pre-fix name for my tasks. The tasks is added in more folders but it doens work when I duplicate?? :(

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I cannot believe that this hasn't been prioritized. This is critical for us to manage tasks effectively with multiple cross-functional stakeholders. When will this be on the road map? 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

The option to keep tags from templates when duplicating and creating new projects would be a very helpful addition. The logic behind copying folder structure first to keep tags is not fully understandable for me. I hope for Q4. Thanks!

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I was hoping this was default functionality. Especially valuable for use with the Salesforce integration so that the choose template has some merit rather than just adding a collection of tasks.

Keeping tags and assignees would allow us to have set templates assigning the tasks to the relevant teams and departments. 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

@Mark Smedley -We've been using duplications for some time now with the following results...

- Assignments are kept

- Tags for folders within the project you are copying are kept

- Only tags to folders outside of the project structure are lost 😩😩😩😩😩😩😩😩

- Dependencies to tasks within the project are kept

- I use 'duplicate' from right-clicking the project name in the sidebar most often because it lets me select options like 'copy description, assignments, attachments', and reschedule it. Plus I can add a prefix (like a project #) to every task to differentiate it from other copies. This means I can keep a timeline and dependencies intact and unique to the project.

- Using Request forms to duplicate a folder doesn't give you any of the above options.

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Another yes vote.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi everyone, thanks for your continued support for this idea. I don't have an update to share at the moment, but I'll make sure to keep you informed when/if I have news. 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Lisa-- Can you confirm if duplicating from Blueprints will keep tagging? 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

@Noel Hey, you can only tag a Blueprint with another Blueprint; you can’t designate a Folder/Project from the main Folder tree as a parent Folder/Project of a Blueprint. I'm happy to help if you have any other questions about Blueprints. 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I would agree with the above comments. We use tagging to help with our marketing elements and reporting, and it is very inconvenient to have to re-tag everything after duplication.

0
Comment actions Permalink

Folllowing List for Post: Preserve Tagging After Project/Task Duplication
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post