Integrating JIRA Agile with your Confluence applications

If you have JIRAJIRA AgileConfluence and Confluence Team Calendars, you can use them together to build stronger user stories and better plan for sprints or releases, while streamlining your team's work. Create meeting notes on the fly, wrap up a sprint with a retrospective report, and more.

This page highlights where JIRA-JIRA Agile-Confluence-Team Calendars features can help your team.

On this page:

Making the integration work

We recommend that you use the latest versions of the Atlassian products. If you are using JIRA Cloud and Confluence Cloud, it's all done for you — you will already have the latest versions. If you are installing everything yourself, here are the minimum versions of the products that you'll need:

Product Version Installation guide
JIRA See the required JIRA versions  for your JIRA Agile version Installing JIRA
JIRA Agile 6.3.5 or later (note, JIRA Agile is a paid add-on) Installing JIRA Agile
Confluence 5.4 or later Installing Confluence
Team Calendars 4.2.1.2 or later (note, Team Calendars is a paid add-on) Installing Team Calendars

Once you have installed the products, you need to configure them as described below, to enable the features described on this page:

Install it yourself:

  • Your JIRA instance must be linked to your Confluence site, and your JIRA project must be linked to a Confluence space. See Linking to Another Application (JIRA documentation). If you have JIRA linked to multiple Confluence sites, the primary link will be used for the features described on this page.
  • If you also want to use Confluence Team Calendars with JIRA Agile, then your Confluence site must be linked to your JIRA site, as described in the point above.
    Note, Confluence Team Calendars is a commercial add-on for Confluence. 
  • JIRA permissions —  Your users need to have the following permissions:
    • Creating/Linking pages to an epic: Requires 'Edit Issues' permission.
    • Creating/Linking pages to an sprint/sprint report: Requires 'Project Admin' permission.
  • Confluence permissions —  Your users need to have the 'Add Page' permission for the appropriate space, if you want them to create Confluence pages via JIRA Agile.

JIRA Cloud + Confluence Cloud:

  • JIRA permissions —  Your users need to have the following permissions:
    • Creating/Linking pages to an epic: Requires 'Edit Issues' permission.
    • Creating/Linking pages to an sprint/sprint report: Requires 'Project Admin' permission.
  • Confluence permissions —  Your users need to have the 'Add Page' permission for the appropriate space, if you want them to create Confluence pages via JIRA Agile.

Planning epics

  • Planning an epic? Perhaps you have some lovingly hand-crafted specifications written up in Confluence. It's easy to link to a Confluence page from an epic in JIRA Agile. Anyone viewing the epic will be able to see the linked pages.
    You can also create Confluence pages (using the Product Requirement blueprint) via the epic.
    Learn more...

Planning sprints

  • Confluence Team Calendars acts as your single source of truth for managing team leave, tracking projects, and planning events. If you have Team Calendars installed in Confluence, planning your sprints around leave and events is even easier. Add a JIRA Agile Sprints event to your team's calendar in Confluence, and as you plan your sprints, you will be able to see whether team leave or events will impact your work. 
    Learn more...
     

Managing sprints

  • You are getting your sprint underway. Ideas are being discussed in the planning session. Instead of jotting the notes down on paper, you can simply create a meeting notes page in Confluence (using the Meeting Notes blueprint), directly from the sprint in JIRA Agile.
    You can also link your sprint to existing pages in Confluence.
    Learn more...

  • The sprint is wrapping up. JIRA Agile has generated a beautiful sprint report and your team holds a retrospective to discuss the sprint. You can easily create a page for your retrospective in Confluence, via your sprint report in JIRA Agile.
    You can also link your sprint report to existing pages in Confluence.
    Learn more...

Managing releases

  • The release is underway. Provide your stakeholders with updates on how the release is going, by creating JIRA status reports in Confluence. The JIRA status report provides a snapshot of the release at a point in time. Stakeholders can monitor progress, even if they don't have access to JIRA.
    Learn more...

  • You have just wrapped up a release. Notify stakeholders of exactly what changed between releases by providing them with a JIRA change report in Confluence. You can also use the change report to let everyone know what your team has accomplished, even people who don't have access to JIRA.
    Learn more...

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport