My personal approach would be: create a template with the Sales Funnel, then many blank lines, then the Iron Fences tasks… When the customer chooses 1a or 1b you delete the empty tasks and irrelevant tasks. If needed, Templana can host such a project in a private repository for you, if you need to share it outside your colleagues.
@Wally_Montpetit another option for you is to create a Sales Funnel Template Project that includes a template task within it. Simply create a template task for teammates to copy when the “customer gives go ahead and wants to order an Iron Fence.” The template task can live in the project and simply be copied and then dragged and dropped to the appropriate place in your list. None of your work would ever need to be deleted.
Here’s a rough outline of how that Sales Funnel template project and corresponding template task could look in Asana:
As you can see, I put my template tasks at the top of the project, so I can copy them easily. I can copy the “Iron Fence Order” template task, then put the copy into my “Post-Sale” section. You’ll also notice that project name includes “TEMPLATE” in the title. You can of course copy the project and change the project name for each client.
Hi Ulrik. We’re unable to say specifically if this will happen in the next 30 days, but it is scheduled to happen soon. It sounds like you’re at an important time in the decision making process. I’ll be happy to connect you with one of my colleagues who can provide more information.
Hi @Ulrik_Binzer. For what it’s worth, when I was first evaluating Asana I thought the lack of templates was a dealbreaker. I eventually realized that creating my own templates as dummy projects/tasks/subtasks was just as good, and we do it every single day. Once the custom template feature is available, I’m not even sure I’d bother changing to it at this point. Given that the feature is coming soon, though, I’d strongly encourage you to not to make a decision you’ll have to live with for a long time on the basis of a temporary issue when copying projects is a viable alternative for the interim.
I am absolutely for being able to save custom project templates in Asana as it would make my life of building out easy to use templates for my teammates so much easier. Although, I would love if we could go one step further and make template tasks, along with the ability to save those custome template tasks.
My team works with many external partners across many cities and we’ve found it easiest to create a project for that city’s partnerships, with each partner being it’s own task. And since what we do is program implementation at these partners, we then have a separate project with various program implementation task flows that we now have to manually copy and drag over to the partnerships project, and then drag into the subtask view of each partner task to show what programs that partner is implementing, as well as what tasks need to be completed for each program implementation at each partner.
It’s a convoluted workaround that would be made so much easier if someone could simply make the partner a parent task, and then whey they go to type in a sub-task, there is a window that pops up that asks if they would like to select a pre-made task template that would allow them to select the program, which would then auto-populate all of the tasks associated with that program.
is it possible to use the custom templates inside of subtasks within a certain project?
Instead of creating multiple tasks with a common purpose we would like to limit to fewer parent tasks and have the multiple subtasks inside of the parent task. This will streamline our initial view and help to categorize our tasks per say the vendor’s name and then all tasks in the project related to the vendor are subtasks. I can apply custom fields to the project but they do not show in the subtasks unless i assign them individually in the subtasks. - Thank you in advance!
When it comes to Custom Templates, how do you make them accessible to your team without giving everyone access to the base template? We removed most of our team from our “Templates Library” in order to streamline the process for creating and updating, and now none of them can use our templates when they create a new project.
This sounds like a permissions issue. I’d actually suggest that you add your team back to the templates library for them to access the template and then create Asana conventions that encourage your team to not edit the base template. I think you’ll find these Guide articles on project permissions and conventions to be helpful: