Create Confluence pages without leaving your Jira issue

🚧

Case study under construction.

Overview

Problem

Speaking with Jira + Confluence co-users, we identified a huge pain point with working across the two products today.

As a developer, I want to easily access and update documentation related to my tasks (i.e. PRDs, decision logs, tech specs) in order to complete my tickets quickly and accurately.

But today, I need to load a whole additional product – Confluence – in a new tab. Not only does the new product throw me out of my current context, it adds to my ocean of tabs, thus making it harder to find my way back to my Jira task.

All this context switching and navigation takes focus away from my goal, disrupting my flow.

“I would be spending 70% of my time on Jira and 30% of my time going back and circling, ‘ok - what was that that I needed?’” Senior Developer

Solution

We developed the ability for Confluence and Jira co-users to view, edit, and create auto-linked Confluence pages without leaving the Jira issue they’re working on.

Whether you're adding product requirements, drafting a testing report, documenting a product decision, or capturing meeting notes – this update aims to make it easier to add the context your team needs to tackle tasks and projects effectively.

Outcome

More users using Jira + Confluence together than ever

Increased engagement with multiple Confluence features

Customers want it