Jira roll-ups without Premium

You want story points and time added up from subtasks to stories, epics and initiatives, and the one place Jira does all of it is Plans (formerly Advanced Roadmaps), on Premium. This page says what Plans does and what Premium costs, what Jira gives you on Standard, then what Sumline costs beside it.

What Premium adds

• Plans rolls estimates up through every level. Story points or time, from subtasks to epics and the levels above them, with progress by estimate and by work item count (Atlassian). The figures are the plan’s: they show when you open the plan, and in the plan they replace any estimate entered on the parent by hand.
• It is on Premium and Enterprise only. Atlassian’s pricing page lists “Advanced planning (Plans)” under those two plans, and its own pages say the same (pricing).
• Levels above epic, such as initiatives, are Premium too. “Jira Premium and Enterprise customers can also create and manage additional levels in their work type hierarchy” (Atlassian).
• Premium brings more than Plans. The same pricing page names global automation and more storage among its features. If your site wants those anyway, Plans comes with them.

What Jira gives you on Standard

• Σ time tracking, one level. A story’s Σ figures add its subtasks’ time to its own; an epic shows its stories’ own time and nothing below them, and story points have no Σ at all (JRACLOUD-70150). The Σ columns can be added to a search and exported. More in Sumline, Plans and Σ fields.
• The Epic report, on company-managed Scrum boards, shows one epic’s complete, incomplete and unestimated story points (Atlassian).
• The timeline’s progress bar counts an epic’s children by status, not points or hours (Atlassian).
• Automation rules write a sum into a field, one level and one field per rule, and only when their trigger runs. The rules, step by step: story points to the epic, logged time to the epic and % complete.
• Formula fields calculate within one work item: Atlassian’s page says a formula “can only run using data within a single work item”, so it cannot add up children (Atlassian). More in Can a Jira formula field add up child work items?

On Standard, those cover a lot of what a team asks for. What none of them gives is a total from every level below an epic, kept current without a rule, on the epic itself.

What each costs

Jira’s prices here are Atlassian’s list prices in effect from 13 October 2026. Atlassian prices monthly billing per user, progressively: USD 9.70 a user for the first 100 users on Standard, USD 8.20 for users 101 to 250, USD 6.85 for 251 to 1,000; on Premium USD 19.60, USD 14.65 and USD 10.20 (future pricing tables). Sumline’s prices are those set for its Marketplace listing, billed by Atlassian the same way, per user and progressively; it is free for sites with up to 10 users.

A month, for the whole site:

• 25 users: Jira Standard USD 242.50, Premium USD 490.00, so the step to Premium is USD 247.50. Sumline: USD 18.75.
• 50 users: Standard USD 485.00, Premium USD 980.00, a step of USD 495.00. Sumline: USD 37.50.
• 100 users: Standard USD 970.00, Premium USD 1,960.00, a step of USD 990.00. Sumline: USD 75.00.
• 250 users: Standard USD 2,200.00, Premium USD 4,157.50, a step of USD 1,957.50. Sumline: USD 150.00.
• 1,000 users: Standard USD 7,337.50, Premium USD 11,807.50, a step of USD 4,470.00. Sumline: USD 337.50.

Annual billing costs less for both. Prices change: check Atlassian’s pricing page and the Pricing tab of Sumline’s Marketplace listing for your own site.

Which fits

• Your site is on Premium already: use Plans for planning, and look at Sumline only if people outside the plan need the totals on the issue.
• You would move to Premium for Plans as a whole (planning across teams and spaces, capacity and dependencies): the roll-ups come with it.
• You would move to Premium only for the totals: compare the step to Premium above with an app, or with Automation rules if someone can keep them up.

With Sumline

Sumline is our app. It adds estimates up on Free, Standard and Premium alike:

• Every level, from subtask to story and epic, and to initiatives where your site has them (they need Jira Premium): story points, original estimate, time spent and remaining, children in other spaces included.
• On the issue, in the Details column of every issue with children as soon as it is installed, and in the Sumline panel with each child’s share.
• In a table per space or across the spaces you choose, with both percentages, filters, rows that open to the issues under them, and Excel and CSV downloads; and on a dashboard gadget.
• Each estimate counted once, and unestimated work named rather than counted as zero.

What it does not do: Sumline only reads, so its totals are not a Jira field. You cannot search them with JQL or use them in an Automation rule, and it does no planning: no capacity, no dependencies, no dates. For that, Plans is the tool.