Confluence Knowledgebase Integration

Welcome to the Jira for Designers series brought to you by Design at Scale™ — Academy. In a previous article, we discussed Sprint for Designers(↘︎Link) and how best to run your Sprint for designers using Atlassian Jira Board. This article will take our exploration into a slightly different place outside of management. The place is called Atlassian — Confluence(↘︎Link), and it helps us to define something we refer to as a knowledgebase. Knowledgebase is the baseline for all the project-related information that serves the creation of different types of documentation and further design guidelines(↘︎Link).

Jira is for tasks

In the previous three articles, we have explored Atlassian’s Jira Kanban(↘︎Link), Scrum(↘︎Link), and Sprint(↘︎Link). This allowed us to see where these tasks overlap, what role they play and how best they contribute to the overall delivery.
If we look closely at the ticket, we will see that there are several things that define the ticket. Whether it is a story or a task, we have the ability to attach external pieces of information. Some of the Agile Coaches(↘︎Link) call it the evidence. In the design world, we relate to them as assets — let alone design assets.