Use project owner in task level rules.

English Forum Ask the Community
1

Hi everyone,

I’m trying to build a scalable workflow where the Project Owner acts as the primary Point of Contact (POC) to influence task-level automation. Specifically, I want to avoid hard-coding names into rules so that the system remains dynamic when templates are used by different owners.

The Goal:

  1. Use the Project Owner as the “Source of Truth” for who is the POC.

  2. Use a second People Custom Field called “Internal Editor” at the task level.

  3. Have task-level rules (like “Assign to Editor when moved to Review”) trigger based on who that Project Owner is.

The Problem: Asana rules currently require a specific user to be selected in the “Then” action. I cannot find a way to “Map” the Project Owner variable directly into a Custom People Field (Internal Editor) via a rule.

My Questions for the Community:

  • Is there a way to sync the Project Owner identity to a Task-level People Field automatically without manually selecting a name in every project?

I’d love to hear how you handle “Dynamic Routing” so that templates don’t require 10+ rule updates every time a new project is launched.

2

Hi @Occasio_Gee1 , indeed, this is not possible using the native rule actions. However, this is most likely possible by using Script actions within rules, which are exclusively available on Enterprise tiers.

Your rule will essentially pull data from fields at the project level and populate then into fields on the task level.

More info here:

I’m no developer but I’ve managed to create numerous scripts using ChatGPT or Copilot.

3

FYI this is also available via our Flowsana variable substitution (we have a variable for {project.Owner}).

1 Like