Notion and Jira, ready to switch on
A page in the Notion database you connect becomes a Jira issue the moment its status property reaches the value you choose, the page body travels as the description, and the Jira status, sprint and fix version come back as properties product can plan with. 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 Notion integrations · all Jira integrations
Notion already connects to Jira.
It does: Notion's help says you can insert Jira links into pages and sync Jira projects and work items into Notion databases. That brings Jira into Notion for reading. This pair starts in Notion: a page you wrote becomes an issue when it's ready, and the status returns to your property. If seeing Jira in Notion is all you need, use Notion's own sync.
What moves, and when
The details you would normally get after a sales call. Here they are up front.
| What | Direction | When | Rule |
|---|---|---|---|
| Spec page becomes an issue | Notion to Jira | When the status property reaches the value you choose | The page body goes into the description with headings kept, so engineering reads the spec where they work |
| Grouped items under one epic | Notion to Jira | When you use parent relations | Items under the same parent become issues under one epic, and the epic key is written on the parent |
| Jira status into your board view | Jira to Notion | Within seconds | A select property follows every transition, so the Notion board is right without anybody asking |
| Sprint and fix version back | Jira to Notion | When they change | Written into properties you name, which is what product reads at planning time |
| Comments meet in the middle | Both ways | Within seconds | Notion comments become Jira comments with the author; Jira internal comments stay in Jira |
| One page, one issue | Both ways | Every change | The issue key sits in a property, which is why a status set twice never opens two issues |
How to set up Notion and Jira
Ten minutes of your time, then it's ours.
- Choose Notion 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 Notion integration secret and the Jira Cloud API token
- Notion integration secret: open notion.so/my-integrations, press New integration, choose Internal and give it a name. Full Notion 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 keysEach key is checked against Notion'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 page, then it's RunningA minute or two. Create a page in Notion, watch its twin appear in Jira, then close one and watch the other close.
When Notion 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 Notion and Jira
Three ways people connect these two, and what each one asks of you. The built-in app is described above.
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.
Can specs stay in Notion and tickets in Jira?
That's the whole idea. Product writes and plans in Notion, engineering works in Jira, and the two meet on the status property and the description. Nobody copies a spec into a ticket by hand again.
Does every page become an issue?
No. Only pages whose status reaches the value you name, usually Ready for dev. Ideas and drafts stay in Notion until somebody decides they're work.
What can Jira integrate with?
Ready-made on Dovetly, Jira pairs with Slack, Trello, Asana, HubSpot, Google Sheets, Notion, monday.com and Airtable. All of them are for Jira Cloud and use an API token from id.atlassian.com; Server and Data Center aren't covered. Anything else, describe it and a person replies with a price within a working hour.
Is Jira better on a server or in the cloud?
We can only speak for what we connect: Jira Cloud. Its REST API and API tokens are what this pair uses, and Server and Data Center use a different API that isn't covered here. If you're on Data Center, describe it and we'll say whether we can build it.
Anything to know about Notion?
An integration only sees the pages and databases you have connected it to, so a database nobody shared with it stays invisible even to a valid key.
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.
