How to keep your teams informed by publishing JIRA issues in Confluence pages


Keep everyone aware of your development team's progress by creating Confluence pages from your JIRA issues and updating those pages when work is done on user stories.

Problem

You're part of the software development team for your company and need to keep other departments (Marketing, Sales, Consultants, etc.) aware of your progress and inform them of your product's upcoming features.

Your software team manages their daily work directly in JIRA - it is where you write your epics, user stories and their corresponding requirements. Yet communicating your work outside of your immediate team is challenging, as JIRA is mostly a dedicated solution for development teams. Other departments might not have access to JIRA or they simply do not use it for their own work.

Under these circumstances, what is the best way to keep everyone in the know? There is however a tool which everyone can access and connect to daily: your company Confluence.

Solution

Elements Copy & Sync offers a convenient feature that allows for creating Confluence pages automatically from any JIRA issue. The following information will be copied to our new Confluence page from our user stories:

  • Summary
  • Description
  • Status
  • Fix versions
  • Sprints
  • Component's impacted



Everything begins with the user story you want to share with other teams; from the 'More' menu (or by clicking on the button under the issue description) you will be able to trigger the operation and start the Confluence page creation process.



You will be asked to select the target parent page under which the Confluence page is to be created. The title is already filled in from the issue key and summary, however you can override these defaults if necessary.



Click OK and that's it! The Confluence page is created and prefilled with the issue status, priority, components and description. Even the attachments and the labels have been entered.



Labels are a good way to organise your Confluence pages. In this example we put the issue status in the label field so that we can build convenient reporting tables on all our user stories.



So how do you keep the page updated when you start working on the user story? If you execute the Elements Copy & Sync operation, the page gets updated automatically!



The page is updated according to the changes made in the issue: Sprint, Fix version and Status.



Because the issue status is injected into the page labels, the Page Properties Report macro reflects the change in the parent page - all teams are now aware that you started to work on the user story!

Let's go down to the configuration aspects of the use case. Click on the following link to start the set-up.

Let's get started