How to Link Confluence With Jira 2026 Easily

Open Confluence and look at the "For you" landing page — if your site already has Jira software and business projects on the same Atlassian domain, they show up right there as recent projects with open work item counts. This is worth checking first, because if you can already see Jira projects like this from inside Confluence, the two products are on the same site and most of the plumbing is already in place. What's still missing is the formal application link that lets Confluence macros pull live Jira data and lets Jira issues reference Confluence pages directly, which is the piece the rest of this guide sets up.

The connection itself is configured from the Jira side. Go to your Jira admin settings and look under the Integrations section in the left sidebar — that's where Application links lives, alongside Compass and DVCS accounts.

This page lists every external application currently linked to your Jira instance, along with its status. If Confluence isn't listed yet, this is the screen you'll use to add it, and it's also where you'd come back to check or remove a link later if something needs to be reconfigured.

From the Application links page, start a new link and choose Direct application link rather than an application tunnel — a tunnel is only needed for self-managed instances sitting behind your own network. Paste in your Confluence site's URL (it follows the pattern yoursite.atlassian.net/wiki) into the Application URL field and continue. Jira validates the address and pulls basic details about the target application automatically, which is what makes this a few-minute setup rather than a manual credential exchange.

The next screen asks for an Application Name and Application Type — give it something your team will recognize later, since this name is what shows up in the Application links list going forward. Application Type defaults to Generic Application, which is correct for a standard Confluence connection; the optional fields below it for consumer key, shared secret, and service provider name are for advanced OAuth setups and can be left blank for a normal same-organization link. Continue through the confirmation and the link becomes active immediately, at which point Jira and Confluence can start referencing each other's content.

With the link active, open any Jira issue and use the Link option to attach a related Confluence page directly to it — search by page title and Jira pulls in the reference, showing it in the issue's Links section from then on. It works the other way too: inside a Confluence page you can insert a Jira issue or Jira report macro that displays live status, assignee, and progress for one issue or a whole filtered list, updating automatically as the ticket moves through your workflow instead of going stale like a plain hyperlink would.

The application link only creates the possibility of connection — someone still has to link the right page to the right issue for it to be useful. A simple team convention works best: every epic gets linked to its planning or requirements page the moment it's created, and every major spec change gets a note back on the epic. Do this consistently for a sprint or two and the pattern sticks, at which point new team members find both the ticket and its context in either tool without asking around.

Linked pages and issues don't self-correct when a project reorganizes, a page gets archived, or an epic gets split. Build a light review into your sprint retro or backlog grooming — a quick scan of whether the linked docs on your active epics still match what the team is actually building. It takes a few minutes and prevents the slow drift where the Confluence link on a two-year-old epic points at a spec nobody has opened since the project's first week.