Story Point Rollups Without Leaving Confluence

Jira can tell you the story points for one project. The rollup across five projects is still something you build by hand.

Jira calculates story point totals well within a single project or board — velocity charts, sprint reports, burndown. What it doesn’t do natively is roll story points up across multiple projects into one combined view, especially when that view needs a custom calculation Jira’s own reports don’t offer, like completion percentage weighted by point value rather than issue count.

The common workaround is exporting each project’s issues, combining them in Excel, and calculating the rollup there — a process that has to be repeated every reporting cycle, disconnected from Jira the moment the export is taken. Confluence’s native Jira macro doesn’t help either, since it can display issues but can’t calculate a custom cross-project formula on top of them.

Excel-like Tables for Confluence closes that gap: its Jira Issue Sheets feature pulls every project’s issues into one Confluence table, where its own formula engine calculates the cross-project rollup Jira’s reports don’t offer.

What this looks like in practice

A PMO Analyst overseeing five engineering teams needs a monthly cross-team story point rollup — total points committed, completed, and a weighted completion percentage — for a portfolio review. Today, that means exporting all five teams’ Jira boards, combining the exports in Excel, and calculating the weighted percentage there, since Jira’s own velocity reports only work at the single-project level.

The Excel file gets pasted as a static table into the portfolio review’s Confluence page, disconnected from Jira the moment it’s exported.

What breaks without combined Jira and calculated rollups

• The PMO Analyst repeats a manual export-and-combine process every single reporting cycle
• The weighted completion percentage — the number the portfolio review actually cares about — isn’t something Jira calculates on its own, so it’s recalculated by hand each time
• The static table on the review page is disconnected from Jira the moment it’s pasted in, and nobody notices when it drifts from reality
• Comparing this month’s rollup to last month’s means keeping manual copies of past exports, since nothing here is version-tracked
• A single team’s Jira Issue Sheet getting rebuilt or reorganized without a shared starting point can silently break the PMO’s cross-team formulas without anyone catching it until numbers look wrong

How Excel-like Tables for Confluence fixes this

Its Jira Issue Sheets feature pulls live story point and status data from all five teams’ boards directly into one Confluence table. Each team’s sheet is built from the same saved template, so the columns the PMO Analyst references stay in the same place even as new teams get added. The Analyst builds the weighted completion percentage as a formula once, referencing the live Jira fields — so the rollup recalculates automatically as each team’s board updates, instead of being rebuilt from scratch every review cycle.

Key capabilities for this scenario:

• Jira Issue Sheets → live story point and status fields from multiple projects, in one Confluence table
• Combined Jira and spreadsheet formulas → a weighted completion percentage Jira’s own reports don’t calculate
• Templates and reusable sheets → every team’s Jira Issue Sheet starts from the same column layout, so the PMO’s Cell Linking formulas don’t need rebuilding when a new team joins the rollup
• Cell Linking → combine per-team Jira Issue Sheets into a single portfolio-level rollup
• Scalable data handling → the rollup stays fast across five teams’ worth of issues without slowing the page down

What changes for your team

The monthly export-and-combine cycle disappears. The PMO Analyst opens the rollup page before the portfolio review and the weighted percentage is already current, calculated from live Jira data instead of a month-old export. Comparing trends over time means looking at the same live page, not hunting through old file copies — and adding a sixth team to the rollup means handing them the template, not rebuilding the Analyst’s formulas.

Built for the people running this

Project Manager / Program Manager — You need a cross-project view Jira doesn’t natively provide. Combined Jira and spreadsheet formulas calculate it directly, without an Excel detour.

Head of PMO / Director of Operations — Portfolio-level rollups stop depending on a manual monthly export process that only one analyst knows how to run.

The rollup Jira couldn’t calculate got calculated anyway — without leaving Confluence.

Backed by Ricksoft, Inc.’s ISO/IEC 27001:2022 certification, Excel-like Tables for Confluence runs alongside Jira’s own velocity reports rather than replacing them — reach for Excel-like Tables for Confluence when a rollup spans multiple projects with a custom calculation, not just a single board’s built-in totals.