Jira Image of the Day: Benefits of Connecting Jira and Confluence

[#1]

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management, Jira Core, Confluence
Deployment Type	Jira Cloud, Jira Server, Jira Data Center, Confluence Cloud, Confluence Server, Confluence Data Center

What is shown?

A snippet library in Confluence to provide reusable code examples to the development team in Jira. Developers can access this information without leaving Jira.

Visit:

• For business projects: Jira project > Pages

• For software projects: Jira project > Project pages

• For service management projects (users): Jira project > Knowledge base

• For service management projects (admins): Jira project > Project settings > Channels and self service > Knowledge base

What can we learn?

The way to get the most out of your Atlassian applications is by connecting them! By connecting Jira and Confluence, you’ll be able to leverage the following benefits:

Increased visibility

Information is more visible and accessible when it can be viewed in one place. Everyone can leverage the same information and know what everyone else is working on.

Improved access

Users can embed information from one application into another, so it’s easier to access. Users don’t have to leave the application they’re currently in to get information from somewhere else.

Real-time data

Dynamically embedding information means you’re always seeing the latest and greatest information in real-time. Gone are the days of exporting information from one place to import it into another. As we all know, the second information is exported, it’s already stale.

Single source of truth

Connecting applications avoids the need for multiple copies of the same information which creates a reliable single source of truth. There’s no more hunting for information shared via email and wondering if it’s still accurate.

Consistency

Finally, using Atlassian applications together helps standardize processes and creates consistency. Confluence pages have templates so similar information is presented in a standard format. Jira issues and JSM requests all follow a similar info collection and progress reporting format. Consistency ensures users can easily locate and leverage common information.

Connection Ideas

I realize creating a Confluence code snippet library for the Dev team to use in Jira is a narrow use case. Here are some other ideas for sharing information using Jira to Confluence integration:

• Publish a list of on-call or emergency contacts for each system

• Provide reusable wording and communication examples to support agents

• Link HR requests to the organization’s policies and enrollment forms

• Provide checklists for hardware, access, and office furniture for new employees

• Link to the Finance team’s expense reimbursement procedure

• Provide self-service help content to internal and external customers

• Publish each team’s “definition of done” (DoD) reminders list

• Link Jira issues to requirements stored in Confluence

• View Jira boards, dashboards, timelines, and calendars on Confluence pages

• See real-time Jira issue status in Confluence

• And more

---

Back to intro and image list