nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lookup issues on Level 2 Hierarchy Work type

deseymour

I have added a Level 2 work type in my hierarchy and would like to know if there is any JQL I could use to look up the work types within that Level 2 item. Currently, my hierarchy is

Theme - Level 2

Epic - Level 1

Task - Level 0

I am using the following as a lookup to find the Tasks within the Epic - "Epic Link" = {{issue.key}}

I need something similar to lookup the Epics in the Theme.

Accepted answers

Trudy P Claspill

Hello @deseymour

Based on the example you mentioned for Epics, you appear to be trying to get the child items of he Epic.

Is your goal to get the child items of the Themes?

If so the JQL would be:

Parent = <key for the Theme work item>

In Jira Cloud the Parent field is used at all levels to record that hierarchical parent of a work item. The "Epic Link" field has actually been included in a long term deprecation plan and you should switch to use "Parent" wherever you have used "Epic Link".

All comments

Trudy P Claspill

Hello @deseymour

Based on the example you mentioned for Epics, you appear to be trying to get the child items of he Epic.

Is your goal to get the child items of the Themes?

If so the JQL would be:

Parent = <key for the Theme work item>

deseymour

Again...you gave me what I needed. Thank you so much. I was trying to find the children of the Theme. But I didn't know if additional hierarchy levels would work the same way.

Thiago Wenceslau -Appfire-

I’m Thiago, a support engineer at Appfire.

If you are considering third-party apps, you could also take the search a step further with recursive search using JQL Search Extensions(JQLSE).

To automatically find all subtasks, epics, and linked issues down the entire project tree, you can use a special function called childrenOfIssuesInQueryRecursive. Just replace KAN-65 with your specific issue key in the format below:

issue in childrenOfIssuesInQueryRecursive("issuekey = KAN-65")

Screenshot 2026-05-28 at 13.28.29.png

If you want to combine multiple advanced queries together (nesting), JQLSE supports it with a quick two-step workaround:

Save your initial search query as a Filter (e.g., name it "My Base Search").
Reference that saved filter inside your final JQL search.

Please contact our support if you have any other questions about this.

Best regards, Appfire support team.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud