Delivery lead wants percent complete by story points, not by issue count — Hierarchy Totals

When

By issue count the epic is half done: two of four stories are closed. The two still open are the big ones, and the review asks for the share by points.

Set up

Add the Hierarchy Progress gadget to a dashboard.
In its settings, tick the projects and pick Story point estimate as the weight field.
Save.

You get

The Hierarchy Progress gadget with three project rows — MOBL, FIN and PLAT — and their epics: done out of total, % done, % by points, what is left and a bar on every row, with unest. badges; MOBL-95 reads 2 / 4, 50% done and 24% by points.

Every epic, every level above it and every project on one row: done out of total, % done by issue count, % by points and what is left. The row furthest behind comes first. MOBL-95 above is 50% done by count and 24% by points.

Why it pays

Both shares sit side by side, so the review talks about the open work instead of about which percentage is the right one. Nobody exports the epics to a spreadsheet to weigh them by hand.

Limits

Done means Jira’s status category Done, not resolution. When none of the open work under a row is estimated, % by points shows a dash rather than 100%. The trend of each project’s percentage starts the day the gadget is set up — nothing before it — and draws one line per project, none per epic. Up to 50 projects per gadget.