Skip to content
Menu
HelpSumline, Plans and Σ fields

Sumline, Plans and Σ fields

Jira Cloud has three ways of its own to add estimates up: the Σ figures of time tracking, Plans, and an Automation rule. Each one answers part of the question. This page says what each does, where it stops, and what Sumline does differently, so you can choose. It was checked against Atlassian’s own documentation on 3 October 2026; Jira changes, so follow the links for the current word.

Σ fields: a work item and its sub-tasks

When sub-tasks are on, Jira shows a Σ figure beside the time tracking values: the work item’s own original estimate, time spent and remaining estimate, plus those of its sub-tasks. Atlassian describes it in the Time Tracking Report and in this knowledge base article.

What that means in practice:

  • One level only. Time rolls up one level and no further: a story’s Σ includes its sub-tasks, and an epic’s includes its stories’ own time but not their sub-tasks’ (Atlassian’s behaviour update of 3 June 2025 on JRACLOUD-70150). Nothing reaches an initiative.
  • Time only. The Σ figures are time tracking values; there is no Σ for story points.
  • Both levels are added. A story estimated at 8h whose sub-tasks add up to 8h shows 16h: the parent’s own estimate and its sub-tasks’ are summed, not one or the other.

Plans: the whole tree, on Premium

Plans (formerly Advanced Roadmaps) does roll estimates up through every level, story points or time. Atlassian’s page on how Plans rolls up estimates says three things worth knowing:

  • it is part of Jira Cloud Premium and Enterprise only;
  • the figures it rolls up are the plan’s: you see them when you open the plan, and a board, a filter or the work item’s own fields do not show them;
  • the generated values replace any estimate entered by hand on the parent while the plan shows them, and they follow the remaining work, so they go down as time is logged on the children.

If your site is on Premium and the people who need the numbers work in a plan, Plans may be all you need. What the step from Standard costs, beside Sumline, is in Roll up in Jira without Premium.

The Automation rule: a sum written into the parent

Atlassian publishes an Automation rule that sums story points into the parent. When a story’s or sub-task’s Story Points change, the rule looks up the parent’s children with the lookupIssues smart value and writes their sum into the parent’s own Story Points field. It works on every plan, and the result is a real field you can search on.

Where it goes quietly wrong:

  • It runs only when points change. Moving a story to another epic or deleting one changes no story points, so neither epic is recalculated until some other child’s points are edited. The number looks current and is not.
  • It overwrites the parent’s own estimate. Whatever the epic was estimated at before is replaced by the sum, so the two can no longer be compared.
  • One level per rule. Each rule adds one level to the next. Sub-task to story and story to epic need their own rules, and to reach an initiative needs another.
  • One field per rule. Time fields, and team-managed spaces’ “Story point estimate”, need rules of their own.
  • Every run counts toward your site’s Automation usage.

What Sumline does differently

  • Every level, from sub-task to initiative, story points and time alike, on Free, Standard and Premium. See How the numbers are calculated.
  • Each estimate counted once. When a parent and its children both carry an estimate, one level counts (the children, by default) and the value set aside is named, never summed twice. So Sumline’s Remaining on a story can be lower than its Σ Remaining Estimate, which adds the story’s own remaining to its sub-tasks’. The tables say so under the figure, for example “own 80h not counted”.
  • Team-managed and company-managed spaces alike, each read from its own story-points field, even in one tree. See Team-managed and company-managed spaces.
  • Computed when you look. Nothing is written back, so moving a story to another epic shows on the next open or Recalculate, with no rule to keep in step.
  • What is missing is named. Unestimated children, values left out and the remaining estimate on done work items are listed, never counted as 0.
  • On the work item, in a table and on a dashboard, for everyone who can see the work items: two percentages, filters, rows that open to the work items under them, and Excel and CSV downloads.

And what it does not do: Sumline only reads, so its totals are not a Jira field. You cannot search on them with JQL, show them on a board card or use them in an Automation rule. Each person sees the totals of the work items they can open; see Privacy, permissions and data.