Asana Integration
Configure Asana task creation, project mappings, and portfolio review
The Asana integration creates linked tasks for Core tickets and updates the linked task when supported ticket fields change.
Configure Asana
You need permission to manage integrations and an Asana Personal Access Token with access to the projects you plan to use.
- Open Settings → Integrations → Asana.
- Enter your Personal Access Token in the configuration form.
- Choose the optional Workspace and Default Project.
- Save the configuration and confirm the integration is enabled.
To replace credentials, re-enter the token in the form. Stored tokens are not displayed again.
Connect projects
Tasks use the Asana project associated with the ticket's project or customer default project. Projects synced through Everhour can carry an Asana mapping; Core recognizes their as: project identifiers.
Before expecting a task, confirm the ticket has a project and that the project has a valid Asana mapping.
Ticket-to-task workflow
Core can create the task in the background when a ticket is created or assigned a mapped project. Starting a ticket timer also ensures the task exists. Email and form tickets may not acquire a project until triage, so check the project selection if there is no task yet.
The task includes the ticket title, number, description, and a Core link. Long descriptions are shortened when needed; Core can fall back to a compact note with the ticket link so task creation can finish.
Updates to a linked ticket's title, description, and completion state are reflected in its Asana task. Use the stored task link to open it in Asana. The Asana settings page also lists recent linked tasks.
This workflow does not offer a general two-way mapping of comments, attachments, or Asana sections to Core statuses.
Portfolio review
Open importer on the Asana settings page opens the portfolio importer:
- Enter an Asana portfolio ID and run the dry-run.
- Review projects against the mappings already in Core.
- If needed, add selected unmapped projects to the Asana reconciliation queue for review.
The dry-run reads Asana and Core. Adding queue items records review work in Core; the importer does not create projects or change Asana records.
Troubleshooting
- No task: confirm the integration is enabled, the token can access the target project, and the ticket's project mapping is valid.
- Ticket is visible before the task: creation continues in the background; check the linked task and sync result after it finishes.
- Time has not reached Everhour: an Asana task can take time to become available in Everhour. Review the time entry's sync status in Core and retry a failed entry where offered.