Epic progress, rolled up.
Story points, time and % complete, from subtasks to initiatives. Right in every space. Nothing counted twice.
Privacy first. No servers. Changes nothing in Jira.

Estimate in Jira
Story points, a time estimate, or both. Sumline rolls them up the tree.
Add story points
Give it story points, under More fields.

Set the epic
Set the story’s Parent to its epic.

See the totals
Sumline shows the epic’s totals, with nothing to set up.

A total for every space
Every epic across the spaces you choose, in one table, with a total for each space and one for all of them. Group by team, fix version or type too.





See what the totals leave out
Every estimate field and both percentages on the work item. Work with no estimate is listed by name.

Already on every work item
Works as soon as it’s installed. Story points, time and both percentages, without opening a panel.

On the dashboard too
The total, then each epic’s two progress bars and its warnings, on any Jira dashboard, for people who never open a work item.

How the numbers add up
Nothing is counted twice
A story estimated at 8 whose subtasks also add up to 8 counts as 8, not 16. One level counts, the subtasks by default, and the values left out are listed.
Unestimated work is flagged
Each one is named rather than counted as zero, and an empty epic shows “—”, never 100%.
“Done” follows Jira’s status category
Renamed and custom workflows count correctly, whatever their status names.
You only see work items you can open
Sumline reads Jira as the person viewing, with that person’s permissions.
What you get
Rolled up
- Points and time
- Story points, original estimate, logged and remaining estimate, plus up to three number fields of your own.
- Subtask to initiative
- Every level, including children in other spaces.
- Two kinds of done
- % by estimate. % by count. Side by side.
- The right field in every space
- Sumline finds the story points field in any space.
- Service desks too
- Requests and their subtasks roll up under each epic.
- Rows that open
- Open any row and see where its total comes from.
Also
- A total per person
- Group by assignee, priority, status, type, space, sprint, fix version or team for a total over each group.
- Delivery warnings
- What may hold the work up, named on its row: overdue, over estimate, closed early or ready to close.
- Excel and CSV
- The rows on screen, after your filters and sort, with hours as numbers a spreadsheet adds up.
- Admins choose
- The fields, the row level, what counts and which warnings show.
- Your columns
- Show or hide any column on every table.
Dark mode, too
Every Lineset app follows your Jira theme, light or dark.

Secure and private
- Runs on Atlassian
- Your data stays on your Atlassian site.
- No servers
- None of ours, and no outside services: nothing is sent anywhere.
- Changes nothing
- It reads Jira and writes nothing back.
- Reads as you
- It sees only what your permissions allow.
Built on Atlassian Forge. No tracking. What it reads and stores →
Pricing
Free up to 10 users
The price per user drops as you grow
- Billed by Atlassian
- Every feature on the free tier
- 30-day free trial
Questions
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 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.
Doesn’t Jira’s Time tracking already add up the time?
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.
Doesn’t Jira Plans already roll this up?
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.
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, under the row’s figures on the tables, and in the downloads.
All questions →Doing it with Jira’s own tools? Step-by-step guides →
Works well with
LoglineWho logged the hours on each epic, and whenSee them on one epic
BlocklineWhat could make each epic lateSee them on one epic
WorklineWho has time for each epic’s work, week by weekSee them on one epic
ChangelineHow long the work in an epic takes to reach productionSee them on one epic