What we do
Tools
Industries
Department
How we workLet's talk →
Home/Jira/Jira and Confluence
Jira + Confluence

Jira and Confluence: How to Link Them, and Where the Link Stops

Jira tracks the work. Confluence holds the pages about it: specs, meeting notes, release notes. On Atlassian Cloud the two already know about each other, so linking them is a few clicks. Here are those clicks, which feature fits which job, and what still happens by hand once the people who need the update don't use Atlassian.

Put Jira work on a Confluence page

Quickest: paste a Jira link onto the page. A /browse/ link shows one work item with its live status. A saved filter or JQL search link shows a list of matching items.

From the editor: insert the Jira work item element, then pick a project and search, or type a JQL query.

Insert Jira work item

Make a ticket from page text: highlight the text and use the toolbar. The highlighted words become the summary, and the new item is linked back to the page.

Highlight text + Jira work item Create single work item

Why the words don't match older guides: Jira Cloud now calls issues work items. Same thing, new name. The REST API still says issue.

Which Jira feature in Confluence fits the job

All of these work inside Atlassian Cloud without add-ons. Readers only see the Jira details their own Jira permissions allow.

What you want Use this Good to know
Live status of a few tickets inside a spec or plan A pasted Jira link, or the Jira work items element with a JQL query Adjust which columns show and how many items appear. A Jira links button at the top of the page lets readers jump to the linked work.
A requirements doc that turns into tickets The Product requirements template, which has a placeholder to link or create the Jira epic Highlight text in a table on a published page to create several work items at once, one per row.
A change log or status report for a release The Jira Report blueprint (Change Log or Status report), or the Jira Chart macro Charts come as pie, created vs resolved, and two-dimensional. Good for a sprint review, less so for customers.
Sprint meeting notes and retros Meeting notes created from Jira for a sprint, and the Retrospective template The notes page is linked to the sprint automatically, so it's findable from Jira later.
A knowledge base for a service desk A Confluence space connected to Jira Service Management as its knowledge base Customers without a Confluence license can read linked articles through the help portal, with limited access.

Jira or Confluence: which one does what

Jira

Work that moves

  • Each item is a piece of work with an owner, a status and a workflow.
  • Built for boards, sprints, filters and reports on what got done.
  • Answers "who is doing this, and is it finished?"
Confluence

Writing that stays

  • Pages and live docs: specs, decisions, how-tos, meeting notes.
  • Organized into spaces and page trees, edited together.
  • Answers "what are we building, and why did we decide that?"

Neither needs the other. Jira alone is fine for a team that tracks work and keeps few documents. Confluence earns its place once specs and decisions need to live somewhere everyone can find them, next to the tickets that carry them out.

Where the Jira and Confluence link runs out

Everything above stays inside Atlassian. These are the copy-and-paste jobs that start where your Atlassian users stop.

Release notes stop at a Confluence page

How you'll know: The release page is done, then someone rewrites it for the public changelog, the help center and the customer email.

Fix: Jira automation can publish a Confluence page when a version is released. To go further, one approved set of notes can be posted to your website, help center and email tool without retyping. See Jira automation for the in-Jira half.

Clients and sales can't see status without a login

How you'll know: Account managers ask engineers in chat whether a client's request has shipped, because the answer lives on a page they can't open.

Fix: Copy the status of the linked work items onto the client's CRM record, or a page they can open, and keep it updated when the item moves.

The help center article stays wrong after the fix ships

How you'll know: Your knowledge base lives outside Confluence, and nobody remembers to update the article once the bug fix goes out.

Fix: When a linked work item is marked done, open a review task on the affected article, or update it directly from the approved text.

Exported pages are frozen in time

How you'll know: A PDF or Word export of the status page goes to a client and is out of date by Friday.

Fix: Send a link to something that stays live, or regenerate the report on a schedule and send the new copy each time.

Questions people ask

Are Jira and Confluence the same thing?

No. They're two separate Atlassian products that are built to work together. Jira tracks issues, now called work items, as they move through a workflow. Confluence is for documentation: pages, wikis and meeting notes. Many teams run both, but neither requires the other.

Do I need both Jira and Confluence?

Not necessarily. Plenty of teams run Jira alone. Confluence is worth adding once you need shared, structured documents, like requirements, decisions or a team wiki, linked to the work tracked in Jira.

How do I link a Jira issue to a Confluence page?

Paste the Jira issue's link onto the Confluence page, or use Insert, then Jira work item, and search for it. To go the other way, highlight text on the page and create a Jira work item from it. Pages that link to an item also show up on that item in Jira, so the link works from both sides.

What's the difference between Jira and Confluence?

Jira is built around separate pieces of work moving through statuses, with owners and due dates. Confluence is built around writing and organizing longer content that refers to that work. In short: Jira says what's being done, Confluence says what and why.

Can Jira automation create a Confluence page?

Yes. Jira automation has a Confluence action that publishes a new page in a space you choose, for example when a version is released. For pages filled with detailed Jira data, teams often call the Confluence REST API from a rule instead. Our Jira API page covers the API side.

Does this work on Jira and Confluence Data Center?

Yes, the macros and linking exist on Data Center too, but an administrator first connects the two products with an application link. The renamed "work items" wording is a Cloud change, so Data Center screens still say issues.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.