This article describes integration best practices and recommendation from the OnePlan team regarding the Wrike with OnePlan integration.
Effort Rollup
Unlike Wrike, OnePlan automatically aggregates effort values to the parent task, which might cause discrepancies. Suggestion for a workaround is to only add effort to the lowest level sub tasks, or root level tasks that have no sub item.
Project Hierarchy
OnePlan organizes imported projects as a flat list, not supporting Wrike's folder/project hierarchy. Plan your projects within OnePlan to align with your organizational needs, understanding the flat structure limitation.
Auto-adjusted Dates
Wrike might change start/end dates to the next business day automatically, based on your settings. To fix auto-adjusted dates in Wrike:
1, Go to Account Settings: Click your profile picture and select "Account Settings."
2, Update Working Days: Under "Time & Date," click "Working Days" and adjust the workweek to match your schedule.
3, Save: Save the changes.
Project Creation Limitation
Currently, this integration does not have the capability to create new projects within Wrike. However, the OnePlanUpdate strategy can import projects, their tasks and sub-tasks from OnePlan into existing Wrike projects.
Task Order
The order of tasks in Wrike may not exactly match what is in OnePlan due to Wrike's different sorting methods. A workaround for this would be creating a "Sort-order" custom field in both OnePlan and Wrike. Then, sort tasks by this field for consistency.
Task Creation
Wrike allows users to create tasks in the space level, however this feature is not supported in OnePlan. Only tasks that are associated with a project can be synched to OnePlan.
Workflow Statuses
OnePlan does not support any of the workflow statuses from Wrike. It’s also not available in the field mapping section.
API IDs
Wrike uses internal IDs in the APIs, that are not displayed in the Wrike UI. If you want to manually run the OnePlanUpdate strategy, then you will need to use the internal IDs. There is a field called “Wrike API ID" that can be mapped to a OnePlan field. Use this ID when manually running the OnePlanUpdate strategy.
As these IDs are not displayed on the Wrike UI, you have to first map the field and then import the Wrike data into OnePlan to locate the ID you need.