Asana and Jira, ready to switch on
A task moved into the Asana section you nominate becomes a Jira issue, a Jira transition moves the task and writes the status into a custom field you already report on, and comments travel with their author. You paste two keys in your account and it runs, in about ten minutes.
No setup fee, cancel any month, and a person on live chat if a key doesn't work.
More with these apps: all Asana integrations · all Jira integrations
What moves, and when
The details you would normally get after a sales call. Here they are up front.
| What | Direction | When | Rule |
|---|---|---|---|
| Task becomes an issue | Asana to Jira | When it enters the section you name | In the project and issue type you choose, with the description, the due date and the task link |
| Status into a custom field | Jira to Asana | Within seconds | The Jira status lands in an Asana field, so product reads it in the view they already use |
| Subtasks travel one level | Asana to Jira | With the parent | First-level subtasks become Jira subtasks of that issue; deeper trees stay in Asana |
| Assignee by email | Both ways | With every change | Matched on address; anyone we can't match falls to the person you nominate |
| Comments | Both ways | Within seconds | With the author's name, so a question asked in Asana is answered in Jira and seen in Asana |
| Done both ways | Both ways | When either closes | A resolved issue completes the task, and a completed task transitions the issue to Done |
How to set up Asana and Jira
Ten minutes of your time, then it's ours.
- Choose Asana and JiraPress Connect. This pair is already selected on the checkout page at $39 a month, and there's nothing else to pick.
- Pay and open your accountCard or invoice, about two minutes. The account opens with this integration waiting for its two keys.
- Paste the Asana personal access token and the Jira Cloud API token
- Asana personal access token: open app.asana.com/0/developer-console, or go to Settings, then Apps, then Manage developer apps. Full Asana guide
- Jira Cloud API token: open id.atlassian.com/manage-profile/security/api-tokens and press Create API token. Full Jira guide
Each screen carries the full guide with the exact menu names, about six minutes for both. - We check both keysEach key is checked against Asana's and Jira's own API the moment you paste it. If one doesn't pass, the screen says what to fix, and a person joins the chat if that isn't enough.
- Create one test task, then it's RunningA minute or two. Create a task in Asana, watch its twin appear in Jira, then close one and watch the other close.
When Asana or Jira changes its API, we fix it within a working day. You don't get a ticket to solve.
- Everything in the table above, with monitoring on.
- Fixes when either app changes its API.
- A person on live chat, replies within a working hour.
- Custom logic beyond the table is priced separately.
No setup fee, cancel any month
Ways to connect Asana and Jira
Two ways people connect these two, and what each one asks of you.
Before you decide
Which one is the source of truth?
Neither, and that is why the loop guard matters. Each team works where it prefers, and the twin follows. If you would rather one side be read-only, say so and we set it that way.
Do subtasks and checklists come across?
The top level does, with title, dates and assignee. Subtasks and checklists differ so much between these two that we treat them as a custom job rather than pretending they map cleanly.
Asana has its own Jira Cloud integration.
Yes. Asana for Jira Cloud gives an immediate two-way sync, and its help page says you can create or link a Jira issue from a task. If it does what you need, keep it. Ours is for teams that want one fixed rule: tasks become issues only from one section, the status lands in a field you already report on, and a person is on the phone when Atlassian changes something.
Which Jira project and issue type?
You name both while connecting, and a second section can point at a second project. A required field on that issue type gets a default from you, so Jira never refuses the issue.
What if a task has no section yet?
Nothing happens. Only tasks that enter the section you named cross over, which is what keeps a brainstorm board out of the engineering backlog.
Can you use Asana as a ticketing system?
You can log requests in Asana, and this pair hands them to engineering: a task moved into the section you nominate becomes a Jira issue with the description and the due date, the Jira status comes back into an Asana custom field, and comments travel with their author. Closing on either side closes the other.
Does Asana integrate with Jira?
Yes. Asana has its own Jira Cloud integration (above). This pair is the rule-based one: tasks become issues only from one section, first-level subtasks come along, assignees are matched by email, and a person keeps it working. You paste an Asana personal access token and a Jira Cloud API token; $39 a month.
Anything to know about Asana?
A personal access token acts as your user, so tasks are created in your name and only in projects that user can see.
Anything to know about Jira?
This is for Jira Cloud. Server and Data Center use a different API and aren't covered here.
What if mine is a bit different?
Tell us what should go where in plain words. Small changes to the rules above are usually free; bigger ones we price the same day and build into the same account.
