Create Rule to allow assignment of tasks based on project "role"

Bumping this so Asana knows this would be the single best update they could make! :chart_increasing:

I read EVERY Asana email hoping to see “Role Bases Rules” on here.

Recently I’ve just seen a bunch of AI stuff that we have access to but haven’t found value in, just waiting for this one :crossed_fingers:t3:

2 Likes

Hi everyone,

I’d like to suggest an enhancement for Asana rules: the ability to use project roles (e.g., Approver, Collaborator) as part of rule logic.

For instance, a rule like:
When a task is moved to “In Review”, assign it to the project’s Approver.

This would help standardize workflows across multiple projects by assigning tasks based on roles, rather than specific individuals.

Curious to hear if others would find this useful too, or if it’s something already being considered!

3 Likes

Welcome to the forum, @Bruna_Borges! I’ve moved your post to the existing thread on this topic. Make sure you use the Vote button near the title to lend your support.

1 Like

When creating a project from a template using a rule, the project roles defined in the template are not included in the new project. Including them would allow pre-defined tasks by role to be assigned immediately on project creation.

1 Like

Hi @Anton_kossmann,

FYI I merged your post with an existing topic for this request. You can add your vote for it at the top of the thread!

@Anton_kossmann , I think you are requesting this instead:

I didn’t think so, @Richard_Sather, because he said

???

What do you think, @Anton_kossmann?

@Phil_Seeman , I’ve added in (…) a clarification to that thread’s title, because that thread does cover conversion via a rule, too.

So I have a workflow to review project requests (raised through a form), and when the request is approved, the final action is to generate a project into a portfolio from a pre-defined template, powered by a rule. Currently the roles defined in the linked template are not included in the project when it is created, meaning actions are created with deadlines, that are not assigned to anyone.

Does this help?

Hi all! It’s been a few months since this forum was updated. I found a “Semi” work around with AI Studio that will SOMETIMES let me assign a rule using AI to assign a task based on project roles (through a rule). Unfortunately, not all rules are letting AI work. I get an error message ): I’d love for rules to allow for assign based on project roles! we have a template that follows the same steps but each project includes different people and different information so the rules definitely help us move through the process all were missing it the project role dynamic instead of having to set it up correctly (and remembering to do it) when we create a project using said template.

@Yulissa_Alvarez I have used a similar workaround with an AI studio rule, but have had the same result. Its inconsistent and sometimes doesn’t work (which has caused issues in our workflows that where painful to resolve)

Also for what could be such a simple automation, it seams like a huge waste of AI credits to be dedicating on average 300-400 credits per automation, which could be run 100’s of times in a month. I would much rather have those credits free for more impactful AI work.