How to Integrate Asana With Jira

Asana's Home and Inbox are where business-side users track their own tasks and notifications: overdue items, due-today items, activity grouped by date. On the Jira side, work lives in projects or spaces with items like epics, stories, and tasks carrying their own keys, such as TS-8 or POS-3. The integration's job is to let someone living in the Asana view see and act on what's happening in a Jira space like that, without needing a Jira login.

A typical Jira space, like a Scrum backlog, organizes work into an active sprint and a backlog underneath it, with each item showing a status (To Do, In Progress, In Review), a due date, story points, and an assignee avatar. This is the granular, engineering-facing view the integration reaches into. When someone in Asana wants an update on a task like "Design Packaging," the Jira Cloud app is what pulls that status back without them opening Jira directly.

Inside an Asana project, click Customize, then Apps, and search for Jira Cloud (Browse apps works the same way if you're starting from outside a project). The listing is developed by Asana itself and lays out the split plainly: business teams get Jira updates without leaving Asana, and engineering teams keep working in Jira while their changes surface on the linked Asana task. Click Connect to Jira Cloud and authorize the connection against the Jira site you want linked.

Once connected, open the app's Data sync setting tab. This is where the plan difference shows up directly: on Business or Enterprise, you can configure full two-way sync between an Asana project and a Jira project, choosing which fields carry across and whether comments sync too.

On Starter, that tab is largely unavailable; you're limited to creating an Asana task from a Jira issue and viewing a Jira widget on a task, one direction, not a live two-way sync. Confirm which tier your workspace is on before telling a team to expect automatic two-way updates.

The install screen lists what Jira Cloud can do once connected: access your name and email, access your tasks, projects, and workspaces, create and modify tasks and comments, and display external Jira data on your Asana tasks, visible to anyone who already has access to those tasks. That last point matters for anything sensitive, since linking a Jira issue to a shared Asana task makes that Jira context visible to every collaborator on the task, not just you.

With the app installed, open an Asana task, find the Jira Cloud option in the task's app row, and either link it to an existing Jira issue or create a new one. Test with something low-stakes: link one task, change its status in Jira, and confirm the update lands on the Asana side. If you're on Business or Enterprise, also confirm the sync direction you configured (Asana to Jira, Jira to Asana, or both) is behaving the way you set it up before rolling the app out more broadly.