Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

child issues not visible in parent-issue (advanced roadmaps)

Ariane Voorbeijtel Cannenburg April 30, 2021

We created 2 levels above the epic level, namely "initiative and theme". As a administator I can see all child issues (epics)  within the parent "initative"

 

But the other jira-users cannot. The epics and initiatives are located in the same project and wel all have the right permissions. We would like to have this view for all users of the project. 

 

 

 

4 answers

2 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 30, 2021

Hey @Ariane Voorbeijtel Cannenburg,

If possible, could you share a screenshot of what you and your users are seeing? I am currently thinking of 2 possible options:

  • In your advanced roadmap plan itself, make sure that the hierarchy levels being displayed are set correctly also for your users (so they are not accidentally filtering away the levels above Epics).
  • Maybe silly, but I've seen it happen before: make sure your users are not looking at the roadmap from the link in their project, but explicitly from your advanced roadmaps plan. These are different roadmaps and the one accessed from the left hand side navigation does not include the levels above epics.

Hope this helps - if not, happy to help based on a bit more information! 

1 vote
Rodolfo So August 19, 2021

Hi @Ariane Voorbeijtel Cannenburg 

Have you resolved your issue? .i've also encountered the same issue.

Appreciate your help on this.

Ariane Voorbeijtel Cannenburg August 20, 2021

Hi @Rodolfo So ,

Notice I have never gave feedback on the earlier mentioned solutions. We did figured it out and now I am crushing my brain what the reason was. I remember the child-issues didn't show up in the screen from the parent item. If I remember correctly it had to do with the permissions within Advanced Roadmaps. Not al users had permissions to see Advanced Roadmaps (this because we were experimenting with it).

So it was on system level, these users couldn't see the "plans" button on top either.

When we gave all jira-users the rights to at least see Advanced Roadmaps the issue was resolved

Hope this helps;)

Like # people like this
Rodolfo So August 22, 2021

Hi @Ariane Voorbeijtel Cannenburg 

 

Can you provide me screenshot what are the changes need to apply in the advanced roadmap permission? 

 

Thanks

Rodolfo So August 22, 2021

Hi @Ariane Voorbeijtel Cannenburg 

 

I've already added jira-users group under  advanced roadmap permission with advanced roadmap users but we are still facing same issue.

 

Thanks

Ariane Voorbeijtel Cannenburg August 23, 2021

@Rodolfo So Hmm that is a pitty. I cannot provide a screenshot because I do not have the rights to enter that part. If you already added the user to the right user group in roadmaps than I am afraid I cannot help you further! Hope somebody else can help you further; good luck

Alexander Allen April 11, 2022

Solved it for me!

0 votes
Svajunas February 3, 2023

If you add epic as the parent for the story this story does not appear as a child for the epic. For the rest of hierarchy levels it works as expected.

If you add any other issue type as the parent for the story it works as expected.

Atlassian should think how to unify existing epic functionality and advanced roadmaps hierarchy (for example displaying parent as epic is now displayed in the issue card in the backlog or board) so we don't have overlaping half baked features when using advanced roadmaps.

0 votes
Dave
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 1, 2021

Hi @Ariane Voorbeijtel Cannenburg ,

In addition to the suggestions from @Walter Buggenhout (which are both very good things to check!) I'm also wondering if everyone is looking at issues in the plan (i.e. as opposed to directly in the project) and whether or not you've committed those changes to Jira by using the "Review Changes" button within the plan and have saved them (assuming that you created them in the plan).

Screenshots or steps to reproduce this problem would definitely help!

Regards,

Dave

Suggest an answer

Log in or Sign up to answer