...
Getting Started with Asana
Anchor | ||||
---|---|---|---|---|
|
...
Strategic Roadmaps to your Asana Instance
...
In order to connect your Roadmaps to your instances & projects in Asana, an Account Admin on your Roadmunk Strategic Roadmaps account will need to establish the connection between Roadmunk Strategic Roadmaps and Asana first. Once this connection is established, users will be able to view and select this integration option during their on-roadmap setup and save both instance & credential details for future setup of additional roadmaps.
Expand | ||
---|---|---|
| ||
To create a new Asana integration in RoadmunkStrategic Roadmaps:
|
Expand | ||
---|---|---|
| ||
To update an existing Asana integration in RoadmunkStrategic Roadmaps:
|
Expand | ||
---|---|---|
| ||
To delete an existing Asana integration in RoadmunkStrategic Roadmaps:
|
Anchor | ||||
---|---|---|---|---|
|
...
Strategic Roadmaps in Asana
In order to authorize the data transfer between Roadmunk Strategic Roadmaps and Asana, Roadmunk Strategic Roadmaps relies on a user-generated credential which allows the user to view and pull their data from their projects. In this case, we require a Personal Access Token (PAT) generated in Asana as your credential and during the roadmap setup will allow you to set a Credential Label so you can easily differentiate this particular token from others you may use (in the case of teams working across multiple active Asana deployments).
...
In Asana, click on your avatar and select My Settings > Apps > Manage Developer Apps.
Click + Create new token.
Specify a Token name. It can be anything and does not need to match the Credentials Label in RoadmunkStrategic Roadmaps.
Check the I agree… statement.
Click the Create token button.
Click the Copy button and paste the value into the Personal Access Token field in RoadmunkStrategic Roadmaps.
For the sake of user & data security, tokens can be reset or removed by either the user or their administrator from the Developer Apps menu. For more details regarding token expiry, please refer to the line item in the What to Expect After Integrating section.
...
It's a quick and easy process to set up an integration between your Asana projects and your team's roadmaps in RoadmunkStrategic Roadmaps. The setup process can be broken down into three stages: triggering the integration, applying synchronization settings, and applying field and filter settings. Once those have been completed, your roadmap will be set to pull and visualize data from Asana as needed.
...
All fields pulled from Asana are Account-Level by default - Since the properties and values of these synchronized fields are managed in Asana, we automatically promote them to account-level so they can be accessible as common fields in Portfolio roadmaps.
There is an External ID field that appears in the Items Table view - When synchronizing data from Asana, we pull in the ID of each task for reference on your roadmap. This is clickable and linked out to your team's Asana instance, so you can quickly access the respective work item from either your Table view and Item Card.
Unable to change or add new projects on a single roadmap - As with our other integrations, we limit connections between roadmaps and third-party tools to be a 1:1 connection. This means that you will be unable to sync multiple projects into a single roadmap; however, you will be able to create multiple roadmaps for each project and use those as sources in a Portfolio roadmap.
Additional Date fields will be read-only - Due to a variance in field formatting between Roadmunk Strategic Roadmaps and Asana, any additional Date fields selected which are not mapped to Start and End Dates will be pulled in as read-only text fields.
Tokens may expire a set number of days after being created - Unlike API tokens generated for credentials in Jira, which have a longer-term expiry, Personal Access Tokens generated in Asana may eventually expire. While Asana does not publicly list specific expiry limits for their Personal Access Tokens, our team always likes to make note of this with token-based authentication.
...