Skip to content
Dangel Studio
de en

Rollup Guard

Epic progress and hierarchy mismatches at a glance, no Premium plans required.

Jira Cloud · in Marketplace review

Listing still under review. Rollup Guard is built, tested and deployed to production; the Marketplace listing is currently with Atlassian. That is why there is no install link here yet. The documentation on this page already describes what will ship. Write to me if you need earlier access.

What it does

On Jira Standard there is no built-in answer to “how far along is this epic, really?” Per-epic progress and the quiet contradictions in between only come with Plans or Premium. Rollup Guard computes both straight from your project:

  • Child progress per epic: how many child issues are done, as an always-floored percentage, computed on every visit from the issues visible to you.
  • Three hierarchy checks: a done epic with open children · all children done but the epic still open · children due after their epic’s due date.
  • Works on Jira Standard: no Plans, no Premium license needed.
  • Subtasks handled correctly: subtasks belong to their story, not to the epic, so they are never miscounted as “without an epic”. Epics are recognised by hierarchy level, not by name, so renamed issue types keep working.
  • Read-only by design: no storage, no writes, no background jobs.
Real Jira: two epics, all three mismatch checks on the project page
Fig. 1 Real Jira: two epics, all three mismatch checks on the project page

Getting started

  1. Install the app for your Jira Cloud site from the Atlassian Marketplace listing.
  2. Open any project and go to the Rollup Guard page. The rollup renders immediately, no setup.
  3. Fix the reported mismatches right in Jira and reload the page. Everything is recomputed live on every visit.
Per-epic progress: a done epic hiding open children shows up instantly
Fig. 2 Per-epic progress: a done epic hiding open children shows up instantly
Three hierarchy mismatch checks
Fig. 3 Three hierarchy mismatch checks

Permissions and data

Rollup Guard runs entirely on Atlassian Forge and requests exactly one permission:

  • read:jira-work: one bounded, read-only JQL search per page view, scoped to the single project you are looking at, executed with your own permissions (asUser). It fetches only summary, status, issue type, parent and due date; epics and children are grouped in memory and the rollup is rendered directly.

No writes to Jira, no background jobs, no scheduled scans, and no storage of any kind: the app persists nothing, so there is nothing to delete, export or leak; it stores no personal data either. No external servers, no data egress, no AI, no tracking, no third-party services.

Read-only by design: the app persists nothing at all
Fig. 4 Read-only by design: the app persists nothing at all

Support

Direct line to the developer: no ticket system, no first-level filter.

Support is provided on a best-effort basis. No fixed response or resolution times (SLA) are promised.

Status and versions

  • In preparation: the app is fully built, deployed to production and verified end-to-end; the Marketplace listing is being prepared and will be linked here once Atlassian approves it.
  • Limits of this version: it counts issues in this project that are visible to you. Children in other projects are not counted; on very large projects the page labels a partial rollup as such instead of claiming complete percentages.

Legal

License: the end-user license agreement (standard EULA) shown on the Atlassian Marketplace listing applies; Atlassian presents it during installation. Privacy: Atlassian apps privacy policy, with a dedicated section on Rollup Guard; the short version is in “Permissions and data” above. The app is not intended for covert employee monitoring or automated performance evaluation; see the privacy policy for details.