# Leveraging project templates - a deep dive

**URL:** <https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474>\
**Category:** Forum Leader tips\
**Tags:** forum-leader-tip\
**Created:** [17 April 2024 08:00 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474 "2024-04-17T08:00:40Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [7 October 2024 14:57 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/22 "2024-10-07T14:57:03Z")

</div>

You’re welcome. 🙂

> [@Bridgett\_Fogg](#):
>
> > The biggest problem with this approach and really all “conversion” of tasks to projects is that you are not able to utilize the Project Roles and Auto Assignees feature of project creation. It skips that step entirely.
> 
> Unfortunately we don’t find Project roles particularly useful in its present state. Most of the time when a project is submitted we don’t know who will be doing each function. It is weighed up between team members and workload after its added against other projects and then assigned out after taking in those considerations. To be honest it would be good to have those project roles be able to be filled out and autoassigned to the right people - post project creation - but as I understand it, that’s not possible right now

Adding your vote and voice in this topic might help get this on Asana’s radar:

> [@Fill project roles after project creation](https://forum.asana.com/t/fill-project-roles-after-project-creation/359613):
>
> It’s great to see Asana has added the ability to set up Project Roles in the template. However, it appears these roles have to be filled in when the project is created from the outset. It would be great if you could leave the role blank and fill it in later (maybe from the Overview page) as some roles aren’t known until later on in the project.

---

<div class="post-metadata">

**Author:** ![Anabella\_Sammarone](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/anabella_sammarone/32/261816_2.png) [@Anabella\_Sammarone](https://forum.asana.com/u/Anabella_Sammarone)\
**Post date:** [7 October 2024 21:34 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/23 "2024-10-07T21:34:08Z")

</div>

Hello Team,  
Can w branch out to different Templates depending on specific fields on a form?  
Is there a way?

---

<div class="post-metadata">

**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\
**Post date:** [8 October 2024 05:46 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/24 "2024-10-08T05:46:39Z")

</div>

Hi @Anabella_Sammarone , yes, you can create a custom rule which based on certain conditions of a single-select field (within your form’s question), then the action would be to convert task to project based on Template A.

Then if another condition is met (i.e. a different option from your single-select field), then a different action would create a project based on twmplate B, and so on.

Does that help?

PS: note that the ‘convert to project’ rule action does not currently support the option to let you leverage project roles or project start/end dates to autopopulate your projects created by such a rule action.

---

<div class="post-metadata">

**Author:** ![Anabella\_Sammarone](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/anabella_sammarone/32/261816_2.png) [@Anabella\_Sammarone](https://forum.asana.com/u/Anabella_Sammarone)\
**Post date:** [8 October 2024 14:46 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/25 "2024-10-08T14:46:17Z")

</div>

Great, thank you. Do you have an example that I can follow or a step-by step guide or tutorial? Thanks.

---

<div class="post-metadata">

**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\
**Post date:** [8 October 2024 14:54 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/26 "2024-10-08T14:54:33Z")

</div>

@Anabella_Sammarone

1. Create a single select custom field in the project
2. Add the field to your form and set the question title
3. Create a rule that triggers on new tasks being created
4. Create branches in that rule (otherwise if) that check: whether the task comes from your form AND the custom field is set to a specific value
5. Create actions at the end of each branch to convert the task to a project, here you can select the template to use

---

<div class="post-metadata">

**Author:** ![Anabella\_Sammarone](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/anabella_sammarone/32/261816_2.png) [@Anabella\_Sammarone](https://forum.asana.com/u/Anabella_Sammarone)\
**Post date:** [8 October 2024 20:02 UTC](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474/27 "2024-10-08T20:02:23Z")

</div>

Thank you, all will try it out.

[Previous page](https://forum.asana.com/t/leveraging-project-templates-a-deep-dive/771474.md?page=1)
