Confluence Progress Bar: How to Show Page and Project Progress

Does Confluence have a native progress bar?

Short answer: no. Confluence Cloud does not ship a custom field that renders a coloured bar at a percentage value. There is no equivalent of the Jira "Custom Field" concept where a Marketplace app can drop a progress bar onto every page.

What Confluence does offer, out of the box, is a handful of building blocks that teams stitch together when they need progress on a page:

• Status macro — a coloured pill label (e.g. IN PROGRESS, BLOCKED, DONE) that you can drop into a table cell or inline in text.
• Tables with a percentage column — a manual approach where you type the number yourself and update it on each review.
• Chart macro — renders a chart (including a horizontal bar) from a table of numbers on the same page.
• Task lists — checkboxes inside a page. Confluence shows how many are completed in some views.
• Jira Issues macro — embeds a JQL-driven table of Jira issues with status, assignee, and custom field columns.

Four practical approaches

Here are the approaches teams use most often, with the trade-offs spelled out:

1. Status macro

Type /status on any page and Confluence inserts a coloured pill. Use it next to deliverables in a table — one row per workstream, one Status macro per row. The full project then "feels" like progress: a row of green DONE pills tells the reader at a glance.

Limitation: it is a stage label, not a percentage. You can't say "67%" with a Status macro, only "IN PROGRESS". For most steering-committee level reporting this is enough.

2. Manual percentage column

Add a table with columns for Workstream, Owner, % Complete, and Notes. Type the percentage manually and update it weekly. Some teams add a Unicode bar — for example ██████░░░░ 60% — to fake a visual bar inside a table cell.

Limitation: it goes stale fast. The number reflects whatever the page author last typed, not the underlying work. Treat it as a snapshot, not a live indicator.

3. Chart macro

Insert the Chart macro and point it at a table on the same page. With a horizontal bar chart, the chart effectively becomes a multi-row progress bar — one bar per workstream, length determined by the percentage in the table.

Trade-off: you have to maintain the table for the chart to update, so it inherits the staleness problem from approach 2. The advantage is the rendered chart looks like a real dashboard tile, which works well in executive reports.

4. Jira Issues macro (live from JQL)

If your work already lives in Jira, the Jira Issues macro is the only approach that updates on its own. Configure it with a JQL filter (e.g. project = ABC AND fixVersion = "Q3 release") and the table shows every matching issue with status, assignee, and any custom field columns you choose.

You can then compute progress two ways:

• By count — the macro shows total results and you can put a JQL for done issues alongside it. Resolved: 14 of 23 (61%).
• By custom field — if you have a per-issue progress field (for example a manual or status-mapped progress bar set up in Jira), display the value as a column in the macro. You see the percentage for every issue without leaving Confluence.

How to embed Jira progress in a Confluence page

The Jira Issues macro is the most underused option for this problem. Here's how to set it up:

1. Open the Confluence page where the progress should appear (e.g. a project home page).
2. Type /jira and select Jira Issues.
3. Authenticate to your Jira site if prompted.
4. Paste a JQL filter, for example project = ABC AND sprint in openSprints().
5. Click Display options and add the columns you want — including any custom progress field if you have one set up in Jira.
6. Insert. The table is now live and updates whenever a reader loads the page.

When progress belongs in Confluence vs Jira

Confluence is the right home for progress when:

• The audience is non-technical — stakeholders, executives, customers.
• The cadence is weekly or monthly, not per-commit.
• You want narrative around the number ("we hit 60% but the integration with X is the bottleneck").

Jira is the right home when:

• The work is already tracked as issues.
• Progress should update as soon as a status changes or a subtask is closed.
• You want list-view columns and dashboard gadgets, not page embeds.

For the second case, a dedicated progress field in Jira is usually the right starting point. Visual Progress Tracker for Jira adds three field types (manual, status-based, subtask-based) directly to Jira issues — and because the values are stored on standard Jira custom fields, they appear in any Confluence page that uses the Jira Issues macro to query that project.

Frequently asked questions