Jira integrations, ready to switch on
Jira is where engineering and support teams track issues, and other teams keep asking for a way to get things in and out of it. Tickets, form responses and deal events want to become issues, and issue changes want to reach a chat. You create an API token for your Atlassian account, paste it with your email and site address, and it connects.
Projects and tasks · all Projects and tasks integrations · atlassian.com/software/jira
Jira and the apps it talks to
Eight pairs, $39 a month each, flat whatever the volume, all on the same Jira Cloud API token. Click a pair to see exactly what moves, and when.
Projects and tasks
Trello and Jira
Trello cards become Jira issues, and transitions move the card back
$39/mo
Connect
Asana and Jira
Asana tasks become Jira issues when they're ready, status comes back as a field
$39/mo
Connect
Notion and Jira
Notion specs become Jira issues when they're ready, and Jira status shows on the page
$39/mo
Connect
monday.com and Jira
Items in a group you name become Jira issues, sprint dates land on the timeline
$39/mo
Connect
Name the second app and say what should go where. A person replies with a price within a working day, and the finished integration shows up in the same account as the ready-made ones.
What Jira sends and receives
Each line is a row from one pair's table, in that pair's own words. Open the pair for the rule behind it.
Out of Jira
- New issue in the projects you name to Slack, within seconds
- Transitions to Slack, within seconds
- Comments to Slack, within seconds
- Blockers to Slack, when the priority or the flag changes
- One key, one thread to Slack, every event
- Transitions move the card to Trello, within seconds
- Status into a custom field to Asana, within seconds
- Status back on the ticket to HubSpot, within seconds
Into Jira
- Card becomes an issue from Trello, when it enters the list you name
- Labels set priority from Trello, with the card
- Task becomes an issue from Asana, when it enters the section you name
- Subtasks travel one level from Asana, with the parent
- Ticket becomes an issue from HubSpot, when it reaches the pipeline stage you choose
- Deal opens a feature request from HubSpot, when the deal property you nominate is set
- Requests tab opens issues from Google Sheets, every few minutes
- Spec page becomes an issue from Notion, when the status property reaches the value you choose
Good to know about Jira
- This is for Jira Cloud. Server and Data Center use a different API and aren't covered here.
- A field that a project marks as required has to be on the create screen for that issue type, otherwise Jira refuses the issue; permissions and workflow properties can refuse it the same way. We set a value or a default for the required fields while connecting and check the rest.
Before you decide
What do I paste to connect Jira?
Jira Cloud API token. Open id.atlassian.com/manage-profile/security/api-tokens and press Create API token. About three minutes, and we check the key the moment you paste it.
What if the pair I need isn't here?
Describe it: name the second app and say what should go where. A person replies with a price within a working day, and the finished integration shows up in the same account as the ready-made ones.
What happens when Jira changes its API?
We fix the integration on our side within a working day. You don't get a ticket to solve.