How to view your
Jira work in a tree

The right choice depends on your task. Scheduling a release calls for dates and dependencies. Reading the work below an epic calls for a clear list of children. These are related needs, but they do not require the same interface.

Start with the hierarchy Jira already has

Jira’s default hierarchy has three levels: epics, standard work items, and subtasks. Stories, tasks, and bugs are examples of standard work items. They normally sit alongside one another, rather than forming a chain from story to task to bug. See Atlassian’s explanation of work types.

Imagine a small team improving a checkout flow. An epic represents the wider effort. A story describes a customer-facing outcome, a task covers implementation work, and a bug tracks a defect. Subtasks break a standard work item into smaller pieces.

A hierarchy is also different from a link. Two issues can be related, or one can block another, without either becoming the other’s parent. Before choosing a visualization, check whether you need parent and child nesting, dependency links, or both.

Viewing hierarchy is not configuring hierarchy

A tree view displays relationships. Configuring hierarchy changes which levels and parent relationships your Jira setup supports. Opening a different view does not create an initiative level, place tasks beneath stories, or change your organization’s work types.

Cascade’s tree is a browsing interface for existing work. Do not treat it as a hierarchy configuration tool or a promise of arbitrary levels above epic.

Check Jira’s native options first

Jira already has several ways to inspect and organize work. Availability and labels can vary with your plan and space configuration. Atlassian’s current documentation often says “work item” where you may be used to “issue.”

Timeline: useful when dates matter

The Jira Cloud timeline can show parent work and the standard-level children below it when child planning is enabled. Atlassian documents this as level 1 and level 0; its child-planning documentation says the subtask level is not shown. This is useful for scheduling, but is not the same as browsing every level of an issue tree. See child work item planning on the timeline.

Plans: a broader planning context

Jira Cloud Premium and Enterprise include advanced planning features. In a plan, the “Show full hierarchy” filter option can retain children belonging to filtered work items even when those children do not match the filter. This is worth checking if your team already works in Plans. Atlassian explains how hierarchy and filters work together.

List: a straightforward field-based view

The native list is useful for scanning, sorting, creating, and editing a space’s work. If your immediate question is who owns an issue or which status it has, that may be enough. See Atlassian’s overview of the list view. Choose by the workflow you need, rather than assuming every task needs a tree.

When a browser-based tree view is useful

A tree helps when context matters more than dates. You might want to read all the work below an epic, understand which subtasks belong to a story, or inspect a detail without losing the surrounding list.

For a developer, that can mean reviewing an assigned issue in the context of its parent. For a team lead, it can mean checking related work together. A project manager or business analyst may find the same arrangement useful when reading scope and acceptance criteria.

Filtering introduces a trade-off: a shorter result list is easier to scan, but removing parents can hide context. Keep that distinction in mind when interpreting any filtered view. A matching issue is not necessarily a complete picture of the work around it.

A practical workflow with Cascade

1. Install from the official store listing. Cascade is a Chrome extension for Jira Cloud, not an Atlassian Marketplace app. Check your organization’s extension policy first.
2. Open your Jira Cloud workspace. Cascade uses your existing signed-in session; it does not require a separate Cascade account or API token.
3. Click the floating Cascade button. On the Jira page, it first appears along the right edge. Cascade opens in your Jira tab, starting on “Assigned to me.” From there, stay with your assigned work or choose epics, then browse their issue trees. Use search and filters to focus on the work you need.
4. Inspect the details. Open an issue’s detail pane to read information and comments while retaining the surrounding context.
5. Review supported changes or export. Update indicators and supported diffs answer a different question from current issue details. For spreadsheet work, download CSV or copy the current view for Excel. Some of these, such as indented export, are planned for Cascade Pro and are free for everyone during early access.

×

The Cascade homepage includes a screenshot walkthrough and answers about access and privacy. Review those before deciding whether the extension fits the way you work.

Know the boundaries

Cascade is intended for Jira Cloud on atlassian.net in Chrome. This guide does not promise compatibility with Jira Server, Data Center, every browser, or Jira Product Discovery. Product Discovery’s ideas and discovery workflows should not be assumed to follow the software issue workflow described here.

Jira administrator installation is not needed according to the store listing. Employer-managed browser policies can still restrict installation. The extension also works within your existing Jira access; it is not a way to view work you do not have permission to see.

The Inbox starts from installation and does not recover an earlier notification history. Supported description and acceptance-criteria diffs should not be confused with a complete historical audit of every field. Likewise, a hierarchy export preserves the current view’s structure; it is not a replacement for portfolio planning.

According to the extension privacy information, processing and caching are local, with normal requests to your Jira instance. Exported files and anything you copy remain your responsibility to store and share appropriately.