Advanced roadmap started displaying some epics and some stories as if they are without parent

[Ievgen Korshunovych]

About a month ago the project I was running had a roadmap without any issues but then one day we noticed a suspicious new number of issues without parents. I've looked into those and did not see anything changed there, they all had parent links but some of them displayed on the roadmap as "without a parent". Our roadmap is capturing hierarchy Initiative->Epic->(story, task, bug).

All of the epics are in different statuses among those without parents, only some issues of epic and story level are displayed like that, the majority are sitting fine within our hierarchy.

I've tried recreating the board, I have tried removing and adding parent links and nothing seems to help. I've checked all of those issues without a parent and they all have links to either an initiative in case of epic to an epic in case of story.

Building a filter around that data would be too much work since there are a lot of initiatives and epics and we have no spare time to invest in such a huge overhead.

Does anyone else have this issue?

Thank you

[Vijay Dhoot]

Any update on this?

[Crystelle S]

Question 1 - are all your queries exclusively in JQL? i.e. are you using any add-ons like scriptrunner?

Question 2- have any of the issue view permissions changed in any of the projects for these issuetypes?

[Ievgen Korshunovych]

1. No addons are used at all, all queries are exclusively in JQL

2. Nothing on the view permissions side has changed

Epics belong to one separate project which feeds the roadmap, some of the epics are showing up as without the parent but have a parent link to initiatives that also belong to the same project. The same situation is with some stories, which also have an epic link but are shown as issues without parents.

[Crystelle S]

Ok - next question: are you using the Resolution field for anything other than when the ticket is complete or canceled (i.e. the end state of the ticket) and what is the setting for how many days of resolved tickets to show in your Plan?

[Ievgen Korshunovych]

We use the resolution field to differentiate the reason an item is closed. 

30 days of resolved tickets to show in our plans.

In parallel with the advanced roadmap, we have created a basic one, and it seems like there are no orphan tickets displayed. We have tried recreating the advanced one in the past as well but it does not seem to help.

[Crystelle S]

Okay - I think you're at the point where you will want to open a support ticket with the Atlassian support team for Advanced Roadmaps. I've run you through all the end user possibilities I know of - unless anyone else has ideas I think you may want to touch base with someone that can take a look at your configuration in your instance. 

[Ievgen Korshunovych]

Ok, thank you, Crystelle!

Since there is some urgency to it, we'll roll with the native basic roadmap and if we decide to go back to advanced I'll have to look into this again.

[Meredith Bird]

Not sure if you ever received the answer to your questions, but...

I've seen "fake" orphans like this in Jira's Advanced Roadmap when the parent isn't included in the query results but the child is.  Advanced Roadmap treats those children as orphans in the plan, even though they aren't truly orphans.

I've fixed this by using the following syntax in my issue filters that feed Advanced Roadmaps, where "ABC-1" is the initiative or epic that's missing:

issuekey in portfolioChildIssuesOf(ABC-1)  OR  key = ABC-1

The challenge appears to be that the "issuekey in portfolioChildIssuesOf()" statement includes all the children *but* does not include the parent, so you have to separately specify the parent ID to be included in the issue filter as well.