Settings

Sumline works without any settings. A Jira admin can change four things, for every space on the site, under Jira settings › Apps › Sumline settings. Nothing there names a field: story points and sprint fields are always detected per space. See Team-managed and company-managed spaces.

Fields to roll up

Story points, Original estimate, Time spent and Remaining estimate, 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 CSV. The columns of the tables stay as they are.

Rows on the rollup tables

• Epics (and anything above them), the default: one row per epic, and per initiative where the site has that level.
• Initiatives only (the level above epics): one row per initiative. This option is greyed out on a site with no level above epic.

Done only

Off by default. When it is on, Sumline counts only issues whose status category is Done, and only when every issue between them and the row is done too: an issue 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 CSV’s 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.

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.

Either way, the values that were not counted are named in the panel and the export. See Each estimate counted once.

After saving

“Saved. Every rollup recomputes on its next open.” People who have a view open see the new numbers after they press Refresh or open it again.