How do I search a whole branch in JQL?

Use inComponentHierarchy("Auth") in the issue navigator — it returns every issue whose path is Auth or starts with Auth/, at any depth. If two nodes share a name, add the depth as a second argument: inComponentHierarchy("Auth", 2).

What happens when I rename or move a node?

Issues show the new name immediately — field values are linked to the tree, not frozen text — and JQL results are recalculated automatically, so no stale search results.

Does it work with Jira Service Management?

Yes. The Component Hierarchy field works on issues, create dialogs, transition screens, and JSM portal requests, so agents can file requests against paths like Catalog/Billing/Refunds.

Jira App

Component Hierarchy for Jira

Name: Component Hierarchy for Jira
Rating: 4.5 (50 reviews)

Jira components are a flat list — a poor fit for layered systems where Auth sits under Platform, and SSO under Auth. Component Hierarchy adds a parent-child tree: build it on a project page, pick a full path like Platform/Auth/SSO on each issue, and search a whole branch with one JQL function. Every node is a real Jira component, so boards, releases, and reports keep working exactly as before.

Get it on the Atlassian Marketplace User Guide

Free for up to 10 users · Cloud · Atlassian Marketplace

Features

Why teams choose Component Hierarchy

Parent-child component tree

Build the platform → module → submodule tree on a project page. Every node is a real Jira component — boards, releases, and reports keep working.

Cascading picker on issues

Pick a full path level by level — Platform/Auth/SSO — on issues, create dialogs, transition screens, and JSM portal requests.

Subtree-wide JQL function

inComponentHierarchy("Auth") returns every issue on or under a node, at any depth. Replace fragile component in (...) lists that rot as the tree grows.

CSV import & export

Bulk-build the tree from a Name,Parent CSV, export it as CSV or JSON, and sync every node to a matching Jira component with one click.

Getting started

How it works

1
Build the tree
Open project sidebar → Apps → Component Hierarchy and add nodes. Existing components with matching names are adopted, not duplicated.
2
Pick a path on an issue
The Component Hierarchy field is a cascading picker: choose level by level, store the full path. Setting it adds the node components to the issue automatically.
3
Search whole branches
inComponentHierarchy("Auth") matches a node and all its descendants. Combine with any other JQL, and results stay correct after renames and moves.

FAQ

Frequently asked questions

Yes. Creating a node creates a Jira component with the same name, existing components are adopted when names match, and setting the field on an issue adds the node components to it. Boards, releases, and reports that filter by component keep working.

Learn more

Guides & tutorials

Jira Component Hierarchy

Scenario solutions

Part of these solutions

Organize Jira Components into a Tree

Jira components are a flat list — fine for three entries, unusable at fifty. Learn how to give components a parent-child tree and search whole branches with one JQL clause.

Explore more

Modern Numbered Headings for Confluence

Professional table of contents with 5 numbering styles

Raw Storage Source Editor Pro for Confluence

A powerful app that allows you to directly edit the raw storage format (XML) of Confluence pages

Raw Storage Source Editor for Confluence (Free)

A powerful app that allows you to directly edit the raw storage format (XML) of Confluence pages

Ready to try Component Hierarchy for Jira?

Install from the Atlassian Marketplace. Free for up to 10 users.

Get it now