Suggestion to add rule condition "task is added by template"

English Forum Product Feedback
,
1

Currently, you’re able to set the condition in Asana to check if a task was added to the project by form but it would be great if you could choose to set the condition “task is added by template” and even better to choose which template it was added from.

For more context, my company often uses task templates for recurring meeting dockets. I like to name the template the title of the meeting and then have a rule to change the task title to include a section for the date and for who ran the meeting (ex. Weekly Marketing Meeting - MM/DD/YY - Ashley). Weekly Marketing meeting is the template name. It would be nice if the first condition is checking if the task was created from the meeting template before renaming it.

2

Note: Not a solution but marked as such to elevate a key reply

Welcome, @Kimberly_King,

Until/if Asana implements this, have you considered using a custom field to enable this on your own?

You could create a single-select From Template custom field with values like Template A, Template B, etc. (one for each task template you have).

Edit each task template to set the default value for this field to its corresponding single select value.

In the rule you want to use just specify the trigger as:

  • When: Task added to this project
  • If: From Template is Template

Use “Otherwise If” for each of the additional templates.

In List view Options, toggle off the display of Task Template since it’s not relevant there.

Thanks,

Larry

1 Like
3

Hi Larry…

Thanks for suggesting this solution, I have tried it but I can’t seem to get it to work…

My debuging seems to indicate that if a Task is Added via a Task Template it doesn’t trigger rules based on the “Custom Field” values. The only “Check If” option that would work is “Task is no longer Blocked”

Is there topic or suggestoin to ensure that Tasks Added via a Task Template always trigger rules? So I can vote or do you think this is a bug?

Jason.

4

@Jason_Woods,

I just did a quick test and I think the rule did run:

  • When: Action is changed
  • Check if: Custom field is set to value
  • Do this: Create subtasks

Thanks,

Larry

1 Like
5

Thanks @lpb - Yep that worked… Much appreciated.

1 Like
6

This is actually a great workaround. I didn’t jump to it immediately because we already use so many custom fields, but I will definitely be considering this. Thank you!

1 Like
7

Terrific! Thanks for replying, @Kimberly_King.

1 Like