[Status: Backburner ⌛️] Option for Folder tags transfer when duplicating task.

Bumping this, agreed.

An option to Copy Task with Tags would help a lot.

Duplicating a project with 100 tasks with tags is currently impossible.

Also agree. Would be extremely helpful (logical) if all tags/statuses built into template project should pass to the duplicated project. 

This used to work, but seems have stopped. It is also an issue with blueprints.

Blueprints are great that you can plan and assign without clogging up workloads, but we need the ability to tag other folders ready for duplication.

Has anyone found a fix for this?

@all, thanks for posting here. I've updated the status here.

The Product Team understand the need for this and agree it's a good idea. There are plans to begin investigating duplication scenarios next quarter and this will be added to that investigation. 

At this point, it would be great to hear some use-cases, and how you're working-around this right now. Why? Well often the team can find ways to achieve this in different ways and understanding what you're looking to do and what you're doing now helps them understand how to implement something like this in line with how you're currently using Wrike.

Thank you for posting and voting! 

Right now for the work around, we manually add the folder tags right after the duplication. Only way we have found that it has worked so far. 

We manually tag tasks after creating new projects from our WRIKE blueprints. One main use of task tags is to filter certain key tasks & milestones to track in WRIKE calendars. The ultimate result works really well for us, but it is an inefficient step to tag the relevant tasks on every new project since it would be so easy to duplicate from the blueprint if WRIKE supported it. 

We'd like to use this to distribute work to a team when we don't know who exactly will be responsible. We'd tag the team's incoming folder and let them ingest and process the work as normal.

There are a few ways we would use this but the primary use case is:

We have a folder template where we have all of the tasks needed to complete a project internally, and then we have a separate folder that pulls just the final tasks (a marketing email being sent, for example) that we link to a calendar that gets shared with an external team. That keeps the calendar simplified with the most important info for them. Currently, when we duplicate that template, I have to manually go in and re-tag each final task to that separate folder. If it could carry over the tag from the template version, it would do it all automatically and ensure we don't miss anything.  

This would be extremely useful for us too. Currently, like already stated, we manually tag the new items after duplication, but this is an extremely inefficient use of time - particularly when copying a project or folder with many sub-folders and tasks within it.

We would like to request this feature as well. We have projects that are broken down for view in multiple ways that rely on multiple tags. These projects are highly templatizeable, but duplicating our template strips the tags and makes re-tagging a burden.

Specifically speaking, we are a marketing department that has promotions running on different media throughout a season. We want to view each project with all its promotions to be worked on, but we also want administrative views that give visibility into what promos are running on what schedule on what media. For example, we folder views for all schedule emails, digital signage, web banners, social posting, posters, etc. These top-level views are important to make sure we don't have gaps or overloading in our promotional schedule.

Here is an example of what our Digital Signage calendar looks like. Each of those tasks has up to 15 sister tasks that are cross-tagged to other marketing vectors and show in their respective views.

Hi everyone! Thanks a lot for your support here 🙏

After conducting research, our Product team couldn't fit this suggestion in the short-term roadmap, so I've changed the status to a Backburner for now. I'll get back to you when there's an update for this! 

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

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Hi, I wanted to see if there was an update or a way around this? We are testing Wrike out and loved the tag feature as we have an intricate web of organizations and moving parts. I work with coordinating international week-long volunteer teams which essentially is a week-long event with many moving and repeating parts. Is there a way that I can easily duplicate this 6-month long planning process with dependencies and tags in multiple folders? 

Thanks! 

Hi Rachel Rogers, welcome to the Community! 🙂

No updates at the moment, but we'll keep checking with the team and keep you posted! 

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

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Can this be added. Having to manually add tags back into a duplicated template project is a waste of time. Especially on large projects.

Hey Support Admin, thank you for bumping this older thread and sharing your feedback! 

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

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Any word on this? I am also running into this issue when creating from a blueprint.  My example is - I have a project save to a folder called master schedule, with sub-projects within that are saved to their own respective folders.  The individuals are given access to the folders that are relevant to their part of the project.  When I save from a blueprint, it is all saved within the folder that I selected as the destination folder.  But - I would would want it to also dump the sub-projects (phases) into their correct folders.  Right now, I need to go through after I have created the project and assign the sub projects (phases) to the correct folders.

Maybe there is a better solution for this?

Our current structure for a project is Project, Sub-project (phase), tasks, subtasks when applicable.