Calculating Weighted Status Fields in Jira without a Custom Script

A parent issue with ten sub-tasks still can’t tell you, on its own, how much of the work is actually done.

Break a piece of work into sub-tasks in Jira, and each one gets its own status. What Jira doesn’t do natively is roll those sub-task statuses — or their story points — up into a single completion percentage on the parent issue. Native Jira just doesn’t have that math built in.

The two common workarounds both come with a catch. Advanced Roadmaps handles rollups, but it’s a separate, paid product tier, not something every team has access to. The other route is a ScriptRunner scripted field that sums sub-task points and calculates a percentage — which works, but needs a developer to build and maintain, and any change to the calculation (a different weighting for in-progress items, say) goes back into that same queue.

Excel-like Tables for Jira gives teams a third option that doesn’t require either.

What this looks like in practice

A product owner at a mid-sized SaaS company breaks each feature into eight to twelve sub-tasks with story point estimates. Leadership wants a completion percentage on the parent issue for the roadmap review. Without Advanced Roadmaps or a ScriptRunner field, that number gets calculated by hand — pull up each sub-task, note its points and status, do the math in a notebook or a side spreadsheet, then manually update a “Completion %” field before the review.

With Excel-like Tables for Jira, the product owner builds a small table inside the parent issue listing each sub-task, its story points, and its status, with a formula calculating weighted completion automatically. The result maps back to the “Completion %” field the roadmap review already pulls from — recalculated the moment a sub-task’s status changes, not the moment someone remembers to redo the math.

What breaks without this

• The “Completion %” field reflects whatever was calculated by hand last, not the current state of the sub-tasks underneath it.
• Recalculating by hand takes real time on every feature, every review cycle, which doesn’t scale as the number of parent issues grows.
• A sub-task moving from “In Progress” to “Done” doesn’t change the parent’s completion percentage until someone manually redoes the math.
• Two people calculating completion percentages differently — one counting by story points, one by raw sub-task count — produce numbers that aren’t comparable across features.
• Teams without Advanced Roadmaps and without ScriptRunner access simply don’t have a completion percentage at all, and report progress qualitatively instead.

The larger the backlog of parent issues needing a rollup, the more this becomes a recurring manual chore rather than a one-time setup problem.

How Excel-like Tables for Jira fixes this

Excel-like Tables for Jira turns the rollup into a formula inside the parent issue itself, rather than a calculation that has to happen somewhere else and get copied in. The sub-task breakdown and the weighting logic live in a table in the same issue, and the completion percentage writes straight to the Jira field the roadmap review already uses — recalculating automatically as the underlying data changes.

Key capabilities for this scenario:

• 450+ formulas — weighted completion calculations based on story points, status, or any other criteria, without Advanced Roadmaps or a script
• Two-way Jira field mapping — the “Completion %” field updates automatically from the table, not from a manual recalculation
• Reusable table templates — the same rollup structure applies across every parent issue, so completion percentages are calculated consistently
• Structured sub-data inside issues — the sub-task breakdown lives in the same table as the calculation, not a separate spreadsheet
• Conditional formatting — flag parent issues below a completion threshold automatically ahead of a review

What changes for your team

Preparing for a roadmap review used to mean manually recalculating completion percentages for every feature the night before. Now the number is already current, because it recalculates the moment a sub-task’s status or points change.

Comparing progress across features used to mean trusting that everyone calculated completion the same way. Now every parent issue uses the same table template and the same formula, so the numbers are comparable by default.

Built for the people running this

Project Manager / Program Manager — status rollups across sub-tasks are exactly the kind of manual math you’ve been doing by hand without Advanced Roadmaps. Excel-like Tables for Jira automates it with a formula you control directly.

Product Manager / Product Owner — feature completion percentages for a roadmap review no longer require a night-before recalculation. The rollup updates as the sub-tasks do.

Jira Administrator / System Administrator — teams asking for a scripted rollup field no longer need to go through you or a ScriptRunner license. The formula lives with the user who needs it.

A parent issue shouldn’t need a paid add-on or a developer just to know how much of its own work is done.

Excel-like Tables for Jira is Cloud Fortified and Runs on Atlassian; ISO/IEC 27001:2022 certified at the company level.