Insert Custom Field Values from Triggering Task into New Task via Rules

Dear Asana Team,

I would like to request a new feature for Asana’s automation rules. Specifically, I am looking for the ability to insert values from custom fields of a triggering task into the custom fields of a new task created by an action in a rule.

Current Scenario

At the moment, it is possible to add values from custom fields into the task description of the new task through automation rules. However, there is no option to directly transfer or inherit the values into the actual custom fields of the new task. This limitation requires manual copying and re-entering of data, which can disrupt workflows.

Feature Request

• Add the option to transfer selected custom field values from the triggering task into custom fields of the new task when using the action to create a new task or subtask in a rule.

• Ideally, users would be able to map specific custom fields from the triggering task to selected fields in the new task created by the rule.

Why This Feature Would Be Helpful

This feature would help streamline workflows by reducing manual data entry and ensuring consistent information transfer between tasks, especially when automating task creation. It would save time, minimize errors, and enhance efficiency for users who rely on automation to manage complex projects.

This functionality would be especially helpful for Text and Number fields, where precise data needs to be carried over from one task to another. However, the request applies to all types of custom fields (e.g., dropdowns, dates, persons, etc.).

2 Likes

This would be very helpful. We currently have to rely on creating new subtasks instead so we can retain Text values. For visibility, it would be amazing to be able to create full on tasks that would carry the values.

Hi Cyrill,

Just for clarity, can you list the specific rule action(s) where you would want this option available? Thanks!

I added more details in the first point under Feature Request. Do you think it’s clear enough now?

Yes, thanks!

This would be very helpful when needing a task to trigger a SEPERATE task but needs to inherit the same data submitted in a form. We have several use cases this would be helpful. Sometimes multiple teams working from the same task adds to confusion