Fully delete all tasks in a folder even if they exist elsewhere
When deleting a folder, my desired behaviour is that all tasks within that folder are deleted even if they are also 'tagged' in another folder.
For example, we are mapping out templates for process tasks, and within each department folder there may be tasks relating to, for example, getting translations carried out.
We want to have all of these 'translation' tasks in a folder, such that if for this particular iteration of a project Translation is not required, the user can simply delete the translation folder and those tasks will be completely removed from the plan. (we will of course make sure that the dependency logic will be maintained even if these tasks are deleted)
What currently happens instead is that all the tasks remain in the individual department folders.
I can see the argument for letting them remain, but I don't see how that would 100% be desired. Is there any scope to add a setting, or even a pop up when you try to delete a folder that contains tasks that exist elsewhere, asking if you want to delete or leave those tasks?
Many thanks.
I would also like to have this "full delete" of a project or a task so that it does not remain in other folders.
Hi Fabrice Parisot, thank you for chiming in here and adding your support👍🏼
I would also like this full delete feature!
Thank you for supporting this suggestion Lize Loftie-Eaton, I'll now share your feedback with the respective team 👍
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
So if this "full delete feature" is not available, what are people doing to delete tasks that are 'tagged' in other locations?
Yes, we need this feature. When our Project Owner creates from Blueprint several tasks within the project are auto-cross-tagging into other Team's folder structures in their Team Space. If the Project Owner deletes the Project (used the wrong blueprint, created with wrong end date, etc) those "orphan" tasks still sit in the cross-tagged folders but they're not cross-tagged into a main project. As a System Admin team we are constantly cleaning these up and having to teach Space Admins to clean them up. We're tempted to reduce permissions so team members can Create but cannot Delete but that's not the best for the end user experience.
We need this feature very much as well - we are managing resourcing my tagging tasks with effort in other locations and it is really mucking up the workload charts when they get deleted in one location, but not another. Is there a workaround at least or is this feature coming?
We need this feature very much as well - we are managing resourcing my tagging tasks with effort in other locations and it is really mucking up the workload charts when they get deleted in one location, but not another. Is there a workaround at least or is this feature coming?
Hi Rhonwyn Williams, thank you for your comment. We'll consult with the Team and let you know in this thread if there are any changes.
May I please kindly ask you to confirm in which cases you see this behavior? For instance, if you tag a task with a different Space, folder or project and then delete it from one of the locations, is the task deleted from both parent items?
Looking forward to your reply 🙂
Hi Juan - I have automation rules in place that tag sub projects in other spaces. When I delete the main project these are not deleted as part of it. In some cases you may want these to stay, but I think there needs to be an option asked if you want all sub projects deleted when you delete the parent item.
Appreciate your detailed feedback Rhonwyn Williams, we'll share your use case with the responsible team at Wrike 👍
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
I also really need this! My use case is similar as above. Projects and tasks get automatically tagged to other folders and spaces. When i delete a project or task, i don't want to have to go looking in all the other places to ensure its been deleted elsewhere.
One work around i see is editing the location to before deleting to take it out of all other places, and than deleting from current folder or project.
This seems cumbersome, and hard to ensure the team will do.
Hello Kyle Martin, thank you for adding your feeback and for sharing your use case with us 👍 I've passed your comment on to our Product Team and we will keep you updated if there are any improvements 🙂
Is there an update on if a full delete feature will be added? Having tasks remain in different folders after a project is deleted is causing confusion for my team.
Hi Maegen Maher, thank you for your comment; I'm afraid that we don't have updates about this suggestion at the moment. Please, rest assured that we will keep you informed if there are any changes 👍