Advanced Task Synchronization for Custom Field Management

“Hi everyone, We would like to copy multiple tasks from one project to another, including all their custom field values. So far, we have tried copying and pasting the tasks using Ctrl+C and Ctrl+V. However, only the project title is carried over, while the custom fields remain empty in the destination project. Both projects already contain the same custom fields, so we expected the existing values to be copied as well. Is there a way to copy tasks between projects while preserving all custom field values? Or is there an alternative approach that would allow us to achieve this? Thanks in advance for your help!”

“Hi Asana Community! Have you ever updated a custom field at the project level and wished that the same change could automatically reflect across every task within that project? For example, when a project owner selects a region, business unit, priority, or delivery category, the corresponding information may also need to be updated on all the tasks in that project. Traditionally, this could mean bulk-editing tasks or building a workaround to keep the data consistent. With the ability to trigger actions on tasks based on changes to a project’s custom field through portfolio-level rules, we can now explore a more streamlined approach to this problem. I’d like to share a practical use case. The business problem: Regional project management Imagine an organization managing hundreds of projects across multiple regions, such as North, South, East, and West. Each project contains dozens of tasks, and the organization wants every task to carry the correct region for reporting, filtering, and operational tracking. Consider this workflow: A project is created from a standard template. The project owner selects South in the project’s Region custom field. Every task within the project needs to reflect South in its own Region custom field. Later, if the project is reassigned to another region, the task-level values need to be updated accordingly. Without automation, someone must update the individual tasks manually. This becomes increasingly difficult as projects grow and requirements change. The solution: Use a portfolio-level rule The idea is to use a portfolio-level rule to watch for changes to the project’s custom field and then apply an action to every task in that project. How to configure the rule Trigger Select the relevant portfolio. Configure the trigger to detect when the project’s Region custom field changes. Where supported by the rule builder, specify the relevant region value as a condition. Action Configure the action to operate on the tasks within the affected project. Set the task-level Region custom field to the required value. The result is a rule that propagates the selected project-level value to the tasks in that project. Example: What happens when the region changes? Event Project Region Task Region Initial setup North North Project reassigned South South Project reassigned again West West Instead of updating each task individually, the rule handles the task-level changes when the relevant project field changes. Other practical use cases The same pattern can be applied to several business scenarios, depending on the fields and actions available in your Asana setup. 1. Priority and escalation management When a project’s priority changes to High, automatically update a task-level escalation field so teams can identify work associated with high-priority initiatives. 2. Business unit alignment When a project is assigned to a business unit, update the corresponding task-level Business Unit field to support consistent filtering and reporting. 3. Compliance and governance When a project enters a particular governance category, update a task-level review or compliance field to indicate that the relevant workflow applies. 4. Delivery classification When a project changes its delivery type, update a task-level classification field to help teams organize and report on the work consistently. Why this matters This approach connects project-level decisions with task-level execution. Less manual work: Reduce repetitive bulk updates when project attributes change. Better data consistency: Keep relevant task fields aligned with the project’s current attributes. Improved reporting: Make it easier to filter and report on tasks using standardized custom fields. Greater scalability: Apply the same automation pattern across projects managed through a portfolio. A few things to consider Before implementing this pattern, test the rule with a sample project and verify its behavior. Confirm that the action updates the intended tasks and custom field. Check how blank or previously populated task fields are handled. Test whether subsequent project-field changes overwrite existing task values as intended. Verify the behavior for newly created tasks, since a rule triggered by a field change may not automatically populate tasks created afterward. Consider limiting the action to matching tasks if you don’t want every task updated. Over to the community I’d love to hear how others are using portfolio-level rules to connect project-level decisions with task-level workflows. Which project-level field would you propagate to tasks in your organization? Is it Region, Priority, Business Unit, Compliance Category, or something else? Please share your use cases and any additional patterns you’ve discovered! image480×400 12 KB”