- Yes, but only after one condition is met
- What the pairing lets you do
- Getting Jira work onto a Confluence page
- Linking a page to an epic from Jira
- Two limits worth knowing before you rely on it
- Where the pairing earns its keep
- Other tools that connect to Jira
- My verdict for a team already on Jira
- Frequently asked questions
Yes, Confluence integrates with Jira. Both are Atlassian products and connect natively once your sites are linked. You can embed Jira work items on a Confluence page with the Jira work items macro, create work items from the editor and link Confluence pages to work items in Jira. It isn't a two-way content sync.
Yes, but only after one condition is met
Confluence and Jira are both Atlassian products, and they're built to work together. Nothing happens on its own, though. Every feature below depends on your Confluence site and your Jira site being connected. If you already use Jira and want to add Confluence, Atlassian says to go to Switch sites or apps, then More Atlassian apps.
One wording note before we start: Atlassian now calls Jira tickets work items. Older guides say issues. It's the same thing.
What the pairing lets you do
| In Confluence | In Jira |
|---|---|
| Show a list, a single work item or just a count with the Jira work items macro | See automatic links to any Confluence page that mentions a work item in the macro |
| Create a new Jira work item from the editor without leaving the page | Link an existing Confluence page to a parent-level work item, an epic by default in software spaces |
| Show Jira gadgets on a page | Embed a Confluence activity stream or page on a Jira dashboard |
Getting Jira work onto a Confluence page
There are three ways in. Choose Jira work items from the toolbar, type /jira while editing, or paste a Jira search filter URL into the page. Pasting a work item URL, a search or filter URL, or the URL of an XML search view auto-converts it into the macro, which is the quickest route of all.
Inside the macro you can refine the list by keywords, filters or JQL. You can show one work item, a chosen subset or just a count, using Total work item count under Display options. The count links back to the search in Jira, which makes it handy for a status page that says how many bugs are open without listing them all.
Whenever a work item is mentioned on a page through the macro, Jira creates a link to that page automatically, so the developer looking at the ticket can find the spec.
Linking a page to an epic from Jira
From the Jira side, open the epic or other parent-level work item, select + to add related work, select Page, then Link page. That connects your requirements doc or meeting notes to the work they describe.
Team Calendars for Confluence also surfaces Jira versions, work items and sprints, with JQL support and a timeline view that looks about 3 months ahead.
Two limits worth knowing before you rely on it
Atlassian Support is clear that the integration isn't automatic until the two sites are linked: the Jira macro and the page-to-epic link both depend on it. And a single work item can hold a maximum of 2,000 links in total, counting web links, Confluence page links, links to work items on a different Jira instance and links to other Atlassian apps. Most teams will never reach it, but a long-running epic that collects every meeting note might.
It's also worth being clear about what this isn't. The macro displays Jira data on a page and links the two together. It doesn't sync page content back into Jira or keep two copies of a document in step.
Where the pairing earns its keep
Atlassian's own examples are good ones: write up a workaround for a bug as a knowledge base article, write a product requirements document for a feature, or document a work item with the team in Confluence. In each case the page holds the thinking and Jira holds the tasks.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Other tools that connect to Jira
Notion's Jira sync creates connected databases for selected Jira Cloud spaces and their work items, and the synced properties are read-only in Notion. Linear's Jira integration syncs issues with Jira and needs a Jira user with the global ADMINISTER permission to install the webhooks. If you're open to replacing Jira altogether, my list of Jira alternatives covers the field, and my guide to wiki software for teams does the same for Confluence.
My verdict for a team already on Jira
If Jira runs your work, adding Confluence is the natural home for the documents around it. Link the sites first, get everyone pasting Jira URLs into pages so the macro does the work, and link every spec to its epic. Just don't expect the page and the ticket to update each other. They point at each other, and that's what they're for.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Confluence integrate with Jira?
Yes. Once your Jira site is linked to Confluence you can embed work items on pages, create work items from the editor and link pages to work items.
How do I show Jira tickets on a Confluence page?
Edit the page, type /jira or use the toolbar, choose Jira work items, then search by keyword, filter or JQL.
Can I link a Confluence page to a Jira epic?
Yes. Open the epic, select + to add related work, select Page, then Link page.
Can I show only a count of Jira items?
Yes. Choose Total work item count under Display options in the macro.
Is there a limit on links per work item?
Atlassian states up to 2,000 links per work item, including web links and Confluence page links.
