As you work within Asana you might occasionally find that a project is no longer needed. Asana offers the capability to Archive a Project, but you might find in specific instances that the data within a project is no longer needed. As shown below, the Asana Guide highlights steps to take when deleting projects and things to consider when performing this action.
This is great information, but what about subtasks? What are the necessary steps to ensure that when deleting a project you aren’t left with an “orphan tasks”?
When deleting a project, tasks that meet one of these conditions will remain within Asana after deleting a project:
- Tasks that are assigned
- Tasks that are multihomed to another project
- Subtasks where the parent task remains (not deleted)
- Subtasks that are multi-homed to another project (those that are assigned will be deleted, if not multi-homed or having a parent task that remains)
Knowing this, what is the “best practice” to completely purge a project where none of the tasks or subtask are required any longer? - >>> un-assign at all levels with no multi-homing assignments! This can be achieved by performing an Advanced Search if you filter to the project in question AND add a subtask filter to show all tasks associated with the project, as seen below. Simply bulk-select any items that are no longer needed and remove the assignee and any other projects the task (or subtask) is mapped to.
While deleting projects might not be a “best practice” itself, we all may have situations where information might need to be purged (such as when you import to project via CSV but learn your import file has some errors that need to be addressed/imported against). To prevent uncovering orphan tasks over time, consider the steps listed above. Cheers!!!