Confluence 5.6 has reached end of life
Check out the [latest version] of the documentation
By using Confluence and JIRA Agile together, you can unleash the potential in your development team. This page provides some suggestions for how you can get the most of Confluence and JIRA Agile.
The features described on this page require JIRA 6.1.3 and JIRA Agile 6.3.5 and later.
Confluence is the perfect place to start defining your requirements. Here's how you can use Confluence features to support this process:
The tight integration between Confluence and JIRA mean that you can easily access JIRA issues from the Confluence page, and see their status at a glance, and from within JIRA you can see links to related Confluence pages. All the information you need is never more than a few clicks away.
Often there is a lot of material in Confluence that provides useful context for your team during a sprint. These might be requirements documents, designs, technical specifications, customer research and more. By linking these pages to epics, you make them easy for your team to access during the sprint.
Here's how you can use Confluence to support your sprint from within JIRA Agile:
For users who work primarily in JIRA, the integration means that useful Confluence pages are only a click away.
The JIRA Links button appears on your page when there are links back to JIRA or JIRA Agile. These might be:
The number on the JIRA Links button indicates the total number of issues, epics and sprints connected to that page, regardless of whether you have permissions to view them. The dropdown will only show details of issues, epics and sprints that you have JIRA permissions to view.
Note: