When you use JIRA Agile and Confluence together, you can unleash the potential in your development team. Here are some suggestions to help you get the most out of Confluence and JIRA Agile. The features described on this page require JIRA 6.1.3 and JIRA Agile 6.3.5 and later. 

Use Confluence and JIRA Agile to define requirements

Confluence is the perfect place to start defining your requirements. You can use the Product Requirements Blueprint to capture your requirements, and it'll let you create your JIRA epic and other issues right from the requirements page in Confluence.

On this page:

Here's how it works:

  1. Create a Confluence page using the Product Requirements Blueprint
  2. Choose the placeholder text 'Link to JIRA epic or feature' and choose Create new issue to create your epic in JIRA
  3. Collaborate with your team to define your stories and save the page
  4. Highlight text on your requirements page and choose the Create JIRA issue  link to create stories in JIRA, and automatically link them to your epic
  5. Track the progress of the stories from the Confluence page or from within JIRA

The tight integration between Confluence and JIRA Agile means 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 right there. 

Use Confluence and JIRA Agile to manage your sprints

There's often a lot of material in Confluence that provides useful context for your team during a sprint. These might be requirements documents, designs, tech specs, customer research and more. By linking these pages to epics, you make them easy for your team to find during the sprint. 

Here's how you can use Confluence to support your sprint from within JIRA Agile:

  • In JIRA Agile, create a Confluence page to plan your sprint. The page is created using the Meeting Notes Blueprint – and handy template that helps capture the details you need – and is automatically linked to the sprint.
  • In an epic, link to useful Confluence pages, including requirements, designs, and more.
  • Report on your progress to stakeholders using the JIRA Reports blueprint in Confluence.
  • Use the Retrospective blueprint in Confluence at the end of your sprint to take stock of what went well and not so well

For users who work primarily in JIRA Agile, the integration means that useful Confluence pages are only a click away.

Viewing links between Confluence and JIRA

Whenever you add a link to JIRA issues in Confluence, or link to a Confluence page from JIRA, the JIRA Links button appears at the top of the Confluence page. This makes it really easy to jump from Confluence to JIRA and vice versa, speeding up your workflow.

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 permission to view them. The dropdown, however, will only show details of issues, epics, and sprints that you have JIRA permissions to view.

Note: 

  • The JIRA Links button only appears in the default theme; it's not available in the Documentation theme.
  • The button doesn't detect links from issues displayed in the JIRA Issues macro in table format.

 

  • No labels