💡 Why and when use task templates

A task template always shows the fields any task from the project would show. Removing a field from the task template means removing the field from the entire project.

Also fields like “Dependencies” and “Description” are native fields on each tasks, you can’t remove them.

Does that help clarify things?

It does…but it means that I can’t create custom templates for different task types. I am trying to create a very easy user experience where they only see relevant fields for the task type that they are assigned. If someone has a standard deliverable task, then more data fields are relevant. However, if someone has to solve a blocker task, then there are only about 4 fields that are relevant. Does this make sense? I want to only display what is relevant. Is it possible to front-end with a slimmed down form for these users?

The only way to get on-demand fields in a task template is to have the task template associated with a project that has only those fields. So basically you would have to create various projects, and people would have to go there to use templates, and then move tasks within the desired project…

Hello Larry,

It seems that you shared a good idea for this issue, but my bad that I don’t fully understand the steps to take, it will be very generous of you if you can explain more in detail for nonexpert people like me.

Thanks in advance.

Hi @ShayaG,

First, is your Asana plan either Asana Business or Asana Enterprise? If so, then you can use this workaround suggestion. If you’re on the free Asana Basic plan, or on the Asana Premium plan, you won’t be able to.

I tried to make the steps clear, but it’s hard without demonstrating and interactively discussing and screensharing. We can do those things with a one-hour JumpStart as described on my website: