even issues with parent link appear in the "issues without parent" section in roadmap plan
Asked by Vaishnavi Kulkarni:

We use cloud; data Centre 9.4 version of Jira.

*** ** * ** ***

**Existing hierarchy of issues are as below**   
Outcome -\> Theme \& Objective -\> Initiative \& Key Results -\> Epics -\> Stories \& Tasks -\> Sub-Tasks

*** ** * ** ***

The parent-child relationship between these hierarchies are identified using either "parentLink" / "EpicLink" field.

In my advanced roadmap plan, I wish to display only issues which are linked all the way up top and remove those who are not part of this chain.

*** ** * ** ***

**I am trying to use below query**   
("Parent Link" is not EMPTY OR "Epic Link" is not EMPTY) AND project in ("X", "Y", "Z")

*** ** * ** ***

Under the "issues without parent" section in the plan, many issues WITH parent link are getting displayed still.   
What could possibly be the reason here? we do have multiple issueTypes in same hierarchy level, could this be a problem, if YES, then how do I resolve it?


Answers:
author: Dexter de Vera
body: Hi [@Vaishnavi Kulkarni](/t5/user/viewprofilepage/user-id/4433600) ,

You have issues without parent because of the filter you use. You need filter first the hierarchy you want to display.

ei. Hierarchy from Outcome to Subtask.

(Initiative \& Key Results) Issue 2 is child of (Theme \& Objective) Issue 1, The Issue 1 and 2 will count as without parent because They are not connected in Outcome Issue type.

if some of your issues dont have Outcome (with correct level of hierarchy) it will count as issue without parent". To prevent this make sure you tickets have the correct hierarchy.

If you only have Theme \& Objective as the top hierarchy of your issues, you must filter it by Hierarchy from Theme \& Objective to Subtask. If you missed any connection between you filter it will count issue without parent.

ei. Hierarchy from Theme \& Objective to Epics

(Epics) Issue 2 is child issue of (Theme \& Objective) Issue 1. The Issue 2 will count as without parent because there is a missing connection in your hierarchy (Initiative \& Key Results).

comments: author: Vaishnavi Kulkarni
body: Hi [@Dexter de Vera](/t5/user/viewprofilepage/user-id/4657717) thanks for your quick response, by implementing your solution, the issues in the same level of hierarchy are not getting aggregated, but rather has no much effect on the view.

> ((issuetype in (Objective, "Key Results", Epic) AND "Parent Link" is not EMPTY)  
> OR (issuetype in (Story, Task, Bug, "Tech Debt", Improvement) AND "Epic Link" is not EMPTY)  
> OR  
> (issuetype = Outcome AND "Parent Link" is EMPTY) )  
> OR  
> ((issuetype in (Theme, Initiative, Epic) AND "Parent Link" is not EMPTY) OR ( issuetype in (Story, Task, Bug, "Tech Debt", Improvement) AND "Epic Link" is not EMPTY)  
> OR (issuetype = Outcome AND "Parent Link" is EMPTY) ) AND status not in (Archive,"Won't Do")


author: Dexter de Vera
body: I mean filter button in timeline not the filter in Issue Source.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/272658i199A08635015BD78/image-size/large?v=v2&px=999 "image.png")


Tags: advanced-roadmaps

server