This article describes integration best practices and recommendation from the OnePlan team regarding the Asana with OnePlan integration.
Custom Field List for Mapping
Asana does not use a central custom field configuration like OnePlan. It is recommended to configure one or many projects to be used as templates for the list of custom fields that can be mapped between Asana and OnePlan.
Project Creation Limitation
Currently, this integration does not have the capability to create new projects within Asana. However, the OnePlanUpdate strategy can import sections, their tasks and sub-tasks from OnePlan into existing Asana projects.
Dependency Constraint
Due to limitations in Asana’s API, dependencies supported by OnePlan are restricted to the Finish-to-Start relationships. This is applicable for both OnePlan and Anasa tasks.
Empty Section Import Exclusion
While OnePlan supports sections, only sections containing tasks will be imported into the OnePlan Work Plan. Empty sections will not be included in the import process.
Workspace Licensing
Each workspace can be licensed differently in Asana. It is recommended to verify the licensing requirements for the desired features. As an example, custom fields in Asana requires at least Starter subscription.