Searching with JQL

The app makes hierarchy relationships searchable via JQL (Jira Query Language). This lets you filter issues by their position in the hierarchy, combine hierarchy filters with standard JQL, and build dashboards or boards based on hierarchy structure.

Parent and child search

For the default hierarchy, these JQL search fields are available:

For additional hierarchies, the search field names follow this pattern based on the hierarchy name:

hierarchy{Name}Parent
hierarchy{Name}Children

Where {Name} is the hierarchy name with spaces and special characters removed, in camelCase. For example, a hierarchy named “Release Tracks” would have search fields hierarchyReleaseTracksParent and hierarchyReleaseTracksChildren.

Aggregated field search

Aggregated field values are also searchable. The search alias includes the hierarchy name to avoid ambiguity when the same field is aggregated across multiple hierarchies:

hierarchy{Name}Aggregated{FieldName}

For example, the “Story Points” field aggregated under a “Teams” hierarchy would be searchable as hierarchyTeamsAggregatedStoryPoints.

For custom aggregators, if you set an Index Path in the aggregator definition, you can search on that value with:

hierarchy{Name}{AggregatorName}

For example, the built-in “Progress” aggregator assigned to a “Teams” hierarchy would be searchable as hierarchyTeamsProgress.

Example queries

-- Find all issues that are children of PROJ-42 in the default hierarchy
hierarchyDefaultParent = "PROJ-42"

-- Find all issues that have PROJ-100 as a child
hierarchyDefaultChildren = "PROJ-100"

-- Combine with standard JQL
project = "MYPROJ" AND hierarchyDefaultParent = "MYPROJ-42" AND status != Done

-- Find Epics with more than 5 children
issuetype = Epic AND hierarchyDefaultChildren > 5

-- Find all issues without a parent (top-level in the hierarchy)
hierarchyDefaultParent is EMPTY

-- Find issues assigned to me that are children of a specific Epic
assignee = currentUser() AND hierarchyDefaultParent = "MYPROJ-99"

Using in boards and dashboards

Hierarchy JQL fields work anywhere JQL is accepted in Jira:

• Kanban and Scrum boards — Use a hierarchy filter in the board filter query to show only issues from a specific branch of the tree
• Dashboards — Create filter-based gadgets that show statistics scoped to a hierarchy subtree
• Saved filters — Save commonly used hierarchy searches for quick access

Next steps

• Aggregated Fields — Configure what gets aggregated and how
• Administration — Sync your data and troubleshoot issues