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; } } }

To get child issues in my Jira Plan

Riyas Khareem

Team,

I am setting up a new plan for my project where I am listing all approved roadmap epics from one filter.

But I do not see any child issues under each epic. I verified the hierarchy filter that is showing from "Epic" to "Story"

How do I get this? Any help?

Accepted answers

shib saha

Hi @Riyas Khareem , Check the filter once, does it only include epics or all the work items like epic, story, task etc?

Plan hierarchy is for the work item included in the plan, it can not show the work items which is not getting populated in the plan.

Note: Adjust the filter to include the stories as well. Thanks

All comments

shib saha

Hi @Riyas Khareem , Check the filter once, does it only include epics or all the work items like epic, story, task etc?

Plan hierarchy is for the work item included in the plan, it can not show the work items which is not getting populated in the plan.

Note: Adjust the filter to include the stories as well. Thanks

Riyas Khareem

Is there a way to retrieve all child issues from a filter where I have a list of epics? The reason for this is because the epic filter comes from a different team and it is subject to change/update based on their priorities.

Trudy P Claspill

Hello @Riyas Khareem

Only people with Edit permissions for the filter can change what it retrieves.

Can you share with us the details of the filter?

Natively Jira provides a couple of JQL functions for searching for child items, as documented here:

https://support.atlassian.com/jira-software-cloud/docs/search-for-advanced-roadmaps-custom-fields-in-jql/

If the filter has an explicit list of Epics, then the filter can be modified to get the child issues in those Epics. The available native functions for getting the children require that the parent issue keys be explicitly listed.

If the filter uses criteria to select the Epics implicitly, such as criteria to get all Epics that have a Component value of X, Jira does not provide a native function that can be used to get children of Epics based on a filter that selects the Epics; i.e. this is not supported:

issue in "Parent Link" in ("Component=X")

Doing something like that would require a third party app that extends the capabilities of Jira filtering.

Riyas Khareem

Thank you. As a work around, I made a copy of the filter and added child issues to it to reflect in my plan.

However there should be a way in future that will apply a Jira plan look to for child issues or at least an option to choose child issues.

Olga Cheban _TitanApps_

hi @Riyas Khareem ! I see you already found a workaround for your issue, even if not a perfect one.

As an additional tool for viewing complex work hierarchies, I can recommend our solution, Smart Hierarchy for Jira. It shows you all your work items in a compact view with a progress bar and details for each task. Currently, it doesn’t support filters, but it still can be useful in some cases.

Here's an example: an epic with stories, subtickets, and checklists. However, the solution works with any work types, including custom ones.

Screenshot 2026-01-05 at 12.23.29.png

Please let me know if you have any questions!

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