RollGrid for Jira Support

Jira initiative progress above epics

Roll epics up into initiatives, including when the relationship is an issue link rather than a parent.

Above the epic, Jira Cloud's hierarchy depends on your plan and your configuration. Many sites model initiatives with an issue link instead of a parent field, and nothing in Jira totals across a link.

Building it

  1. Create report. Source = A work item and everything under it with the initiative's key, or a JQL that finds all your initiatives.
  2. Switch on include children.
  3. Go to the Hierarchy step and add a link level: choose the link type that joins initiatives to epics, and the way it points — pick the option that reads Parent … child with the initiative as the parent.
  4. Keep the Structure tab. Set progress by story points, or by count of work items.
  5. Save.

If the initiative shows no children

Try the other direction. Link direction is the single most common thing to get backwards, and the symptom is exactly this: an initiative with nothing under it and no error.

The second thing to check is the link type. Sites use "Relates", "Parent of", "Implements" and others for the same relationship. The editor lists the types your site actually has.

More than one level

Add a second link level for a theme or portfolio tier above initiatives. Jira's own parent links continue to work underneath, so a full tree can run theme → initiative → epic → story → sub-task, with the top two joined by links and the bottom three for free.

What the progress bar means

Progress by points is "points in a done status, over all points in the row and below it". Progress by count is the same with work items. Where nothing beneath has an estimate you get "No points to measure" rather than 0% — because an initiative full of unestimated work is not an initiative that has achieved nothing.

Large initiatives

A portfolio-wide report can reach thousands of work items. The grid handles it — above 200 rows it scrolls in its own box and draws only what is visible — and if the source would exceed the 20,000 limit, RollGrid says so rather than reading a subset that would make every roll-up read low.