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?