## The Problem Subtasks imported to Sunsama as their own tasks are not easily differentiated when they have the same name because they lose their parent task context (which is visible in the Asana sidebar view). This becomes problematic when you combine the following two scenarios: You have subtasks assigned to you in Asana where you are not the assignee of the associated parent task. You have multiple parent tasks created from an Asana task template that contain subtasks with the same name. ### Example You’re a content team that produces content for many customers. You use Asana’s task templates feature to create a task with the following structure: Article A Outline article Draft article Edit article Approve article Revise article Design article graphics Format article Publish article Simply importing the parent task into Sunsama is not feasible as many individuals may be responsible for the various subtasks that go into completing the Article (e.g. a content manager may own the parent task but a writer, editor, designer, customer, and developer may be responsible for individual subtasks related to their skillset). Things breakdown when you are working on multiple articles at once. You end up with many tasks in Sunsama named the same thing without the context of what parent task they belong to readily visible on the task without opening it up in the modal view first—which then causes you to lose context of how it relates to all other similar items. ## Proposed Solution It would be great if you could continue to see the parent task of a subtask when imported from Asana just like we can when viewing the task in the Asana integration sidebar. We can see the parent task when viewing the task in the Asana integration sidebar, but when we drag it into the Sunsama task board we lose visibility of this and only see the Project instead. If some users feel this would clutter the UX, I propose you add the option to allow users to toggle this additional context layer on or off to best suit their needs.
