Skip to content
Menu

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.

The Sumline tab of the Web Storefront space, among the space’s own tabs, highest priority first: 48 work items, 9 To Do, 11 In Progress and 28 Done, a Total line of 79 of 150 points, then twelve epics, one row each with its priority, points, assignee, status, time and both percentages as bars. Two are done, one is not started, and two carry “1 unestimated” warnings.
The Sumline tab in every space. Every row opens to the work items under it.

Estimate in Jira

Story points, a time estimate, or both. Sumline rolls them up the tree.

  1. Add story points

    Give it story points, under More fields.

    WEB-12’s More fields group, open: Story Points reads “Add story points”, with Original estimate and Time tracking under it.
  2. Set the epic

    Set the story’s Parent to its epic.

    The Details column of WEB-12 with its Parent field at the foot: WEB-1 One-page checkout.
  3. See the totals

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

    Sumline’s group in the Details column of a Jira work item, from its heading: Story points 8 / 13, Original estimate 0m / 6h, Logged 2h, Remaining 4h, the progress bars by story points (62%) and by work item count (50%), an amber “No estimate: PAY-12” line and, last, the age with Recalculate.

Add story points, step by step →

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.

Sumline under Apps with APP, LOY and PAY picked and rolled up, grouped by space, highest priority first: 37 work items, 12 To Do, 8 In Progress and 17 Done. A Total line adds up all eleven epics: 62 of 126 points, 49% by points and 46% by work item count. A shaded line for each space adds up its epics: Mobile App (APP) 13 of 44 points, Loyalty (LOY), a team-managed space, 19 of 29 and Payments (PAY) 30 of 53, each epic with its assignee, status, time and both percentages. Three epics carry “unestimated” warnings.
Apps › Sumline over three spaces, grouped by space, highest priority first.
The same table grouped by assignee: a shaded line for each person adds up their epics, Alana Grant 13 of 29 points, Cassi Owens 17 of 29, Kevin Campbell 24 of 40 and Mitch Davis 8 of 28, each over two or three epics, under the Total line, 62 of 126 points.
The same epics grouped by assignee: a total for each person.
The same table grouped by sprint: a shaded line for each sprint and one for work with no sprint, each adding up its epics’ points, time and both percentages, under the Total line.
The same epics grouped by sprint, the epics in no sprint last.
The same table grouped by priority: a shaded line for each priority, Highest to Low, each adding up its epics’ points, time and both percentages, under the Total line.
The same epics grouped by priority, highest first.
The same table grouped by status: a shaded line each for To Do, In Progress and Done, adding up their epics’ points, time and both percentages, under the Total line.
The same epics grouped by status: to do, in progress, done.

See what the totals leave out

Every estimate field and both percentages on the work item. Work with no estimate is listed by name.

The Sumline panel on an epic: “12 child work items across 2 levels” with “Updated 1 min ago” and Recalculate at its right, Story points 10 / 28, Original estimate 7h / 12h, Logged 8h, Remaining 4h, progress by story points (36%) and by work item count (50%), one amber box “Check these work items” naming WEB-15 with no estimate, the child table with its Warnings column, and Open in Sumline.
Work item panel: open it from View app actions (the hexagon under the title) on any work item with children.

Already on every work item

Works as soon as it’s installed. Story points, time and both percentages, without opening a panel.

Sumline’s group in the Details column of a Jira work item, from its heading: Story points 8 / 13, Original estimate 0m / 6h, Logged 2h, Remaining 4h, the progress bars by story points (62%) and by work item count (50%), an amber “No estimate: PAY-12” line and, last, the age with Recalculate.
In the Details column of every work item with children, in a group Jira may show closed until you open it.

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.

The Portfolio dashboard in Jira with Sumline’s gadget: its grey first line “8 parents in APP, PAY · 44% (points) · 46% (12 of 26 done)”, a Total line, the epics PAY-1, APP-1 to APP-4 and PAY-2 to PAY-4 with both percentages as bars, PAY-2 opened to its four stories, “unestimated” and “No estimate” warnings, and a footer with Open in Sumline.
The Sumline gadget, added like any other gadget, for spaces, a saved filter or a JQL query.

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.

Sumline’s table in Jira’s dark theme: the Web Storefront space’s twelve epics, each with its points, time and percentages, on a dark background.

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

See your real totals

Install it. Open any epic. The totals are there.

Get it on Atlassian Marketplace