Asana snap-in acts as a connector between Asana and DevRev. It was created as an example of a functional snap-in and is designed to help developers create their own snap-ins or extend the existing one.
It enables a forward sync, where it extracts tasks, task attachments, and users from Asana and imports them into DevRev. Additionally, it supports incremental and reverse sync, allowing the extraction of issues and attachments from DevRev to be imported into Asana.
- Asana project is used as an external sync unit for DevRev.
- Asana tasks map to DevRev issues:
- The task
name
becomes the issuetitle
. - Task
html_notes
are transformed into the issuebody
. - Task
assignee
is mapped to bothcreated_by
andowned_by
in DevRev. - Task
created_at
is mapped tocreated_date
. - Task
modified_at
is mapped tomodified_date
.
- The task
- Users in both systems are identified by a
name
andemail
.
priority
andstage
are required fields for an issue object in DevRev. Asana tasks by default do not have these kind of fields, but they can be added as custom fields.- Extraction of Asana custom fields is currently not supported since custom field usage requires a payable Asana account.
- By default, all issues created in DevRev from Asana tasks have a priority value of "P0" and start in the "Backlog" stage.
- Developers can find instructions for further snap-in development in the DevRev documentation.