Confluence: JIRA integration features
Objective
How do JIRA and Confluence interact with each other?
Environment
Cloud / Server
Procedure
Confluence and JIRA were designed to compliment each other, and have a number of integration points built-in, giving Confluence users the ability to view, interact with, and reference JIRA issues from a wiki page. This is especially useful in the case where Confluence is being used for project collaboration, requirements gathering, and team meeting notes - involved parties can participate in project discussion, while viewing JIRA issues, or creating new ones without leaving Confluence. To put this in the context of a product-focused team, ideation, product discussion, and requirements authoring are documented on a Confluence page.
From JIRA:
- Access entire Confluence page or report on a JIRA Dashboard (add to dashboard as a gadget)
- Link to a Confluence page in any JIRA issue
- Kick off a JIRA Agile retrospective in Confluence with a single click
From Confluence:
- The JIRA issues macro allows you to display an entire list of JIRA issues within a Confluence page. Issues can be filtered and sorted however you like.
- Ability to embed JIRA reports/charts within a Confluence page (including JIRA filter results, project status reports, and change log reports) – JIRA gadgets and the new JIRA Report Blueprint
- With Confluence Team Calendars, view JIRA issue due dates, milestones, and sprints alongside your people and team events calendars
- Track your important notifications from linked JIRA instances in your Confluence WorkBox - shares, mentions, and comments.
- Users create JIRA issues which correspond to these features, fixes, and stories directly from the same Confluence page simply by highlighting existing text on the page.
- Get a single, dynamic view of all the sprints, epics, and issues related to your requirements at the top of the page ("JIRA links" button)
- Delegate Confluence user management to JIRA in order to use your existing JIRA users and groups for Confluence
Confluence has an out of box page template called Product Requirements Blueprint which helps to define, track and scope requirements for your product or feature. While using the ‘Product Requirements’ template you can:
- Define document properties - Can add properties like ‘Status’ and ‘Owner’ to your document to make easily organize and sort your product requirements.
- Create requirements – Product requirements can be organized in a structured manner with consistency using the customizable template. While using JIRA, stories can be created right from the requirements page and move to and from the page or issue.
- Track progress – Can view the status of all your requirements in one glance. Can also sort by properties like status and release, or access linked JIRA issues from your requirements pages.
For further information on Confluence and JIRA integration:
- 5 reasons to add Confluence if you’re a JIRA Software team
- Integrating JIRA and Confluence together
- Confluence for Software Teams
- Use JIRA applications and Confluence together
- If you go to 55:56 of our demo video
- Video: Product Requirements Blueprint Video for Confluence Team Collaboration Software
- Webinar recap: Using JIRA and Confluence for agile software development
Additional Information