How to Connect Confluence to Jira: A 7-Step Setup Guide
Need Jira issues and Confluence pages in sync? Follow this 7-step guide to connect confluence to jira. Read now to get started.
When Confluence pages and Jira work items don’t connect, project details become harder to find. Your team may copy issue updates into pages, miss changing priorities, or waste time checking which information is current.
That friction grows when people have different access permissions or your products run in separate environments. A link that works for one teammate may show an error to another, leaving everyone unsure whether the integration is set up correctly.
You can connect Confluence and Jira by confirming product access, establishing the right connection for your deployment, and linking a page to a Jira issue. Then test the links with the people who need them. Here’s a practical seven-step guide for cloud and self-managed teams, plus ways to troubleshoot common access and linking problems.
How to Connect Confluence to Jira in 7 Steps
The basic process is to make sure both products are available to your team, connect them where needed, and test a real page-to-issue link. The exact setup depends on whether you use Atlassian Cloud or self-managed Jira and Confluence.
-

1. Confirm access to both products
Check that you can sign in to Confluence and Jira, and confirm that the teammates who need the integration can access both products. An administrator may need to grant product access or adjust group membership.
For example, if a project coordinator can open a Confluence page but receives an access error on its Jira issue link, the connection may work while Jira permissions still need attention.
-
2. Identify your deployment type
Find out whether your team uses Atlassian Cloud or self-managed installations, such as Data Center. This determines whether your products may already be associated or need an administrator to configure an application link.
Cloud products in the same Atlassian site can often work together with little extra setup. Self-managed environments typically require more administrator involvement, especially when products run on different network addresses.
-
3. Check whether the products are already connected
Open a Confluence page and try adding a link to a Jira issue. Paste the issue URL into the page, or use the available Jira linking option. If the issue preview or link appears correctly, the products may already be connected.
If the page shows a plain URL or an error, don’t assume you need to rebuild the integration. First check the Jira address, your permissions, and whether the products are connected through the same site or an application link.
-
4. Connect the products if required
For self-managed Jira and Confluence, ask an administrator to configure an application link between the two product addresses. The administrator should use the supported authentication method for your versions and follow your organization’s security requirements.
For cloud products, an organization or site administrator should check the Atlassian administration settings and confirm both products belong to the expected site. Available settings can differ as Atlassian updates its interface.
-
5. Review authentication and user permissions
Check that the connection allows users to access the right Jira projects and Confluence spaces. On self-managed installations, the administrator should verify authentication settings and confirm that each product recognizes the intended user accounts.
Keep permissions limited to the access people need. Connecting products does not automatically mean every Confluence reader should be able to view every Jira issue.
-
6. Add a Jira issue link to a Confluence page
Edit a Confluence page, copy a Jira issue URL, and paste it where you want the reference. Depending on your setup, Confluence may display a smart link, an issue preview, or another linked representation.
For example, a release-planning page might link to the Jira issue for a feature, a bug, and a deployment task. Add a short explanation beside each link so readers know why it matters.
-
7. Test the connection with teammates
Publish or update the page, then ask a teammate with the intended access level to open each Jira link. Confirm that the right issue appears and that the person can view its details.
Test with more than one permission level when possible. A project lead and a guest contributor may see different results, even when both can open the Confluence page.
Cloud and Self-Managed Connections Work Differently
In Atlassian Cloud, the first thing to check is whether Jira and Confluence are associated with the same site. If they are, try linking an issue before looking for additional configuration. This simple test can save time when the integration is already available.
Self-managed installations need closer attention to product addresses, authentication, and network access. For instance, a Confluence server inside a restricted network may not be able to reach a Jira server hosted on a different internal address until an administrator configures the connection.
Here’s why: a product link only works when the products can communicate and the person opening it has permission to see the destination. Treat the connection and user access as two related checks, rather than one setting.
Choose the Right Jira Link for the Page
A Jira link can do more than point readers toward an issue. Depending on the Confluence version and configuration, you may be able to show a smart link, an issue preview, or a broader issue list on the page.
Use a single issue link when the page discusses one task, such as a defect affecting a release. Use a list or report when readers need to scan several issues, such as open work for a sprint or unresolved launch blockers.
For example, a support handover page could link directly to a high-priority issue and include a Jira issue list for related follow-up work. Keep the page focused so readers can understand the context without sorting through unrelated tasks.

Set Permissions Before Sharing Linked Pages
Confluence page access and Jira issue access are separate checks. A teammate may be able to read a page but lack permission to view the issue it links to. When that happens, the page can appear healthy while the link still fails for that person.
Before sharing a project page widely, ask someone with a typical team role to test it. If they can open the page but not its Jira links, check the relevant Jira project permissions, issue security settings, and user access.
Let me explain: the goal is to give people enough access to do their work without exposing unrelated project details. A quick permission check is particularly useful for pages shared with contractors, clients, or teams outside your project.
Verify the Connection and Troubleshoot Early
Test more than one kind of link after setup. Open a single issue, try a second issue from another project if appropriate, and check the result in a different browser session or account.
If a smart link fails, verify that the Jira URL is correct and that the viewer can access the issue directly. If the products are self-managed, ask an administrator to check the application link, authentication, network reachability, and product versions.
The best part? You can often narrow down the problem by testing the destination directly. If Jira opens normally but the Confluence link does not, investigate the product connection; if Jira itself denies access, review the user’s permissions first.
A Unified Alternative for Project Work and Team Knowledge: ONES.com
ONES.com brings project management and knowledge management together in one platform, powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

This option may suit teams that want project work and team knowledge in a coordinated environment rather than maintaining separate products and connections. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions. A free plan supports up to 30 seats.
Core Capabilities
- Scattered project context: ONES Project supports issue tracking and project workflows → teams can organize work in a dedicated project management product.
- Rigid processes: Custom workflows let teams shape issue states around their real approval or delivery process → work can move through steps that match team responsibilities.
- Inconsistent work details: Custom fields capture information such as release, risk, or request type → teams can make important issue details easier to review.
- Hard-to-track progress: Built-in reporting gives teams views of project activity → leads can monitor work without relying on a collection of extra reporting add-ons.
- Sprint coordination needs: Sprint management supports planning and tracking iterative work → teams can organize their delivery cycles within ONES Project.
- Repetitive task handling: Automation can handle selected routine actions → teams can reduce manual steps in recurring workflows.
- Knowledge separated from project work: ONES Wiki provides a knowledge management space alongside ONES Project → teams can choose paired products for connected work and reference material.
- Strict hosting requirements: Cloud, On-Premise, Private Cloud, and Air-gapped deployments provide different hosting choices → teams can evaluate an environment that fits their operational needs.
Application Scenarios
A software team could use ONES Project to manage issues, sprints, and releases, while maintaining process guidance in ONES Wiki. This can make it easier to keep project workflows and team knowledge within the same platform environment.
A team with strict network restrictions could assess the On-Premise, Private Cloud, or Air-gapped deployment options. Teams can review the available deployment and security requirements before deciding whether the products fit their environment.
Common Connection Challenges and Practical Fixes
- The Jira link opens an access error: The viewer may not have permission to see the Jira project or issue. Check their product access and the issue’s security settings, then test the link again with their account.
- The issue appears as a plain URL: The products may not be connected, or the link may not be recognized in the current setup. Confirm the Jira address and product association, then try adding the link again.
- The connection works for administrators only: Administrative access does not guarantee that other teammates have the same permissions. Test with a regular team account and review access in both products.
- A self-managed connection cannot reach the other product: The products may not be able to communicate over the network, or authentication may be misconfigured. Ask an administrator to check the product addresses, network access, and application link settings.
- People cannot tell what a link is for: A bare issue link provides little context. Add a brief explanation, such as “Track the login defect for the mobile release,” beside the link on the Confluence page.
FAQs About Linking Confluence and Jira
Do I need an administrator to connect Confluence to Jira?
You may not need administrator help if both cloud products already work together and you only need to add an issue link to a page. An administrator is more likely to be needed when the products are self-managed, belong to separate sites, or require application-link and authentication changes. If you can’t see the relevant settings, ask your Atlassian administrator to check the connection and your product access.
Can I link a Jira issue from a Confluence page?
Yes. In many setups, you can paste a Jira issue URL into a Confluence page or use the available Jira linking option. The page may display a smart link, preview, or another linked format depending on your product version and settings. Make sure readers also have permission to view the Jira issue, or they may see an access error.
Why can one teammate open a Jira link while another cannot?
Confluence page permissions and Jira issue permissions are separate. One teammate may have access to the Confluence space but not the Jira project or a restricted issue. Check the affected person’s product access, project permissions, and issue security settings. Then test the link while signed in as that person to confirm the change resolved the problem.
Does connecting Jira and Confluence copy Jira issue details into a page?
A link or smart link lets readers move from a Confluence page to a Jira issue, and some configurations show an issue preview. That does not necessarily mean the issue’s full details have been copied into the page. If the page needs specific context, add a short explanation and link to the Jira issue so readers can check its current details.
Conclusion
Connecting Confluence and Jira usually comes down to three checks: confirm product access, establish the right connection for your deployment, and test a real issue link with teammates. Pay particular attention to permissions, since access to a Confluence page does not automatically provide access to its Jira links.
If a link fails, test the Jira issue directly before changing integration settings. That quick check can show whether the problem is the product connection or an individual’s access. With a tested link and a little context on the page, your team can keep project information easier to follow and act on.