[ built in the open ]
No dates, no fake certainty. A card is planned when the demand is measured — in reviews of apps like this one, in Community threads, or from sites using the app — and every card says where. A card under consideration has a reason to exist but not enough asks yet: a “+1” from your site is exactly what we count, and two different sites asking is what moves it.
A background sync keeps a stored copy of every configured project inside your Jira site, and the gadget renders that snapshot instead of reading thousands of issues on every load. A 31,000-issue portfolio renders in about a second and a half. How freshness works →
Each daily full re-read records one history point per project and field; the Trend button in the gadget draws one line per project (a filtered gadget gets a single line for its filtered total). History is kept both for all issues and for open work only, so a gadget set to Open work only charts remaining work. Daily points for 90 days, weekly to two years, monthly after that. Trends →
Issue keys open in Jira, and the unest. badge on an epic or project row filters the tree to the branches with unestimated leaves — open them, estimate them, done. Drill-down →
A per-gadget setting that leaves out every issue whose status category is Done — Cancelled and Won’t Do count as Done — so each total means remaining work. How rollups work →
Narrow a gadget with a JQL expression of up to 500 characters; a saved
filter works through filter = … as long as it is shared with the app and
with the people viewing the dashboard. The filter runs on the stored
snapshot, so renders stay fast. Filtered gadgets are marked “filtered” in
the header and keep their own trend from the day they are configured.
Filtering with JQL →
Original estimate, Time spent and Remaining estimate join the number fields you can roll up, shown in hours. The DONE column shows the share of the subtree that is done, on rows with children and on project rows. How rollups work →
Hierarchy Totals is on the Atlassian Marketplace, approved on 17 September 2026 and installable on any Jira Cloud site. The app is in the Runs on Atlassian program. Pricing is answered in the FAQ. Get it on the Marketplace →
ships in the next release
A second gadget on the same stored copy. Every epic and initiative shows done out of total, percent complete by issue count and by story points or any numeric field, and what is left — rolled up across projects, laggards first, with a daily trend of each project’s percentage from the day the gadget is set up. Built and running on our test site; it is part of the next release.
Source: The most frequent ask in reviews of rollup apps: percent by weight rather than by issue count (6 mentions), and a bar rather than a table (4).
Click a column header to sort by that field; the choice survives dashboard refreshes. Progress rows already list laggards first — this makes the order yours.
Source: Asked in 4 reviews of rollup and time-in-status apps, 2022–2024.
Download the rows you see — values, badges, hierarchy — with the per-project totals and the formula that produced them, for spreadsheets and status reports.
Source: Asked in 4 reviews and threads of rollup apps, 2015–2025 — each one about an export that dropped the totals row.
Depends on: A file download must work from inside a Forge gadget frame; if it does not, this ships as copy-as-TSV.
A per-gadget setting on the Hierarchy Progress gadget: any epic or initiative whose percent complete is below N % is highlighted, so the laggards read from across the room.
Source: 3 asks for colour thresholds (RAG) on progress gadgets, 2024–2026.
The same rolled-up numbers on the epic or initiative’s own page: totals of its children by the fields you configured, from the stored copy, without opening a dashboard.
Source: Asked on Atlassian's own tracker for roll-up fields (JRACLOUD-88031); apps that show tables inside the issue grew fastest in 2026.
Depends on: Must not need new permissions from your admin.
A rolled-up value that JQL can search means writing it into a field, which needs a write permission — the app runs on read-only scopes and that stays. Atlassian’s own Formula Fields and its tracked roll-up field request may close this natively.
Source: Asked once in eight years of reviews in this niche, 4 times across all rollup apps; one review praises a competitor for needing no custom fields.
Depends on: Two live sites asking, and a way that keeps the app read-only. Atlassian tracks roll-up fields itself as JRACLOUD-88031.
Roll up two fields side by side and show the difference or the ratio — spent against estimated, remaining against original — on every row of the tree.
Source: 4 asks in reviews of rollup apps, 2017–2025: time spent against estimate, days between two dates.
Depends on: The first ask from a live site.
The whole tree with its totals on its own page, wider than a gadget allows, for reading and sharing inside Jira. Part of this app, never a separate one.
Source: Three Community threads asking for a tree with totals, Aug–Sep 2026 (300–1,100 views each); no review in this niche asked for it.
Depends on: Two live sites asking, and no native Jira view covering it first.
Embed a rollup table in a Confluence page so status reports keep themselves current. This would be a separate app, and a link for people without a Jira licence is not possible on this platform.
Source: 12 review mentions of showing rollups in Confluence or to people without a Jira licence, 2020–2024; none asked for a macro by name.
Depends on: Two live sites asking; it would be a separate app with its own listing. A public link for people outside Jira is not possible on Forge.