Does anyone know of a way to convert a task to a project, and use a template?
I have multiple templates available. They’re accessible if I create a project from scratch.
I cannot find a way to access the templates, when creating a project through the task conversion tool. Is this something that perhaps it’s being worked on? It would be very convenient to convert a task to a project by sourcing the ending project from a template already available. Right now, the conversion tool just converts a task to a project that is a vanilla project for me to edit.
No this feature does not exist. I would find it hard to wrap my head around it, how would you match a template project again an existing task structure?
Ahh, that’s the problem. An existing task structure might have subtasks, and collaborators, and items like that. But they’re selectable boxes at the point of conversion. I could unselect those boxes so that the task would just carry its task name and become the project name, and everything else would source from the project template. It was a thought for my design team, as they add tasks for future projects into a project called “Availability Calendar”. Once they’re actually ready to start tracking that particular future project, they would like to convert that single task in the “Availability Calendar” project into it’s own project, but it becomes a vanilla project at conversion (everything is empty except for what you choose to carry over). That’s why they would like they capacity to convert a task to a project, using a template instead. That would give them the defaults tasks, the due dates, the custom fields, etc, already pre-populated for them.
Is it possible to apply a custom template after creating a project, namely after converting a task to a project? My workflow requires selectively “upgrading” tasks to projects, but I’d like to leverage the benefits of custom templates as well. Does my question make sense? Thanks!
Hi @Eric_B and welcome to the Forum! I’m afraid it is not possible to convert a task in a project generated from a template, but sounds like sounds like something our team could consider in the future!
Hi Eric, yep that’s the same problem I have. Your question makes perfect sense, but most of the time asanas answers are too vague or don’t deal with the question at hand and respond something unrelated. I hope they add the capacity of project templates to more places. As is, the only way to currently use a template, is to select it at the moment you create a new project. It is not possible to use a template on an already existing project (even if that project currently has no tasks in it), nor is it possible to use a template when converting a task INTO a project. This last one is the one that would be most beneficial as we too convert tasks to projects once we are ready to expand it and keep track of more items within that “task” without having to use subtasks.
Thanks, Adrian. Glad I’m not alone with this issue. Hopefully Asana is able to add this functionality in the near future. Without it, the task conversion to project is a nice feature, but at least I am not able to make much use of it. Thanks again!
Would LOVE this! We are trying to use a Pipeline project for our sales team and once we close a deal, we wanted to convert that task into a project using one of our templates.
Just create a new project from a template and copy-paste the info you need into the project description – you could even multi-home the original task to the new project for reference.
For example, maybe your Availability Calendar project has a section called Converted to Projects where you move tasks that are already moving forward.
And maybe your project templates now look this this:
SECTION: Pre-Planning
• Original task from your Availability Calendar project
