HierarchyView

HierarchyView is a Forge app for Jira Cloud. Jira natively shows child issues only for Epics. HierarchyView adds a dedicated lookup page where you enter or search for any parent issue key — Feature, Initiative, Theme, Epic, or any custom type — and see every child issue in one table with a progress bar, scope tracking (original vs added work), and cancelled-issue handling. Classic Jira projects that use Epic Link instead of the parent field are supported via an automatic fallback.

HierarchyView runs on Atlassian Forge inside Jira Cloud. You need a Jira Cloud site with issues that use parent–child relationships (or Epic Link in classic projects). Follow these steps after installing from the Marketplace. Screenshots can be clicked to view full size; press Close, click outside the image, or press Escape to return.

1. Open the HierarchyView listing on the Atlassian Marketplace and click Try it free.

   

2. Choose the Jira Cloud site where you want HierarchyView, then click Review. On the Review screen, Atlassian shows trial and billing details for your site — click Install to finish. A Jira administrator may need to approve the app for your organization.

   

3. In Jira, open the Apps section in the left sidebar. HierarchyView appears under Your apps after installation — you do not need to configure anything in Jira project settings first.

4. Click HierarchyView in the Apps menu. The lookup page loads inside Jira.

   

5. In the Parent issue field, type an issue key (for example PROJ-42) or start typing a summary to search. Matching issues appear in a picker — click one to select it, or enter the key directly. Then click View.

   

6. HierarchyView loads the parent summary, a progress bar, and a table of child issues. Issue keys link directly to Jira. If children are found via Epic Link (classic projects), an info banner explains the source.

   

7. Optional for admins: open HierarchyView Settings from the link on the HierarchyView page (top right) or under Manage apps in the Jira sidebar.

   

   On the settings page, choose a project to mirror its issue types, enable types for upcoming features, then click Save Settings. Lookup works for any issue key regardless of these selections. See the Settings section below for details.

   

You are ready to use HierarchyView. To open it again later, go to Apps → HierarchyView, enter or search for a parent issue key, and click View.

After you load a parent issue, the page is organized in three main areas:

• Parent card — issue type, key (linked to Jira), summary, status, and description when available.
• Progress bar — percentage complete based on active children (cancelled issues excluded). Labels show done count, items added to scope, and cancelled count.
• Child issues table — one row per active child with type, key, summary, status, scope, sprint, story points, assignee, and priority. Cancelled children appear in a separate collapsible section.

Table columns are sortable. Large hierarchies paginate at 10 rows per page. Child issue keys open the issue in Jira when clicked.

HierarchyView tracks delivery progress the same way teams expect from Epic views, with extra scope awareness:

• Progress — calculated as done ÷ active children. A child counts as done when its Jira status category is Done. Cancelled children are excluded from both the numerator and denominator.
• Cancelled — children whose status matches common cancelled names (Cancelled, Won't Do, Declined, and similar) are moved to a separate section. Click Show cancelled to expand them.
• Scope — on first load of a parent, existing children are recorded as Original. Children created after that baseline (with a short grace window) appear as Added. The progress sublabel includes how many were added to scope, for example 3 of 8 done · 2 added to scope · 1 cancelled.
• Epic Link fallback — in classic Jira projects where children link via Epic Link instead of the parent field, HierarchyView automatically tries Epic Link when no parent-field children are found.

HierarchyView Settings is available to Jira administrators under Manage apps or from the link on the lookup page:

• Project picker — choose a project to display its issue type layout. This mirrors what you see under Project settings → Issue types.
• Issue types — enable Epic, scheme, and available issue types for upcoming HierarchyView features. Selections apply site-wide. Enabling or disabling types does not block lookup — any parent issue key still loads.

Click Save Settings after changing options. A confirmation message appears when settings are saved successfully.

Questions, bugs, or setup help? Email support@perpetualagile.com. You can also reach us through our support page for SLA details and Atlassian Support options.

HierarchyView runs on Atlassian Forge. For how we handle data, see our Privacy Policy. For security practices, vulnerability reporting, and incident response, see our Partner Security Policy.