I understand that Assigned Tasks within a Project that is canceled remain active and “orphaned” (they display as tasks with no Project.
Can someone provide a use case where this would be valuable? Maybe I’m missing something, but if I use a template (with pre-assigned tasks) to launch a project and then wish to cancel it, there is no reason I would want these tasks to remain active.
Tasks and projects are used by millions of people and many thousands of organizations. I don’t think it’s possible to rule out legitimate use cases. What about an overzealous cleanup effort?
Your example ignores the preponderance of projects that exist that are not created from templates.
Despite the above, I do feel that there are times when it makes sense when deleting a project also to delete assigned tasks (and to delete multi-homed tasks as well, another potential for orphaned tasks). But I think Asana has made the correct choice of the safer default (albeit with side effects) than the more drastic one.
Thanks,
Larry
I forgot to add:
Would you be ok with my merging your topic into this one in order to keep related info and feedback together:
Regardless, please consider adding your vote, if you’d like, by clicking that topic’s title to scroll to the top and vote by clicking the Vote button.
Thanks,
Larry