We would like to use Asana rules when creating tasks. Our goal is that whenever a task is created (via Asana itself or Missive (our inbox management tool, Asana is integrated), it is automatically:
Assigned to a specific person
Set to Medium priority
Set to Not Started for task progress
Given a due date of today
I tried adding a rule in our “Master Project,” but that requires all tasks to be added to that project for the rule to work. Since not all tasks belong to that project, the rule does not apply to them.
We would like this automation to work across all projects, not just one. Is there a way to create a single rule that applies to all projects, or do we need to create the rule individually for each project? Thanks!
As of right now, there isn’t a way to create “global rules.” You were on the right track by adding the rule to your Master Project. It’s much less work to add a rule to all your projects that multihomes tasks into that project, rather than creating separate rules in every project to apply those preferences.
Unfortunately it may become more complex if this is also needed for subtasks and/or recurring tasks.
Subtasks aren’t added to projects by default, so they won’t trigger rules that rely on “task is added to project.” Also, recurring tasks aren’t treated as new tasks, so they also won’t trigger rules based on that condition either.
However, the rule only automates for the first condition, which checks if the task priority is empty. I want this rule to evaluate all the conditions we added. Here is the result:
Funny, I’m having a similar conversation in another thread. Jeremy’s solution to set a field seems like a decent workaround, but it seems that it really only works for automatically created subtasks via rule, otherwise I manually have to set the custom field on every subtask which then just creates more manual work (since most of our subtasks are manually created). Seems like this should be a feature improvement.
Thanks - bundles doesn’t really seem to fit the bill here and we do use multi-homing, but this doesn’t really seem to solve the issue of wanting to set a different status than the first one in the list for new subtasks created on-the-fly (without manually adding a field to each one, which is an equal amount of manual work. Is there any solution for that, or could this be logged as a feature request to enhance?
Maybe custom task types can provide a solution for that, as they default to the first status upon creation. @Richard_Sather has written extensively about those.
Bundles seems a little overkill - I just want me and my team to easily create subtasks that default to a particular subtask. Regarding custom task types - that’s the principal issue - I made a post about it here about the same time Ciara started her post:
