HubSpot and Jira, ready to switch on

A HubSpot ticket that reaches the stage you name opens a Jira issue with the contact and the ticket link, a deal can open a feature request the same way, and a Jira transition writes back onto the ticket so support answers without asking engineering. You paste two keys in your account and it runs, in about ten minutes.

Connect for $39 a month Mine is a bit different

No setup fee, cancel any month, and a person on live chat if a key doesn't work.

More with these apps: all HubSpot integrations · all Jira integrations

HubSpot already has a Jira integration.

It has: HubSpot's help describes connecting HubSpot and Jira, and a Jira data sync that turns support tickets into issues. If you're on a plan that includes it and it does what you need, use it. This pair is for the rules it leaves to you: which stage opens an issue, deals opening feature requests, what a resolved issue does to the ticket, and a person who fixes it when Atlassian changes something.

What moves, and when

The details you would normally get after a sales call. Here they are up front.

What	Direction	When	Rule
Ticket becomes an issue	HubSpot to Jira	When it reaches the pipeline stage you choose	In the project and issue type you name, with the contact, the priority and a link to the ticket
Deal opens a feature request	HubSpot to Jira	When the deal property you nominate is set	Optional, for sales promises that engineering should actually see, with the amount on the issue
Status back on the ticket	Jira to HubSpot	Within seconds	The Jira status lands in a ticket property, and the stage you map moves the ticket
Comments both ways	Both ways	Within seconds	Public ticket comments become Jira comments and back; internal Jira comments stay internal
Resolved means ready to reply	Jira to HubSpot	When the issue is resolved	The ticket moves to the stage you keep for it, never straight to Closed
One ticket, one issue	Both ways	Every change	Held by ids on both sides, so a ticket reopened twice does not open two issues

How to set up HubSpot and Jira

Ten minutes of your time, then it's ours.

Choose HubSpot and Jira

Press 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 account

Card or invoice, about two minutes. The account opens with this integration waiting for its two keys.
3
Paste the HubSpot private app token and the Jira Cloud API token
- HubSpot private app token: in HubSpot open Settings, then Integrations, then Private apps, and create an app. Full HubSpot 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 seven minutes for both.
We check both keys

Each key is checked against HubSpot'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.
Win one test deal, then it's Running

A minute or two. Move a test deal to the stage you chose and watch the issue appear in the project. From then on we watch it for you.

When HubSpot or Jira changes its API, we fix it within a working day. You don't get a ticket to solve.

$39a month

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.

Connect for $39 a month

No setup fee, cancel any month

Ways to connect HubSpot and Jira

Three ways people connect these two, and what each one asks of you. The built-in app is described above.

Built-in appZapier or MakeDovetly

Who sets it upYou, in the app's own settingsYou, one step at a time in the scenario editorAlready built. You paste two keys.

Who fixes it when it breaksThe vendor, when it ships a fixYou: the scenario is yours, so the fix is tooWe do, within a working day, and we watch it

What you need to knowThe app's own settings and what they coverTriggers, actions, filters and how the fields of HubSpot and Jira mapWhere the two keys are. The guide shows it.

PriceSet by the vendorSet by the builder's plan, counted in tasks or operations$39 a month, flat, whatever the volume

Before you decide

Which Jira project?

You name it while connecting, and a second pipeline can point at a second project. Any field that project requires gets a default from you, so Jira never refuses the issue.

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.