Stop 11 · BA Tools & PlatformsTopics · 1/8

Jira & Confluence for BAs

In short

Walk into most Agile companies and you'll find two tabs open on every BA's laptop: Jira for the work, Confluence for the knowledge. Learn both and you'll fit in from day one.

Jira tracks backlogs, sprints, and issues; Confluence hosts documentation and requirements — the most common software pairing BAs use daily at companies running Agile delivery.

The purple blob holds a thick file folder next to a whiteboard covered in coloured magnets and blank cards.

Think of it like this

The hospital ward

Each patient has a thick file with their history, test reports and doctor's notes. On the wall is a whiteboard showing who needs what today: X-ray, medicine, discharge. Confluence is the patient file. Jira is the whiteboard. One explains, the other tracks.

Watch it happen

From requirements page to tracked work

Confluence

Jira

Developer

Requirements page

1/6The BA writes a requirements page in Confluence: goals, rules, flows, open questions.

The big ideas

What you need to know

Jira tracks work

Epics, stories, tasks and bugs, moving through statuses on boards and sprints.

Confluence holds knowledge

Requirement pages, meeting notes, decision logs and process docs, organised in spaces and page trees.

Link them

Link stories to their requirement page and embed Jira issues on the page. Traceability with no extra effort.

Filters and JQL

Jira Query Language lets you build saved searches and dashboards, like 'my open stories this sprint'.

See it in code

Walk through the code

text

1project = FEE2AND issuetype = Story3AND status != Done4AND sprint in openSprints()5ORDER BY priority DESC

1/3Only stories in the FEE project.

A JQL search for every unfinished story in the current sprint of the FEE project, most important first. Save it as a filter and add it to a dashboard.

Save yourself the pain

Common mistakes

Oops

Writing full requirements inside a Jira description and nowhere else.

Do this instead

Keep the bigger picture in Confluence and link it. Jira stories should stay short and focused.

Oops

Letting Confluence fill up with outdated pages.

Do this instead

Add an owner and 'last reviewed' date to key pages, and archive what's no longer true.

Your mission

Set up a mini project

~40 min

Quick check

A key decision was made in a Jira comment thread. What's the best way to make sure people find it later?

Go deeper

1Explore a free Jira and Confluence workspace, building a sample backlog and requirements page.
2Practice linking a Confluence requirements doc to related Jira tickets.
3Learn to structure a Confluence space so requirements are easy to find months later.