Questions

No. Inside Jira, no servers, read-only. Sumline runs on Atlassian Forge, reads Jira as you and writes nothing back. Nothing is sent anywhere.

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 work item 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.

Partly. Jira adds time up one level: an epic counts its stories’ own time, never the time logged on their subtasks. Sumline counts every level, so the subtasks’ hours are in the epic’s total.

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

No. From subtask to epic, everything works on Free and Standard. A level above epics comes two ways: Jira Premium’s own, such as initiatives, which roll up like any parent, or, on any plan, a work type an admin names under Roll up through links in Sumline settings, which rolls up the work items its links point to.

Sumline is free for sites with up to 10 Jira users, with every feature. Above that it is billed per user by Atlassian, at a rate that falls as the site grows, after a 30-day free trial; the Pricing tab of the app’s Atlassian Marketplace listing gives the exact cost for your site.

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, under the row’s figures on the tables, and in the downloads.

Two ways, shown side by side: by estimate (story points done ÷ total; if there are no points, time spent ÷ (spent + remaining)) and by work item count across all levels below the parent. An epic with nothing below it shows “—”, never 100%.

Any status whose status category is Done. Renamed or custom workflows count the same way, whatever their status names. The “done only” setting counts only done branches and lists what it hid.

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 work items whose other field holds a value, and counts the native one only.

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.

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.

Yes. Group by, beside Sort by on the tables, gathers the epics by assignee, priority, status, type, space (across spaces), sprint, fix version or team, with a shaded line over each group adding up its points, time, both percentages and work items. An epic inside its initiative, in the same group, is counted once, and hovering the group’s name says which.

By assignee or team it groups by each epic’s own field: the person the epic is assigned to, or the team in its Team field, else the one its stories share, “No team” last. A grouping that does not apply to the rows on screen stays in the menu, greyed, and hovering it says why, such as “Every row here is one work type” or “This site has no Team field”.

Almost. Sumline rolls up when you open a view and keeps the figures for five minutes, per person, so the next open is instant. Every view says how old its numbers are (“Updated 3 min ago”), and Recalculate reads Jira again right away (on a dashboard, the gadget’s own reload icon), so an edit you just made is one click from showing up.

Yes. A table rolls up at most 2,000 work items, and the count is everything rolled up: the table’s rows (every epic, or initiative, that is open or was done in the last 90 days) plus every work item under them, children in other spaces included. Closed history does not count: epics done more than 90 days ago are not rows and are not fetched. A space with 30 open epics and 3,000 closed work items is well under the limit; 40 open epics holding 2,100 stories and subtasks are over it.

Above it Sumline stops and says so rather than showing a partial number. The work item panel has no such limit, and rolls up any epic however long ago it was done.

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

No. Sumline reads Jira as the person viewing, so Jira applies that person’s own permissions and each person sees only the work items they could open themselves. The cache is kept per person, so one person’s totals are never shown to another.

In Forge Key-Value Storage hosted by Atlassian, in your site’s region: the admin settings, a per-user cache of the figures, a site-wide copy of the field list, work types, priorities and space names kept for an hour, who dismissed the card that says where Sumline shows up, and, once Sumline is on the Marketplace, each person’s count of opens up to five and when they dismissed its request for a review (and, from before 23 October 2026, the date it was first opened and who dismissed its earlier request). Cached figures are served for at most five minutes, and Forge storage deletes them soon after. Nothing is sent anywhere else.

Under Jira settings › Apps › Sumline settings, for the whole site: which of the four fields to roll up (story points, original estimate, time spent, remaining estimate), up to three of your own number fields, whether a row on the tables is an epic or an initiative, whether to count only done work items, whether to ignore the remaining estimate left on done work items, whether the children or the parent wins when both carry an estimate, which delivery warnings show, whether % by work item count counts only leaf work items, work types that roll up through links to a level above epics, and the “Made with Sumline” line under Excel downloads. Story points and sprint fields are always detected per space.

Under Apps › Sumline, and in a Sumline tab in every space (under More when Jira’s tab bar is full, and in the left sidebar of a service desk space). On a work item, it is the Sumline group in the Details column, with the panel under View app actions, once per person. On a dashboard, it is the Sumline gadget, added like any other gadget.

Where to find it, with pictures →

Ask support first: it may already be a setting. If it is another app, tell us. When other teams need it too, we build it.

Request an app →