Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Search child tickets based on parent condition

tpedriel March 21, 2024


Hello I want to create a board that brings tickets based on the parent condition: Epic label = PMO.

I've tried the following but is not working:

project = PMO or ISSUE IN issuesInEpics("labels = PMO")


Error: Unable to find JQL function 'issuesInEpics(labels = PMO)'.


Can you help me please? Thank you


3 answers

2 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 21, 2024

Hello @tpedriel 

If you are using only native JQL functionality in Jira there is not method to select children of Epics based on a filter to select the Epics. That would require a third party app.

There are several that extend JQL capabilities

Some provide functions that would provide the functionality you want.

Are you using any of those apps currently, or are you willing to consider getting an app to satisfy your need?

0 votes
Charlotte Santos -Appfire-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2024

Hi @tpedriel 

I’m Charlotte, a support engineer at Appfire and I’m here to help you.

Unfortunately, natively, you’ll not be able to do it dynamically.

In the app where my team works, JQL Search Extensions for Jira, you can use this query to get all issues whose epic parent has a specific label:

issue in childrenOfEpicsInQuery("labels = PMO")

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

We’ll be happy to help you!

0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 22, 2024

Hi @tpedriel,

just to expand on Trudy's answer, this is unfortunately trickier than one might think; as a hierarchical query, it would really require some kind of join or subquery, which isn't available in plain Jira/JQL.

A few directions forward:

  • If it's a one-off thing, you could first query the relevant epics, and then use the keys of these epics in a second query, in a "parent in (KEY-1, KEY-2, ...)" clause.

If you want to run your search dynamically, without manually "stitching" two queries together, you'll need extra tooling:

  • You might be able to use Jira Automation to propagate epic information down to the epic's children, and then use the respective field(s) on the children to include them into your filter. Obviously, this will add a fair bit of complexity to your system.
  • There's different apps from the Atlassian Marketplace that can help with that. As already mentioned, there's a number of apps that extend JQL by additional functions, including hierarchy-related functions. Scriptrunner and JQL Search Extensions are popular, but there are others as well.
  • Alternatively, you could try one of the more hierarchy-focused apps from the Marketplace. These apps typically have their own ways of figuring out parent/child relationships between issues, and provide more powerful ways of searching through issue hierarchies. I myself work on such an app, in which your query would be easy to solve - I'll provide more details below. I should add that these apps typically come with their own views, which may or may not work for your use case. 

Hope this helps,



Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 22, 2024

Just to expand on the last point, this is how this would look in the app that my team and I are working on, JXL for Jira. Put simply, you'd create a sheet with all issues that are potentially relevant to you, enable the default issue hierarchy (that's just one click), and then use JXL filtering capabilities to narrow down to the issues that you care about:


(I'm using labels here, but it would work the same way with any other field.)

Once you have your list of issues, you can work on these directly in JXL (much like you'd do in e.g. Excel or Google Sheets), trigger various operations in Jira, or export them for further processing.

Any questions just let me know!

Like tpedriel likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events