Over 50% of JIRA Software users also use Confluence throughout the life of software development. Development teams live in JIRA where they track their work, and the rest of the business lives in Confluence where everyone collaborates around requirements, documentation, marketing plans, sales reports, and so much more. There’s value in being able to connect technical teams to non-technical teams to ship software efficiently, just as there’s value in integrating JIRA Software and Confluence so no project is ever siloed to one team and projects ship faster. Here are 7 ways you can do more to bring JIRA and Confluence closer together.
7 ways to do more with a JIRA Confluence integration
Alone, JIRA is a powerful tool to manage project processes from beginning to end, but there’s so much more planning and discussion that happens around projects that is just as important. Confluence provides a home for those discussions to happen transparently, and when you put the two together, teams get to see the whole picture.
1. Automatic links
Whenever a JIRA issue is mentioned in a Confluence page using the JIRA Issue Macro, JIRA will create an issue link to that page for you, automatically. Specs to issues, knowledge base articles to support tickets, project outlines to tasks – easily access those pages, straight from JIRA.
2. Ad-hoc Links
Create links between issues and related pages whenever you like with the Link dialog in JIRA. It’s perfect for referencing a knowledge base article that’s related to a bug report, or user stories and requirements for a new feature request.
3. Embed issues with copy and paste
Autoconvert (aka magic) makes producing reports of issues, backlogs, and tasks as easy as copy and paste. Provided that you’ve connected JIRA and Confluence using Application Links you can paste an individual JIRA issue or JIRA query URLs into the editor and watch them immediately transform into the JIRA Issue macro.
Tip: There are a number of other links you can paste into Confluence that will transform using autoconvert (i.e youtube links will convert to the YouTube video).
4. Create new issues from scratch
Copy, paste, copy, paste, copy, paste – tired yet? So are we. The endless back and forth between two platforms wastes valuable time during which you could be getting the real stuff done. Reduce context switching between JSW and Confluence by creating a new issue straight from Confluence. Just highlight any text on a Confluence page, click the JSW icon that will appear above the highlight, and you’re on your way. Seeing is believing:
5. Display your JIRA data with charts
We love blueprints that make our lives easier and help us work faster. The JIRA Reports Blueprint is especially useful because it makes it easy for development teams to create ad-hoc reports in Confluence to detail their latest releases tracked in JIRA. These reports also provide transparency, giving stakeholders a snapshot of your development team’s progress in a matter of clicks so you don’t have to. The JIRA Report Blueprint includes the JIRA Chart macro, which displays your JIRA projects and issues as a pie chart within your Confluence page for some added context.
6. Maintain traceability within Confluence
Confluence automatically provides a single, dynamic view of all the sprints, epics, and issues related to or embedded in the current page right at the top for easy viewing. Click on the relevant sprint, epic, or issue and we take you straight into JIRA for more information.
7. Create issues from instructional text
Space Admins can insert instructional text into page templates from the page template editor that explains what content to write and how to trigger certain editor features. The instructional text is smart too, disappearing as the user types over it, and is invisible when the page is saved, keeping content clean. Use the power of instructional text in your own templates. Once you’ve selected it in the template editor you can choose to trigger an @mention or a JIRA macro, to jumpstart the issue creation process without having to switch over to JIRA.
Confluence provides a single source of truth for all of your software documentation, bringing teams closer so you can ship software faster. Including JIRA issues in your documentation means less context switching and more ease in keeping stakeholders and teammates in the loop, so momentum never slows. Together, Confluence and JIRA not only speed up the process of conception to creation, they accelerate it.