Company Type
In This Article
The Asana for Jira Cloud integration is available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Premium, Business, and Legacy Enterprise.
Jira Cloud two-way sync functionality is available on Asana Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise.
Visit our pricing page for more information.
Install the Asana for Jira Cloud integration to create transparency between business and technical teams and build interactive, connected workflows.
The Asana for Jira Cloud integration allows business and product teams that plan work in Asana to collaborate and work seamlessly with engineering and technical teams who execute work in Jira.
Note: If your organization uses Jira Data Center, please use the Asana for Jira Data Center integration. Don’t know if your organization uses Jira Cloud or Jira Data Center? Take a look at this Atlassian Community page to find out.
Navigate to a project where you would like to install the Asana for Jira Cloud integration.
From a task in Asana, users can create a new Jira Issue directly in Asana or easily link to an existing Jira issue. We support all Jira Software issue types, including Bug, Epic, Subtask, Story, and Task.
Jira Cloud two-way sync functionality is available on Asana Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise.
A two-way sync refers to automatic updates between designated fields in Asana and Jira. This is achieved by the ability to automatically create and update a task or issue from Asana →Jira, Jira→Asana, or Asana←→Jira on a project basis.
Each Asana project is mapped to sync with a particular Jira Issue type from a Jira project. Asana’s Jira Cloud integration supports standard issue types (e.g., Epic, Story) and custom issue types. Synced fields appear in both list and board views.
Asana | Jira |
---|---|
Task name | Summary |
Description | Description |
Status app custom field | Status |
Priority app custom field | Priority |
Assignee app custom field | Assignee |
Due date | Due date |
Fix version custom field | Fix version |
Other Asana custom field types: Date, People, Number, Single-select, Multi-select | Other Jira custom field types: Date, Number, Dropdown, Checkbox, Short text, Long text |
Jira sprint custom field | Sprint |
Note: We don’t support Timestamp or Dependent drop-down field types in either sync direction. URL, Sprint, Story point estimate fields, and field types are available for Jira → Asana sync only
If you want to kick off work from a Jira Project and keep ongoing data in sync, choose the following settings.
If you want to kick off work from an Asana project and keep ongoing data in sync, choose the following settings.
If you want to mirror an Asana project and a Jira project, choose the following settings.
Comment syncing allows users to stay in their preferred tool (whether that’s Jira or Asana) and collaborate cross-functionally without friction. Users in Jira and Asana can leave comments on tasks or issues in a linked project, and have that comment automatically reflected in the other tool.
Comment sync will occur for any Asana task connected to a Jira issue in the linked project.
Use case 1: Sprint planning with cross-functional teams
Use case 2:
You can import existing Jira issues as Asana tasks and apply the data sync setting to these tasks, allowing you to more accurately reflect how an Asana project is tracking a Jira project with all relevant issues captured as Asana tasks.
When creating an Asana project that should sync with an existing Jira project, import existing Jira issues as well as new issues to sync going forward.
Report by sprint using the sprint field in Jira. The sprint field is a single-select custom field in Asana.
This field should sync just as any other synced single-select field would.
There are scenarios where tasks are already linked to Jira issues prior to having a data sync setting update the values of this task. For example: tasks may be linked to issues prior to a data sync setting being applied to the project, or tasks may already be created prior to getting linked to an issue in a project where the data sync setting is active. In order to have sync apply to these issues while not overwriting values, we apply sync as follows:
A one way sync is performed for all fields, as the user has specified via the data sync settings that one side is the source of truth.
A one way sync is performed for all Jira app custom fields in Asana but standard fields will not be synced to avoid unexpected data loss.
When creating a new Jira issue from Asana, the integration follows Jira’s permission model, so a user can only create a Jira issue if they have permission to do so in Jira. This is the only scenario where a user can write data into Jira (to create a new Jira issue). Similarly, this is also the only scenario where the integration reads Asana data.
After Jira data are synced into Asana tasks, they become part of the Asana work graph object. And therefore, the view and edit permissions to these data are subject to the standard permissions of the tasks and projects.
Learn more about task and project permissions with our Help Center articles.
Custom rules and project-level reporting are available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business, and Legacy Enterprise.
After the data sync, Jira data becomes part of the Asana work graph as custom fields you can use to create project-level dashboards, create rules, and sort, filter, and search tasks.
Please refer to our Jira Cloud FAQ article for more information on Asana for Jira Cloud.
Available on Asana Starter, and on legacy tier Premium | Available on Asana Advanced, Enterprise, Enterprise+, and on legacy tiers Business and Legacy Enterprise |
---|---|
Jira app actions in rules: Premium customers can use rules that create a Jira issue after a trigger is activated. For example, when a task progress is set, a new issue in Jira is created. | Jira app actions in rules: Use rules that create or update a Jira issue after a trigger is activated. |
Link an Asana task to an existing Jira issue. | Jira app trigger: Use rules to create or update an Asana task after creating or updating a Jira issue. |
Two-way data sync: Sync new and existing tasks when they are connected to a Jira issue. The two-way data sync updates task and issue fields when a Jira issue is updated, or an Asana task is updated. | |
Can create custom rules. | |
Can use Jira data to create project-level dashboards, sort, filter, and search tasks. |
These cookies are strictly necessary to provide you with certain features. For example, these cookies allow you to access secure areas that require registration and set your privacy preferences. Because these cookies are essential to providing services to you, they cannot be disabled. You can set your browser to block or alert you about these cookies, but it may cause some parts of the site to not work.
These cookies allow us or our third-party analytics providers to collect information and statistics on use of our services by you and other visitors. This information helps us to improve our services and products for the benefit of you and others.
These cookies provide enhanced functionality, providing chat support, allowing you to more easily complete forms, personalizing content to your preferences, and selecting your communications preferences. If you do not enable these cookies, or choose to disable them in the future, that could impact your ability to use certain features.
These cookies, provided by our third-party advertising partners, collect information about your browsing habits, as well as your preferences for various features and services. They also provide us with auditing, research, and reporting to know when advertising content has been displayed and how successful the content has been. This information allows us and our third-party advertising providers to display relevant advertising content.