Limitations of Unito’s Asana Integration

Here's a breakdown of what Unito's Asana integration can't do yet — and a few other considerations.

Unito's Asana integration is designed to get crucial data out of your projects and into other tools. You've seen what Unito can do for Asana users, so this article will cover what it can't do — yet.

What this article covers:

• Unsupported fields
• Unsupported mappings
• Other limitations
• Other Asana considerations

Unsupported fields

While Unito's integration for Asana supports most of the tool's fields, there are some it doesn't support.

• Project End Date, but you can sync Project Start Dates.
• Due On
• Task Approval States (Approve, Request Changes, and Reject)
• Task followers
• Dependencies
• Date Custom Fields

Unsupported mappings

You can use Unito to map Asana fields to similar fields in other tools (or other Asana projects) in most cases. However, there are a few corner cases that aren't supported.

• Asana Assignees with Text Custom Fields
• Asana Sections with GitLab Milestone

Other limitations

• @mentions: Mentions in the description can't be synced with Unito.
• Attachments must be added to an Asana task — not the task's description — in order to sync with Unito.
• Edited comments:  Unito can only sync new comments, not edits to existing comments. 
• Description fields:  Text in the description can't include a < or > value. Doing so will cause a formatting error that will prevent your task from syncing.

Other Asana considerations

Unito is compatible with all tiers of Asana subscriptions, including free plans! Some functionality is limited to Asana’s higher tiers, such as syncing custom fields.