Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Child Issues do not appear on Parent Link

Deleted user Dec 23, 2019

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??

5 answers

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

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

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.

Like Josh Muir likes this

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

@Filip Pokorny Your solution worked for me! I was able to add the users to the 'Advanced Roadmaps Viewer' permission and the child Epics appeared to the users. Thank you again so much!

Here are the steps I followed:

  1. Navigate to Settings > Products.
  2. Select 'Advanced Roadmaps Permissions' on the left sidebar.
  3. Confirm user(s) or user group(s) in the 'Advanced Roadmaps Viewer' option.


Like Filip Pokorny likes this

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.

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. 

0 votes

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.

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events