There is no native way to export a list of Jira issues into OneNote, and the three DIY routes people try — copy-paste, Excel/PDF export, and a Zapier trigger — each break in a different way. Copy-paste lost the button it depended on, exports produce a dead file that’s stale the next morning, and automation tools append one note per issue instead of building a table. If you want a live, clickable list of your Jira issues sitting in OneNote, you have to point something at a saved filter and let it write the table for you.

Can you export Jira issues to OneNote at all?

Not cleanly. This is a real, recurring ask: in the Atlassian Community, a user asked to “export a list of our open and in progress Jira issues into a table or list in OneNote on a weekly basis.” That’s a normal reporting need. There’s just no button for it. Jira doesn’t export to OneNote, and there’s no native Jira-to-OneNote connector, so every answer in that thread is a workaround. Below is what each one actually does.

Route 1: copy-paste the issue list into OneNote

The old advice was to build a filter, switch to list view, configure your columns, select the rows, and paste them into OneNote with “Merge Formatting” so the issue keys stayed clickable. It worked well when it worked.

It doesn’t reliably work now. In the same thread, after the original poster couldn’t find a copy option, another user confirmed why: “There used to be a lovely Copy button on the bottom after you selected issues” but “Atlassian seems to have removed this” (Atlassian Community). So the route that gave you a clean, clickable table lost the one control it relied on. Even when a manual selection does paste, it’s a one-time copy: it captures the list as it looks right now and never updates.

Route 2: export to Excel or PDF, then email it to OneNote

The next fallback is to run a JQL query and export the results. Jira Cloud does support this: you can export your issues to CSV from the Issue Navigator (Atlassian Support), and from there you can open it in Excel, save a PDF, and forward it into a OneNote notebook.

Two problems. First, it’s a dead file. The moment you export, you’ve frozen the query. By the next standup the statuses have changed and your OneNote page is showing last week’s board. Second, there’s a ceiling: Jira Cloud’s asynchronous export is capped at 10,000 work items from the Issue Navigator (Atlassian Support). For a weekly status list that’s fine on size but wrong on freshness. You wanted a report, and you got a screenshot in file form.

Route 3: automate it with Zapier

The instinct is to skip the manual step and wire Jira to OneNote with an automation tool. Zapier does connect the two: it can trigger on a new Jira issue and, on the OneNote side, “create a new note” or “append content to the end of a note” (Zapier).

But look at what that actually builds. Each new issue fires the trigger and adds a note, or a line appended to a note. You don’t get one table you can scan. You get a growing pile of one-off entries, and nothing goes back and updates a row when an issue changes status or closes. The trigger fires forward on creation; it doesn’t maintain a view. That’s the opposite of what “export my open and in-progress issues as a table” means.

Is there a Jira–OneNote integration, or only an export?

If exporting a file feels too manual, the natural next search is “jira onenote integration” — and you’ll hit a wall of no-code connectors: Zapier, Latenode, Onlizer, and a dozen others. They call themselves integrations, but under the hood they’re the same trigger-and-action automation as Route 3. Latenode, for instance, lists triggers like “Issue Created” and “Issue Updated” wired to actions like “Append Note” and “Create Note” in OneNote (Latenode) — one note per event, not one table.

So the distinction that matters isn’t export vs integration, it’s snapshot vs live. An export writes your issues once. An iPaaS “integration” writes a new note every time an event fires. Neither maintains a single table that reflects Jira’s current state. A real integration would treat OneNote as the destination for a query: point it at a saved JQL filter and keep the results as one table that refreshes on a schedule. That’s the scheduled, auto-refreshing report the connectors can’t build — and it’s the version most people typing “jira onenote integration” are actually after.

What actually gives you a live table in OneNote?

The thing all three routes are missing: a table that reads from a saved Jira filter and refreshes, so it shows the current state instead of a frozen one. That means starting from JQL (the query is the source of truth), writing a real table into OneNote (sortable rows, clickable issue keys, not a pasted image), and refreshing it on a schedule so the weekly report writes itself.

That’s exactly what we built OneNote Reports for Jira to do. You point it at a JQL filter, it writes a clean, clickable issue table straight into your OneNote notebook, and it keeps that table current instead of leaving you a dead export. The stakeholders who live in OneNote and never open Jira get the list they actually asked for, in the tool they already have open, and it’s right every time they look at it.