Parent link updated but Portfolio for Jira showing hierarchy and Jira Child Issue Field is empty
Asked by Stephen T:

I've installed Portfolio and configured my Hierarchy in settings so that the Issue Type called "Product Requirement" is at the highest above Epics (see below).

![PR hierarchy.PNG](/t5/image/serverpage/image-id/62577i60C715F075C15557/image-dimensions/328x174?v=v2 "PR hierarchy.PNG")

I then went ahead and updated the "Parent Links" for a few Epics to the desired "Product Requirement" issue key. (see below)

![Parent Link.png](/t5/image/serverpage/image-id/62578iCFE954AC60149A58/image-dimensions/404x354?v=v2 "Parent Link.png")

**However,** when I click into that parent Issue Type (e.g. PR-257), the "**Child Issues Section"** is completely empty (see below).

![Empty Child Issue.png](/t5/image/serverpage/image-id/62579iE13B051EE5F28221/image-dimensions/434x352?v=v2 "Empty Child Issue.png")

Any idea why this is happening?

Additionally, these hierarchy issue types **are not showing up in my Portfolio for Jira Plan either (see below)**

![Missing PR from Portfolio.PNG](/t5/image/serverpage/image-id/62581i36188C5538685ABC/image-dimensions/726x271?v=v2 "Missing PR from Portfolio.PNG")


Answers:
author: Dave
body: Removing my previous answer because it was incorrect - apologies for any confusion caused.

Regards,

Dave


author: Lara Arthur
body: I'm having the same issue and not finding any solutions. Is this a bug in Advanced Roadmaps? If so will it be fixed any time soon?


author: Tomorr Stasa
body: I am having the exact same problem.

Is it any solution for it?

Thanks


author: Stephen Hayden
body: How was this resolved?

comments: author: Stephen T
body: it has not been resolved


author: Earl McCutcheon
body: Hi Stephen,

Thanks for reaching out, and when it comes to data not showing up on a plan there are several items that can affect this.

First are you using a Next-Gen project type? If this is the case Portfolio does not currently support this project type and when using a Next-Gen project the parent/child mappings will break as well as some other features described here:

* [Portfolio for Jira next-gen support](https://confluence.atlassian.com/jiraportfoliocloud/portfolio-for-jira-next-gen-support-968663298.html)

If you are using a classic project type check out the following list that details some specifics for what items effect how the data shows up on the plan and would be the settings to look at first:

* I can see this one is not the case from your screenshots as the versions are visible but I am leaving this one here incase anyone else runs across this post on similar behavior, but the Fix version and affects version fields must be visible for the issues to show up
* Release assignments to a release that is excluded: If an issue is assigned to a fixVersion that is excluded from the plan, then the issue is not loaded (unless it also has another fixVersion assigned with is included). Things show up if they have either no version assigned, or they have at least 1 version assigned that is included.
* Filter permissions: Is the filter you are using is not shared with other users that try to access the plan, the other use will see a error when checking the issue sources in the plan configuration
* Issue Explicitly excluded before: if the issue has been explicitly excluded from the plan before, go to the plan configuration \> Issue Sources \> Edit sources, and check if the issue shows up as you go through the setup wizard again. if it was excluded, it will show up as unchecked in the table
* Unintended Filters in the UI - accidentally having any filter set on the plan, like for example the schedule range If something doesn't get scheduled it would not show up even though it exists.
* Hierarchy levels / mapping: Anything odd with which issue types are mapping to the hierarchy, exe was a hierarchy recently reconfigured or removed/re-added? try re-adding the parent link to the child issue on the plan and commit the change to clear this one up.
* Custom field configurations: have there been any changes to fields? Portfolio checks this field when loading issues to see if it's in an included or excluded assignment.

Let me know what you find.

Regards,  
Earl

comments: author: Lisa Schaffer
body: Hi [@Earl McCutcheon](/t5/user/viewprofilepage/user-id/502460)

I am having the exact same issue and I don't know why. I also removed the issue type, re-added it. In some cases I can see the hierarchy (in the Portfolio plan) and in others not. I have added ALL releases.

But, I am consistently NOT seeing the Child Issues list, but I can see the Parent Link populated on the Epic.

The Portfolio for JIRA version is 2.23 (data center) and JIRA is 7.12.3

Please help.

Thanks  
Lisa


Tags: advanced-roadmaps

hierarchy