How to Access Confluence from Jira (Step-by-Step)

You’re deep in a Jira ticket. There’s a Confluence page with all the context you need — requirements, decisions, team notes — and you can’t figure out how to get there without opening a new tab and hunting through a dozen spaces.

Sound familiar?

You’re not alone. Teams lose an average of 4.8 hours per week just searching for information scattered across tools. That’s over 200 hours a year per person — not shipping, not selling, not closing. Just searching.

The Jira–Confluence integration is built to eliminate that. When it’s set up right, your docs, decisions, and project context live right inside your Jira workflow. This guide shows you exactly how to access Confluence from Jira — whether you’re using Jira Cloud, Jira Software, or Jira Service Management.

Why Jira and Confluence Work Better Together

Atlassian built both tools to work as a connected system, not as siloed apps. Here’s why the integration matters:

83% of employees rely on technology to collaborate, yet research shows knowledge workers switch between apps over 9 times per hour, breaking focus and slowing execution. Linking Jira and Confluence collapses that gap.

When connected:

• Jira issues can link directly to Confluence pages (specs, runbooks, meeting notes)
• Confluence pages can embed live Jira issue lists and roadmaps
• Teams can create Confluence pages directly from a Jira project sidebar
• Sprint retrospectives, product requirements, and release notes all live where the work happens

Teams using integrated Atlassian tools report up to 25% faster project delivery compared to teams using disconnected documentation and task tools.

What You Need Before You Start

Before accessing Confluence from Jira, make sure:

• You have an active Jira Cloud or Jira Software account
• Your organization also has a Confluence Cloud account (same Atlassian organization preferred)
• You have at least View permissions on the relevant Confluence spaces
• Your Jira and Confluence instances are linked (either same site or cross-site linking enabled by your admin)

If you’re on Jira Data Center or Server, the process is slightly different — covered in its own section below.

How to Access Confluence from Jira Cloud

This is the most common setup. Follow these steps:

Step 1 — Open your Jira project

Go to your Jira project. In the left sidebar, look for the Project Pages section. If your admin has connected Confluence, you’ll see a Pages item in the sidebar directly under your project navigation.

Step 2 — Click “Pages” in the sidebar

Clicking Pages opens the linked Confluence space right inside Jira — no tab switching. From here you can browse, search, and open any Confluence page tied to that project.

Step 3 — Access Confluence from a specific Jira issue

Open any Jira issue. Scroll to the details panel on the right. Under Confluence pages, you’ll see any pages already linked to that issue. Click any page title to open it.

To link a new Confluence page to the issue:

• Click Link (or the + icon next to Confluence pages)
• Select Confluence Page
• Search for the page by title or paste the URL
• Click Save

Step 4 — Create a new Confluence page from Jira

Inside the Pages sidebar in your Jira project:

• Click Create page
• Choose a Confluence space
• Your new page opens in Confluence with the project already associated

This is the fastest way to document decisions, specs, or post-mortems without ever leaving your Jira workflow.

How to Access Confluence from Jira Software (Board View)

If you’re working from a Scrum or Kanban board:

• Click the Project settings (bottom left of your board sidebar)
• Under Apps, look for Confluence
• If a space is linked, you’ll see a direct shortcut to your project’s Confluence pages
• You can also open any issue card on the board → scroll to the Confluence section in the right panel → access or add linked pages

Pro tip: Pin your most-used Confluence spaces to your Jira project sidebar for one-click access. This alone saves teams 20–30 minutes of navigation per day.

How to Access Confluence from Jira Service Management

For support and IT teams using Jira Service Management (JSM):

• Open a request or ticket
• In the right-hand panel, find the Confluence section under Linked pages
• Add knowledge base articles directly to tickets to share with customers or internal agents
• Agents can create new Confluence KB articles from inside a ticket — useful for documenting resolutions for future reference

JSM’s integration with Confluence is especially powerful for knowledge base management. Organizations with integrated IT documentation resolve tickets 30% faster than those without centralized knowledge.

How to Set Up Cross-Site Confluence Linking in Jira

If your Jira and Confluence are on different Atlassian sites (e.g., separate URLs), your admin needs to enable cross-site app linking:

1. Go to Jira Admin Settings → Applications → Application Links
2. Enter your Confluence site URL
3. Authenticate and authorize the connection
4. Once linked, all users can access Confluence pages from Jira issues

This is a one-time admin task. Once done, the Confluence panel appears in every Jira issue automatically.

How to Access Confluence from Jira Data Center / Server

For on-premise setups:

• Navigate to Jira Administration → Add-ons (or Apps)
• Search for Confluence in the Atlassian Marketplace
• Install the Jira–Confluence integration plugin if not already installed
• Go to Administration → Application Links → add your Confluence server URL
• Authenticate with admin credentials on both sides

Once configured, the workflow mirrors Jira Cloud: linked pages appear in issue panels and the project sidebar shows a Pages section connected to your Confluence instance.

Note: Atlassian has announced end-of-life for Server products. As of February 2024, 15% of enterprise Atlassian customers have migrated to Data Center or Cloud. If you’re still on Server, the migration clock is ticking.

Navigating Confluence Spaces Directly from Jira

Once linked, here’s how to move fluidly between the two:

From a Jira issue: Click any linked Confluence page title → opens in the same browser tab or a new one (based on your settings)

From the project sidebar: Click Pages → browse your space hierarchy, search for content, or create new pages

From the Jira top navigation: Click the Apps menu (the grid icon) → select Confluence to open your full Confluence home

From Jira boards: Use the keyboard shortcut G then P to jump to project pages in many Jira configurations

Common Problems and How to Fix Them

“I don’t see a Pages section in my Jira sidebar”

This means either (a) your Confluence instance isn’t linked yet, or (b) the integration is disabled for your project. Ask your Jira admin to link the Confluence space in Project Settings → Apps.

“I can see the Confluence panel but no pages appear”

Check your Confluence space permissions. You may have Jira access but not Confluence view permissions for that specific space.

“The Confluence link is broken or shows an error”

The application link may have expired or needs reauthorization. An admin needs to go to Application Links and re-authenticate.

“I can access Confluence pages but can’t edit them”

You have View but not Edit permissions in Confluence. Ask your Confluence space admin to update your role.

Tips to Get More Out of the Jira–Confluence Integration

Embed live Jira boards in Confluence — use the Jira Issues macro inside any Confluence page to display a live view of your sprint, backlog, or filtered issue list

Use page blueprints — Confluence has built-in templates for product requirements, retrospectives, and meeting notes that auto-link to Jira projects

Track decisions in Confluence, execute in Jira — keep your Confluence pages as the single source of truth for why decisions were made, and Jira issues for what needs doing

Set up Confluence page watches — get notified when linked docs change so Jira task owners stay in sync with evolving requirements

Teams that consistently link documentation to issues report 40% fewer miscommunication-related delays on projects, according to Atlassian’s own productivity research.

The Bigger Picture: Connected Tools vs. Disconnected Outreach

Here’s what most teams miss: internal productivity tools like Jira and Confluence are only half the equation. Your internal operations can be perfectly synchronized — and your external pipeline still stagnates if outreach is manual, scattered, or guesswork.

76% of B2B buyers now expect a personalized, research-backed approach before they’ll engage. If your sales team is still copying and pasting prospects into spreadsheets, that gap between internal efficiency and external results will cost you pipeline.

The same logic that makes Jira–Confluence integration powerful — systematic connection, structured targeting, seamless execution — applies to outbound lead generation. The teams winning pipeline in 2025 aren’t working harder. They’re running systems.