HOW TO

You’re juggling Jira for project tracking and Confluence for documentation — but your team keeps switching tabs, losing context, and making decisions on stale data.

Sound familiar?

The fix is simpler than you think. Embedding your Jira dashboard directly into Confluence means everyone sees live project data without leaving the page they’re already on. No more “what’s the current sprint status?” messages. No more hunting for the right board.

Teams using integrated Atlassian tools report up to 30% faster project delivery compared to teams running disconnected tools. The data you need is already in Jira. This guide shows you exactly how to bring it into Confluence — and keep it there.

What It Means to Embed a Jira Dashboard in Confluence

Confluence and Jira are built by Atlassian. They’re designed to work together. Embedding a Jira dashboard means you’re pulling live Jira data — sprint progress, issue counts, burndown charts, open blockers — directly into a Confluence page using a macro.

When someone visits that page, they see real-time data from your Jira project. No export. No screenshot. No manual update.

Why this matters:

• 83% of employees lose time every day switching between apps, according to research by Asana
• Teams using Confluence and Jira together see a 25% reduction in status meetings, because the information is always visible
• Projects with a single source of truth for reporting are 2x more likely to finish on time and on budget

The integration isn’t just a convenience feature. It’s the difference between a team that’s aligned and a team that’s always playing catch-up.

Before You Start: What You’ll Need

Before embedding, make sure these boxes are checked:

You need a Confluence Cloud or Data Center instance (Server has limited macro support). You need a Jira project with at least one dashboard already configured. Your Confluence and Jira instances need to be linked at the admin level. And you need View permissions on the Jira project you’re trying to embed.

If you’re on Confluence Cloud with Jira Cloud — and both are under the same Atlassian organization — the integration is usually active by default. For Data Center setups, your admin may need to configure the application link first.

How to Embed a Jira Dashboard in Confluence: Step by Step

Connect Jira and Confluence (Admin Step)

This step is done once by your Confluence administrator. If it’s already done, skip ahead.

Go to Confluence Settings → Application Links. Click Create link and enter your Jira instance URL. Follow the OAuth prompts to authorize the connection. Once confirmed, Confluence can pull data directly from Jira.

Approximately 68% of Atlassian customers use both Jira and Confluence together — but a significant portion never complete the application link, which blocks all macro functionality. Check with your admin first if macros aren’t showing up.

Open the Confluence Page You Want to Edit

Navigate to the Confluence page where you want the Jira dashboard to appear. Click Edit (the pencil icon) to enter edit mode.

This works on new pages and existing pages alike. Many teams create a dedicated “Project Hub” page in Confluence and embed all their Jira data there — giving stakeholders a single destination for status updates.

Insert the Jira Dashboard Macro

Click into the body of the page where you want the dashboard to appear. Then:

Press “/” (forward slash) to open the macro menu. Type “Jira” in the search bar. You’ll see several options — select Jira Dashboard or Jira Chart, depending on what you’re embedding.

If you don’t see the Jira macro, it means either the application link isn’t set up, or the macro has been disabled by your Confluence admin. Teams on Confluence Free plans have limited macro access.

Configure the Macro

Once you select the Jira Dashboard macro, a configuration panel opens. Here’s what to fill in:

Dashboard ID: This is the unique ID from your Jira dashboard URL. Open your Jira dashboard, look at the URL bar — you’ll see something like …rapidView=12 or …dashboardId=10200. Copy that number.

Display options: Choose whether to show the full dashboard or just specific gadgets. You can also set the height and width of the embedded frame.

Refresh interval: Set how often the data updates. For active sprints, a 15–30 minute refresh keeps data current without hammering your Jira instance.

Publish and Verify

Click Save or Publish on your Confluence page. The embedded dashboard will load within the page — pulling live data from Jira.

Test it by checking that:

• The correct dashboard is displayed
• Data matches what you see when you open Jira directly
• The embedded view refreshes correctly when sprint data changes

If you see a blank frame or a permissions error, check that you have View access on the Jira project, and that the application link is active.

Embedding Jira Filters and Reports (Not Just Dashboards)

Dashboards aren’t the only thing you can embed. Confluence supports several Jira macro types that serve different reporting needs.

Jira Issues Macro — Pulls a live list of issues based on any JQL (Jira Query Language) filter. Example: embed all open blockers for the current sprint directly on your project status page.

Jira Chart Macro — Embeds visual charts like pie charts or two-dimensional grids. Useful for embedding issue-type breakdowns or priority distributions.

Jira Roadmap Macro — If you’re using Jira’s Roadmap feature (available on Standard and Premium plans), you can embed it into Confluence to give stakeholders a high-level timeline view.

Teams that use visual reporting tools in project management see 43% higher stakeholder satisfaction scores, according to PMI’s Pulse of the Profession report. Embedding charts rather than raw data lists makes information instantly digestible.

Common Issues and How to Fix Them

The Macro Shows a Blank Frame

This almost always comes down to permissions. Confirm that the user viewing the Confluence page has access to the linked Jira project. Guest Confluence users who don’t have Jira licenses will often see blank embeds.

The Dashboard ID Isn’t Working

Jira Classic and Jira Next-Gen projects use different URL structures. For team-managed projects, look for ?rapidView= in the URL. For company-managed projects, it may be ?dashboardId=. Copy the correct number for your project type.

The Application Link Is Broken

Atlassian updates can sometimes reset application link OAuth tokens. Go to Confluence Settings → Application Links, find your Jira connection, and click Edit to reauthorize. This fixes blank macros in bulk.

Data Isn’t Refreshing

If your embedded dashboard shows stale data, check the macro’s refresh interval setting. Also confirm that your Jira instance is reachable — network issues, VPN configurations, and firewall rules can block the data pull even when the link appears active.

Over 60% of Confluence users report encountering at least one macro configuration issue in their first month of use. Most are fixed in under five minutes once you know where to look.

Best Practices for Jira-Confluence Integration

Create a dedicated project hub page. Instead of scattering Jira embeds across dozens of pages, build one “Project Hub” in Confluence per project. Embed the sprint dashboard, key issue filters, and roadmap on this single page. Teams with centralized project pages spend 40% less time in status meetings.

Use page restrictions wisely. Embedding a Jira dashboard in a public Confluence space can expose project data to people who shouldn’t see it. Set appropriate Confluence page restrictions to match your Jira project permissions.

Combine macros with Confluence content. The most effective project pages don’t just embed raw Jira data — they pair it with context. Add a brief sprint summary above the embedded dashboard, and a decisions section below. This turns a data display into a genuine decision-making hub.

Label your embedded views clearly. A Jira chart with no context is confusing. Add a heading above each macro that tells readers exactly what they’re looking at: “Current Sprint Burndown,” “Open Blockers by Assignee,” or “Q2 Roadmap Overview.”

Review permissions after team changes. When someone joins or leaves the team, their Confluence and Jira permissions need to stay in sync. Mismatched permissions are the number one cause of “blank embed” complaints.

Why Teams With Better Visibility Still Struggle to Generate Pipeline

Here’s something that doesn’t get talked about enough.

You can have perfect project visibility — every sprint tracked, every Confluence page up to date, every dashboard live and accurate. And still struggle to grow.

Because visibility inside the team is not the same as pipeline from the outside.

The teams that scale aren’t just organized. They’re also running outbound systems that consistently bring qualified conversations in. LinkedIn outreach. Cold email sequences. Targeting the exact decision-makers who need what you build.

Most teams treat lead generation as something they’ll “get to.” They optimize tools. They document processes. They build beautiful Confluence pages.

And then wonder why the calendar isn’t full.

Conclusion

Embedding a Jira dashboard in Confluence is one of the highest-leverage changes you can make to your team’s information flow. It removes the friction of tab-switching, keeps stakeholders aligned on live data, and turns your Confluence pages from static documentation into active project hubs.

The steps are straightforward: confirm your application link is active, insert the Jira macro, enter your dashboard ID, configure your display settings, and publish. Fix permissions issues before assuming it’s a technical problem — they’re the cause of the vast majority of blank embeds.

Teams using integrated Atlassian environments report 25–30% improvements in delivery speed and stakeholder alignment. The setup takes minutes. The compounding benefit is ongoing.

And once your internal operations are running smoothly, the next step is making sure your external pipeline is just as systematic. That’s exactly what SalesSo is built for — targeting the right people, designing campaigns that get responses, and scaling what works until your calendar is full.