Story points, time and % complete, rolled up from subtasks to initiatives

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.

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.

Yes, and that is the case Sumline was built for. Team-managed spaces keep story points in a different field from company-managed ones; Sumline finds the right field for each space automatically, so a tree that spans both kinds of space adds up correctly.

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. An epic with nothing below it shows “—”, never 100%.

Almost. Sumline computes a rollup when you open a view and keeps it for five minutes, per person, so the next open is instant. Every view says how old its numbers are (“Updated 3 min ago”) and has a Refresh button that recomputes them right away, so an edit you just made is one click from showing up.

On the issue: the Sumline group in the Details column of every issue with children, there as soon as the app is installed, with nothing to add. The Sumline panel with the child table opens from View app actions, the hexagon under the issue’s title, once per person.

In a space: the Sumline tab beside the space’s own tabs (in the left sidebar of a service desk space). Across spaces: Sumline under Apps in the sidebar.

On a dashboard: the Sumline gadget, added like any other gadget.

In Forge Key-Value Storage hosted by Atlassian, in your site’s region: the admin settings and a per-user rollup cache. A cache entry is ignored five minutes after it was computed and overwritten by the next rollup. Nothing is sent anywhere else.

Four things, for the whole site, under Jira settings › Apps › Sumline settings: which of the four fields to roll up (story points, original estimate, time spent, remaining estimate), whether a row on the rollup tables is an epic or an initiative, whether to count only done issues, and which level wins when a parent and its children both carry an estimate. Nothing there names a field: story points and sprint fields are always detected per space.

No. Sumline only reads. Its one Jira permission is read access to issues; the other is storage for its own settings and cache. It cannot edit an issue or change a field value.

Yes. Sumline reads Jira as the person viewing, so Jira applies that person’s own permissions and nobody is shown an issue they could not open themselves. The cache is kept per person, so one person’s totals are never shown to another.

Yes. Epics, requests, tasks and subtasks in a service desk space roll up the same way: original estimate, time spent and remaining from the requests and their subtasks, done by status category, both percentages. The Sumline tab sits in the space’s sidebar. The sprint filter is greyed out because a service desk has no sprints, and story points show “—” unless the space’s screens carry the field.

The one your space uses: “Story point estimate” in team-managed spaces, “Story Points” in company-managed spaces, found automatically. 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.

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.

No, except for initiatives. Rolling up to initiatives needs Jira Premium, which adds the level above epic; from subtask to epic, and everything else, works on Free and Standard.

Inside Plans, on Jira Premium, yes. Sumline puts the number on the issue itself and in a table every user can open, on Free and Standard as well as Premium.

Yes. A rollup table shows 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.

Sumline is free for sites with up to 10 Jira users, with every feature. Above that it is $0.75 per user a month, billed by Atlassian, after a 30-day free trial.

Yes. Above 100 users the per-user rate steps down through Atlassian’s standard volume bands, from $0.75 down to $0.25 at the largest sites.