Settings
Sumline works without any settings. A Jira admin can change the ones below, for every space on the site, under Jira settings › Apps › Sumline settings. Story points and sprint fields are always detected per space, so they are never chosen here. See Team-managed and company-managed spaces.
Fields to roll up
Story points, Original estimate, Logged and Remaining, all on by default. At least one must stay on. A field left out is not added up anywhere and disappears from the totals and the Excel and CSV downloads. The columns of the tables stay, and read “—” for that field.

Number fields to roll up
None by default. Under Your own number fields, pick up to three of the site’s own number fields by name (Jira’s “Number field” type), and each is added up like story points: done / total, counted once when a parent and its children both carry a value. The Story Points field is not in the list, because it is already rolled up as story points. A field shows under the name it has on your site, so a renamed field follows the new name, and a field that is later deleted simply drops out. See How the numbers are calculated.
One row per
- Epic (and anything bigger), the default: a row for every epic, plus every item above epics if your Jira has any.
- Initiative (and anything bigger): a row for every item above epics; epics are not rows. The option shows your Jira’s own names for that work: Initiative on many sites, or Feature, Theme or Campaign if your admin set it up that way (Jira Premium lets each site name the work types above epics, and put several side by side). It is greyed out if your Jira has nothing above epics, which needs Jira Premium. A space with none of that work open says so by name, and that the setting makes the rows.
Done only
Off by default: Count only work items whose status category is Done (hidden branches are always listed in the warnings). When it is on, Sumline counts only work items whose status category is Done, and only when every work item between them and the row is done too: a work item that is not done leaves out its whole branch, done children included. The row itself always stays. What was left out is always listed: in the Sumline panel with the keys, as “N hidden (done only)” on the tables, and in the downloads’ Exclusion note.
With done only on, the totals describe finished work, so % complete is 100 % wherever anything was counted. Use it to see what has been delivered, not how far along something is. The delivery warnings still read every work item: an epic with open work under it is never “Ready to close”.
Remaining on done work items
On by default: Ignore the remaining estimate on done work items (the amount left out is always named). Jira keeps a work item’s remaining estimate when it is closed without logging the time, so without this a finished epic can still show hours left. Switch it off to count Jira’s value as it is. See How the numbers are calculated.
When a parent and its children both carry an estimate
- Children win: drop the parent’s own estimate, the default.
- Parent wins: drop the descendants’ estimates. A parent’s own original or remaining estimate of 0 counts as none, so its children’s count.

Either way, the values that were not counted are named in the panel and the export, except a 0, which changes nothing. See Each estimate counted once.
Delivery warnings
Which warnings about the work itself the Warnings column, the work item panel and the downloads show. On by default: Overdue, Over estimate, Closed early and Ready to close. Off by default, because a team that estimates in story points or sets no due dates would see them on nearly every row: No due date, Unassigned and Logged, no estimate. None of them changes a figure; the warnings about estimates always show. See How the numbers are calculated.
% by work item count
Off by default: Count only work items with nothing under them (leaf work items). On, a story with subtasks counts through its subtasks alone, so a story and its subtasks are not counted side by side; the panel’s line then reads “Complete by work item count (leaf work items)”. The Work items column, and the count over the table, still count every work item.
Roll up through links
A level above epics without Jira Premium. Add a rule, pick the work type (“Theme”, say) and the link that points to its children (“contains”, say, or the other end of a link, “is contained by”): work items of that type then roll up the work items their links point to, and everything under those. Up to three rules, so Theme, then Initiative, then Epic is two. Each work item counts under one parent: when two link it, the first counts it and the other names it. A rule left half filled in is dropped when you save.
Hours format
Time reads as hours and minutes, 76h 45m, as Jira writes it. Pick Decimal (7.5h) to read it as 76.75h. It changes the panel, the Details column, the tables and the gadget, and it takes effect the next time a view opens, with no recalculation. Downloads always hold decimal hours, such as 76.75, whatever you pick, so a spreadsheet can add them up.
Excel downloads
On by default: Add ‘Made with Sumline’ under Excel downloads. Every Excel download then ends with one line under the table, after a blank row, linking to lineset.dev/sumline. Switch it off and the Excel file holds the table alone. CSV downloads never carry it. See Exporting to Excel and CSV.
Saving and resetting
Reset to defaults, beside Save, puts the defaults back in the form; nothing is saved until you press Save.
“Saved. Every view rolls up again on its next open.” People who have a view open see the new numbers after they press Recalculate or open it again; on a dashboard, Jira’s reload icon on the gadget or the dashboard’s Refresh does the same.