Asana integration

Overview

Integrating Luna with Asana allows you to import your Projects or Tasks and keep them in sync in Luna. Linking your Projects or Tasks to launches in Luna will 1) give visibility to all stakeholders about upcoming launches and 2) allow you to save hours on project management, by keeping Asana and Luna in sync.

How can I connect to Asana?

You can connect to Asana on any of the following pages:

• Sign up flow

• Create a new launch page

• Settings >> Integrations page

• Launch page >> Milestones >> Import from Asana

By clicking on “link” on any of these pages, you will be redirected to the Asana OAuth flow, during which you will consent to the permission scope required by the integration.

The connection between Asana and Luna is a workspace to workspace connection. It’s enough for one user (preferably admin) to connect to Asana, for all users to be able to leverage the connection in Luna.

How can I import issue(s) as launches in Luna?

As a user, you can import any of the following issues: project and task. We recommend you to import issues which need some level of cross-functional and vertical collaboration and visibility:

• If you import one issue → you will be redirected to the launch detail page (LDP) of the imported issue

• If you import more than one issue → you will be redirected to the All launches page, which will display the issues you have imported

What fields do you import/sync with Asana?

The following fields will get imported in Luna and will stay in sync with the launch fields:

Luna - Launch	Asana - Projects	Asana - Tasks
Hamburger menu	Link to project	Link to task
Title	Name	Name
Summary	Project description	description
Owner - If no assignee in Asana, then owner is the person importing the issue	Project owner in project roles	Assignee
Participants	Project members	-
Planned launch date - If no due date in Asana, then launch date is today’s import date	Due date	Due date
Labels	-	tags
Luna creation date (log in DB and reflect in timeline)	created_at	created_at

How can I import issue(s) as milestones in Luna?

As a user, you can link your Asana issues to new or existing Luna milestones:

1. Create new milestones by importing one or more Asana issues into Luna. This is done by clicking on the “Import from Asana” CTA, in the milestones module.

2. Link an existing milestone to a Asana issue. This is done by clicking on the “Link milestone” CTA in the hamburger menu of each milestone.

Milestones data will remain in sync with any changes made to their linked issue, in Asana.

What milestones fields do you import/sync with Asana?

The following fields will get imported in Luna and will stay in sync with the milestones fields:

Luna - Milestones	Asana - Lists	Asana - Tasks
Hamburger menu	See details	See details
Name	Name	Name
Owner - If no assignee in Asana, then owner is the person importing the issue	Owner	Assignee
Target date	Due date	Due date
Child issues	List of tasks	N/A

How can I sync a launch with Asana?

By default, syncing is enabled. In order to stop syncing your launch and milestones with Asana, you will need to opt out from the syncing option available in the LDP hamburger menu:

One sided sync - from Asana to Luna:

Luna uses Asana webhooks to keep the data in sync. As a result, a change to an Asana issue field will trigger the corresponding LDP to refresh with the updated Asana issue data. However, changing the data in Luna will not update the issue data in Asana.

For example, updating the launch date in Luna, will not update the Asana issue due date. However, updates to the Asana issue due date or any other Asana field (in table above) will be reflected in Luna.

[Backlog] We’re exploring launching a 2-way sync and more controls on data mapping and syncing

How can I link Asana issues to a Luna template

While importing issues from Asana, you can link one or more issues to a Luna template. This will allow you to create a more complete and streamlined launch, taking into consideration Asana data complemented with pre-defined modules in the template.

When created, launch data will either come from the Asana issue (data mapping table) or from the template. Some fields clash between the two sources, here’s the import logic:

Clashing field	Rule
Summary	The summary section will consist of both the template and the Asana issue summaries. After creation, the summary section will remain in sync with the Asana issue description, whenever a change is made.
Labels	Labels will be added from both the Asana tasks and the template. After creation, labels coming from Asana will sync as per the above mapping. Labels coming from the template will not be impacted.