What this article covers:
- Best use cases for an Asana-Jira integration
- What is synced between Asana and Jira
- What is not synced
- Asana-Jira sync customization options
Use Asana and Jira together to improve your team's efficiency. Whether you need more information to get your workflow set up or you're just checking us out, this guide will show what we sync, how to get started, and how to solve common problems.
Before you start, have you made sure you configured Jira for Unito access?
Best use cases
- Coordinate multiple repos and projects in Asana
- Maintain a high-level roadmap in Asana
- Submit and track requests in Jira directly from Asana
- Collaborate on projects between development and business teams
What is synced?
NEW: Unito users can now build workflows to sync Jira sprints and backlogs to sections in Asana!
A field you would like to sync is not listed? Let us know!
What is not synced?
Again, Jira sprints can now be synced!
Is there a feature you would really like? Let us know!
Here are all the available options for Asana and Jira:
Add rules to filter by tag or label
Unito will sync all work items by default but you can customize your workflow by syncing just some of them (complete guide).
Add rules to filter by issue type
You can filter which type of issues you want to be synced to Asana (complete guide).
You can choose to sync only from Asana to Jira or Jira from Asana. Here is how it works.
Map your Jira and Asana users
Default type for new Jira issues
Unito lets you choose which issue type should be created in Jira each time a new task is synced from Asana.
Sync closed work items
Unito will automatically sync open items automatically. But here is how to also sync closed items prior to the flow creation.
Prefix Asana task title with Jira issue number
Unito doesn't sync the issue number is Asana by default but you can enable that in your flow settings under the Asana tab.
Here is how to do it.