Filter for all child issues for a few chosen epic in a project

[Kaysaff Tal]

We are using jira Premium (advanced roadmap) and i created a plan with a few epics based on a label on each epic. it pulls 27 epics as it should. how do i add all child issues to the plan with put specifing all epic keys?

[Marc - Devoteam · Accepted solution]

Hi @Kaysaff Tal 

The above answer is likely AI based.

Epic Link is already replaced by Parent.

So the JQL would be: (Parent in (SELECTED_EPIC_KEYS) OR labels = "your-label")

Then you could add every new Epic to the list.

But why don't use a label on on relevant issues and use automation in the loop.

So if an Epic needs to be in the plan, just set the correct label on the Epic and create an automation to if the issue is a child of the Epic the label is copied to the child issue

The your plan simply needs a sources filter based on the label.

Automation example:

[Kaysaff Tal]

@Marc - Devoteam As i need to scale i think i will take your Idea :)

The Child_issue will inherit the label from the epic and will add to one unified plan.

what i dont understand is that there should be and expand hirerchy logic. that is why i am using "a plan" to begin with.

and when wanting to add sub-task it gets worse..

I really appreciate your detailed solution, i will implement it now hoping for a better Atlassian feature

[Kaysaff Tal]

hi @Harshit Grover  Thanks for the quick response :)

So , the issue with this solution (implemented by me as well) is that we have 27 epics, and every time we add one i need to add a label to it (makes sense) and add the child issues to the JQL.

this is not scaleable...

It sounds logical to me that Atlassian, that jave all the key I added to the plans, will implements an "pull" hierarchy solution.

Regardless "Epik link" is soon to depreceted switched to parent.

BTW this ability does exist in some Added plugins (Structure is the leading one)...So not sure why not OOTB for Jira.

[Harshit Grover]

Hi @Kaysaff Tal ,

• Make sure you have configure the Plan Issue Sources correctly. (like boards, filters, or projects) include all the child issues of the epics you want.)
• Check the hierarchy levels and ensure that the plan includes levels for child issues (e.g., stories, tasks, and sub-tasks or Epic>Story>Sub-Tasks) .
• If you're using a JQL filter to define the issue source, adjust the filter to include both epics with the specified label and their child issues. For eg use query such as : 

("Epic Link" in (SELECTED_EPIC_KEYS) OR labels = "your-label")

Regards,

Harshit