Story points, time and % complete rolled up from subtasks to epics and initiatives — correct in team-managed and company-managed spaces.
The number is on the issue itself, with nothing to set up, and it covers every level from subtask to initiative without counting anything twice. Two story-points fields, mixed estimates, empty epics, children in other spaces: where other rollup apps go wrong, Sumline gets it right or says what it left out.
01
On the issue, with nothing to set up
Every issue with children shows % complete, done by count and unestimated children in its Details column: no click, and no dashboard, filter or gadget to configure. The Sumline panel adds totals per field, both percentages, warnings and a child table.
02
Every level, counted once
Subtasks, stories, epics and initiatives add up into one number. When a story and its subtasks both carry estimates, one level counts and the rest is listed. Progress is shown two ways, by estimate and by issue count, unestimated children are named, and an empty epic shows “—”, never 100 %. No silent wrong numbers.
03
And a table across spaces
One row per epic or initiative: points done / total, remaining time, both percentages, issue count and warnings. Filter by status, assignee and sprint, sort, export to CSV. Roll up any set of spaces in one table.
Pricing
Free for teams of 10
$0.70 per user a month after that
Every feature on the free tier. Above 10 users, billed through Atlassian.
Questions
Which story-points field does it use?
The one your space uses: “Story point estimate” in team-managed spaces, “Story Points” in company-managed spaces, detected by field type. If a company-managed space has values in both, Sumline uses the native one and names the issues whose other field holds a value; it never adds both.
What counts as done?
Any status whose status category is Done. Status names are never used, so renamed or custom workflows do not change the numbers. The “done only” setting restricts the rollup to done branches and lists what it hid.
What if a story has points and its subtasks have points too?
Sumline counts one level. By default the children win and the story’s own value is set aside; an admin can choose “parent wins”. Either way the values that were not counted are listed under the totals and in the CSV.
Can’t I do this with a dashboard gadget?
Partly. A gadget groups a filter by parent and sums one field: one level down, on a dashboard, once you have set it up. Sumline puts the number on the issue itself with nothing to set up, adds up every level from subtask to initiative with each estimate counted once, and names what it left out.
How is % complete calculated?
Two ways, always both: by estimate (story points done ÷ total; if there are no points, time spent ÷ (spent + remaining)) and by issue count across all levels below the parent.
Is there a size limit?
Yes. A Progress view rolls up at most 2,000 issues, and the count is the whole rolled-up tree: every issue in the selected spaces plus every child of those epics that lives in another space. A space with 300 issues whose epics hold 1,800 stories elsewhere is a 2,100-issue tree and is over the limit.
Above it Sumline stops and says so rather than showing a partial number. The issue panel has no such limit.
Where is my data stored?
In Forge Key-Value Storage hosted by Atlassian, in your site’s region: a per-user rollup cache that expires after five minutes and the admin settings. Nothing is sent anywhere else.
Hear when it launches
Sumline is coming to the Atlassian Marketplace. Leave your email and we’ll send one message when it is live.