If you have JIRA, JIRA Agile, Confluence 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.
We recommend that you use the latest versions of the Atlassian products. If you are using Atlassian OnDemand, 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:
|JIRA||See the required JIRA versions for your JIRA Agile version||Getting Agile Ready with your Atlassian applications|
|JIRA Agile||6.3.5 or later||Installing JIRA Agile|
|Confluence||5.4 or later||Installing Confluence|
|Team Calendars||18.104.22.168 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:
- 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.
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.
- 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.
- 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.
- 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.
- 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.