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

Child Issues do not appear on Parent Link

unknown

I have configured Portfolio for Jira with the hierarchy:

1. Initiative

2. Feature

3. Epic

4. Issues

I attached "Parent Link" field to my Epic issue types and linked the feature parent to multiple Epics but when navigating to that Feature parent I see zero child issues attached despite linking it that way in the hierarchy. Why wouldn't my epics appear as children to the Feature when Linked as parent??

Accepted answers

All comments

Andrew Morin

In the docs it looks like if you have the following it won't work. Putting link below...

If the epic link is set, you can't set a parent link.

https://confluence.atlassian.com/jiraportfolioserver026/showing-portfolio-custom-fields-in-jira-software-939497416.html

I know we have had some struggles with the Portfolio fields in our instance. More in using the advanced JQL for linked issues that comes with ScriptRunner.

Filip Pokorny

May be unrelated, but I'm experiencing similar issue: Some users can't see the child issues from the parent issue detail, but they can see the parent link when you open the child issue details.

I suspect the issue may be connected to permissions. For instance if your board displays issues from multiple projects and some users don't have access to both. I have to investigate a bit, seems like there isn't any info on the internet yet.

Env: Jira Server v8.5.5

Tiffany Ringenbach

We just experienced a similar issue where a few of the child epics were not appearing on an initiative. It turned out the missing child epics had originally been stories that were tied to a different epic but were changed into epics without removing the previous epic value, so the original epic appeared to have 2 epics as stories under it.

To fix the issue we changed the epics back into stories, removed the wrong epic, then changed them back into epics. After this the epics appeared in the initiative as expected.

Al Berjanskii

We experienced this issue recently.

Digging into our configuration it turned out we had two fields of type 'Parent Link', one was a custom field created more recently than the default field.

Issues that had BOTH fields displayed on their view screen were showing up in their Parent tickets child issues.

Issues that had only a single field on their view screen DID NOT appear in their Parent ticket's child issues section.

I permanently deleted the recently added 'Parent Link' type custom field and functionality returned.

Matteo Gioioso

Same bug

Josh Muir

@Filip Pokorny Same thing I'm experiencing. Did you ever resolve?

Filip Pokorny

Yes. In our case the problem was integration of the Advanced Roadmaps for Jira Server plugin. After the integration, every user not included in the Advanced Roadmaps access lost the ability to see children in the issue detail view. The solution was to include users to access the plugin.

Josh Muir

@Filip Pokorny Thank you so much for the response! I will look into this and confirm if it's fixes for me.

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

advanced-roadmaps