Logos for Notion and Jira, representing syncing Jira issues with Notion's synced databases and Unito.
How to Sync Jira Projects to a Notion Database (3 Methods)
Logos for Notion and Jira, representing syncing Jira issues with Notion's synced databases and Unito.

How to Sync Jira Projects to a Notion Database (3 Methods)

It’s a tale as old as time. Your software development teams and product managers love Jira…and no one else does. Anyone collaborating with your developers has to face the tough choice of learning to use Jira or constantly copying and pasting data to their own tool — like Notion. But who has the time for that? Not you. Thankfully, there’s more than one way to set up an integration from Jira into Notion.

Two methods use built-in Notion features while the last depends on a little help from Unito. Here’s a guide to both.

First method: Set up a Jira → Notion integration with synced databases

With Notion’s connections, you can pair tools with your Notion pages to streamline work across teams. At their most basic, these connections can create individual, read-only replicas of work items from other tools, allowing you to keep an eye on their progress without leaving Notion. But synced databases — currently available for GitHub and Jira — take this to a whole other level.

Synced databases bring an entire Jira project into Notion in just a few clicks, meaning you can keep track of dozens of issues without any extra manual work. Here’s how it’s done.

Start by creating a blank Notion page that’ll hold your synced database.

A blank page in Notion with the title of Sprint tasks.

Next, you’ll need to authorize Jira in Notion. Go to the sidebar and click Settings & members.

A screenshot of Notion's sidebar menu.

From there, go to My connections.

A screenshot of Notion's Settings & Members menu.

Find Jira and click Connect.

Notion's "My connections" menu, one way to set up a Jira to Notion integration.

You’ll get this screen from Atlassian. Log in and authorize Jira.

Atlassian's login screen.

Now the magic’s about to happen. Go to your Jira project and copy its URL.

A screenshot of a Jira project.

And paste it into your Notion page. You’ll get a pop-up menu here; make sure to click Paste as database.

Notion's synced databases menu.

Just like that, you’ve created a synced database! Your Jira issues will automatically sync into Notion, and you can open up any of them just like on any other Notion page.

A screenshot of a Notion synced database full of Jira issues.

Limitations of this method

It’s pretty hard to beat “copy and paste a link” for ease of use and simplicity. If you’ve always wanted to see what was happening in a specific Jira project without actually opening it, Notion’s synced databases are just what you’ve been waiting for. That said, synced databases have a few limitations you should consider:

  • They’re read-only: If you thought you’d be able to make changes to your Jira issues from Notion, think again. Treat your synced database as a window into your Jira projects, nothing more. If you wanted an all-in-one workspace that had both Jira issues and Notion database items in a single place, this isn’t the right method.
  • They need a bit of cleanup: Since creating a synced database is done through essentially a single step — pasting a link — you might find yourself with some cleanup to do in Notion. For example, importing a Jira project for this blog post resulted in columns that were out of order and a ton of accidentally duplicated fields.
  • They only work for a few tools: Synced databases are currently only available for Jira, GitHub, and Asana. That’s great if you’re collaborating with people in those tools, but otherwise you’re pretty limited.

So while creating a synced database only takes a few clicks, it’s not always the best solution. That’s fine if you just want a window into a Jira project — and can put up with a bit of manual cleanup — but that won’t work for everyone.

Luckily, there’s another way.

Second method: Embed Jira issues in your Notion workspace

A synced databases bring in entire Jira projects, but sometimes you only need a few Jira issues to give context to work happening in Notion. When that’s the case, you can instead embed single Jira issues, and it’s no more complicated than copying and pasting a link. Here’s how.

First, go to the Jira issue you want to embed in Notion and hit the share button.

A screenshot of a Jira issue.

Hit Copy link.

A screenshot of a Jira issue, with the Copy link button highlighted.

With the link to your Jira issue safely copied, head over to the Notion page you want to embed it in and paste the link.

A screenshot of a Jira issue copied and pasted in Notion.

You’ll get a popup asking you how you want your newly embedded Jira issue to show up. Two of them — paste as mention and paste as link — are mostly cosmetic differences. Paste as preview will actually give you information about that Jira issue you can reference elsewhere. All three options allow you to click through the issue to open the associated Jira project, as long as you have access to it.

Here’s what each version would look like, starting with Paste as link.

A screenshot of a Notion page with a Jira issue pasted as a hyperlink.

Here’s what Paste as mention looks like.

A screenshot of a Jira issue pasted as a mention in Notion.

And, finally, Paste as preview.

A screenshot of a Jira issue pasted as a preview in Notion.

Paste as preview gives you a bit of information about each Jira issue, including its status, its issue key, and more.

Limitations of this method

While copying and pasting a link into Notion is about the simplest way to set up an integration, this method does have its drawbacks.

  • It’s read-only: You won’t be making any changes to the Jira items you paste in Notion. Essentially, you’re just creating a shortcut to your Jira board with a bit of extra information.
  • It’s limited: By mentioning specific issues, you can add context to your work in Notion. But if you want to ask for updates, make changes, or just about anything else, you’ll either need to go into Jira or rely on another platform.
  • There’s no impact on Jira: Copying and pasting your Jira data into Notion adds valuable context in Notion, but the same can’t be said about Jira. If you want to know what’s going in Notion from Jira, you’ll need to use a different integration.

Third method: Sync data with Unito’s Notion→Jira integration

Unito is a no-code workflow management solution with the deepest two-way integrations for some of the most popular tools on the market, including tools like Notion, Jira, Trello, Google Sheets, and more. With a Unito flow, you can automatically sync Jira issues to a Notion database and edit data in both tools.

Here are a few reasons why Unito is the best way to sync Jira and Notion:

Why does this work? When you connect a Jira project to a Notion database with a Unito flow, your Jira issues will become pages in Notion, keeping everything in sync. And because this works in both directions, you don’t have to worry about either tool becoming outdated, and you can make changes on either end

“Our workflow is only possible because of Unito. I’ve looked at other similar services but it’s not possible anywhere else because of Unito’s integration for Notion and Airtable.”

Tom Nassr, CEO at XRay.Tech

Quick facts about Unito’s Jira to Notion integration

Wondering if Unito’s integration is the best fit for your workflow? Here are some quick facts to help you decide.

Unito has the deepest two-way integrations on the market

Automation solutions like Zapier and Tray.io have a ton of integrations but they’re best suited for one thing: pushing data. That means you can get away with using them if you just want to create new pages in Notion or Jira issues, but not if you want to sync any kind of data between them. You’d need a ton of individual automations to get something like that.

Not so with Unito. With a single Unito flow — which you can build in minutes — you can automatically create new work items in both tools and keep them up-to-date automatically.

Unito supports the fields you need

Some of the integration platforms you’ll find on the market lack depth: they only support a few fields in your tools. That means you won’t get all the data you need. With Unito, you’ll get an in-depth view of what’s going on in your tools.

  • Supported fields in Jira: Affected version, Assignee, Attachment, Comment, Component, Description, Due Date, Epic, Fix Version, Issue ID, Issue Number, Issue Status, Issue Type, Label, Link to Issue, Original Time Estimate, Priority, Project Name, Remaining Estimated Duration, Reporter, Resolution, Sprint, Sprint End Date, Sprint Start Date, Subtask, Summary, Time Spent
  • Supported fields in Notion: Title, Description, Created Date, Start and Due Date, Number, Single-Select, Multi-Select, Date, Assignee, URL, Email, Phone number, Checkbox, Creator, Relation.

Companies like yours trust Unito to sync their date

Unito is SOC 2 Type 2 certified and has strict security measures in place to protect your data. Unito’s team of engineers is constantly monitoring infrastructure to ward off threats, and an on-call engineer rotation means there’s always someone available to handle any issues. Here’s how companies like yours are using Unito’s Jira to Notion integration.

How to set up Unito’s Notion Jira integration

Here’s how easy it is to sync Jira projects with Notion.

Connect your Jira and Notion accounts to Unito. Pick the Jira project and Notion database you need to sync.

A screenshot of connecting tools in Unito, the first step to setting up a Notion to Jira integration.
If you can’t get to this stage, don’t hesitate to reach out to our live support staff, ready to jump in and help at a moment’s notice!

Pick a directional flow. This tells Unito where to create new Notion pages or Jira issues automatically based on your manual activity.

A screenshot of setting a flow direction from Jira to Notion in Unito to sync pages to issues

Want to sync everything or just a few work items? Use rules to filter out the Jira issues you don’t want synced.

A screenshot of Unito's rules screen in a flow between Jira and Notion.

Next, map your fields together so all your data goes to the right place. Unito can usually map most of these automatically, but it’s a good idea to review them.

A screenshot of Unito's field mapping screen syncing Jira data to Notion and vice versa

And that’s it! Now just launch your flow and watch as Jira issues are automatically synced to your Notion database through Unito’s integration.

What else can you sync with Notion?

You won’t just be able to sync Jira projects with Unito’s Notion integration. Here’s a guide to syncing Google Sheets spreadsheets with Notion databases.