Skip to content
Menu

Can a Jira formula field add up child work items?

Checked against Atlassian’s documentation on 12 October 2026.

Jira Cloud now has formula fields: a field whose value is calculated from other fields. So the question comes up, as it did under one of our own posts: “can’t we do that with the new Jira calculated custom fields?” This page says what a formula field can and cannot add up, what to use for a total from child work items, then what Sumline does.

What a formula field does

  • It calculates within one work item. Atlassian’s page: “A formula can only run using data within a single work item”, and its example says a formula on one work item “can’t calculate costs across work items B or C” (Atlassian).
  • It works with that work item’s fields: arithmetic on number fields, rounding, dates and text, with the functions Atlassian lists (supported functions).
  • Its value shows in the list view, on the board, in JQL and in Automation, in company-managed and team-managed spaces alike.

So a formula field is good for a number that belongs to one work item: two of its number fields multiplied, a budget against its actuals, working days to its due date. It cannot read an epic’s children, so it cannot add their story points or their time up to the epic.

What adds up children

  • Time tracking’s Σ figures, one level: a story includes its subtasks’ time, an epic its stories’ own time (JRACLOUD-70150). Story points have none.
  • An Automation rule with a lookup of the children writes their sum into a field on the parent, one level and one field per rule; see Sum story points from subtasks to epics in Jira. A formula field can then use that field, for example to turn the sum into a percentage, since it is now a field of the epic.
  • Plans, on Premium and Enterprise, rolls estimates up every level, inside the plan; see Jira roll-ups without Premium.

With Sumline

Sumline is our app. It is the part across work items: it reads each issue’s children, wherever they live, and adds them up without a rule or a field.

  • Story points, original estimate, time spent and remaining, from subtask to story, epic and initiative (initiatives need Jira Premium), and up to three number fields of your own, rolled up like story points.
  • % complete two ways, by estimate and by issue count.
  • Each estimate counted once, and unestimated work named.
  • On the issue, in a table and on a dashboard, with Excel and CSV downloads.

What it does not do: Sumline only reads, so its totals are not a field a formula, JQL or an Automation rule can use. If you need the total in a field, the Automation rule is the way today. How Sumline counts is in How the numbers are calculated.

The Sumline group in the right-hand column of a Jira epic: 8 of 13 story points, 2h logged, 4h remaining, progress by estimate and by issue count, one unestimated child by key, and Recalculate.
The Sumline group on the epic PAY-2, in the issue’s Details column: 8 of 13 story points, 2h logged and 4h remaining across its children.

Sumline is in Marketplace review. Get one email the day it’s live.