Advanced Roadmaps not seeing Parent Link issues on plan

[Andrew Morin]

Maybe I am crazy but I have three separate projects that contain the issue types for Initiative, Program & Project as these issue types are shared across hundreds of projects in our Jira instance. When I load a board that has Epics linked to the what we call CHCAPABLTY project issue types which are at the Project level above the Epic and linked via the Parent Link field I see this in my plan. I thought any Parent Link issues would automatically load or am I mistaken? I cut off the screen shot but the Epic is the first one in the plan list and is clearly using the Parent Link.

[Kathy Dickason]

Has anyone figured this out? I'm having the same problem.  It's like the Parent Link field is ignored.  My Issue Sources filter includes the issues linked to in Parent Link.  My hierarchy is correct. 

[Mary from Planyway]

Hi @Andrew Morin 

It's Mary from Planyway roadmap for Jira

It sounds like you're using Jira to manage a complex project structure with multiple levels of hierarchy that go beyond the standard Epic-Story-Subtask model, by incorporating custom issue types like Initiative, Program, and Project. These custom types are used to organize work at a higher level than Epics. The Parent Link field, typically associated with Advanced Roadmaps (part of Jira Software Cloud's Premium plan or Jira Data Center), is used to link issues across different hierarchy levels.

From your description, it seems you expect that when you view a board or plan that includes Epics, the issues linked to those Epics via the Parent Link (in your case, Project-level issues from the CHCAPABLTY project) should automatically appear in the plan. However, you've noticed that these higher-level issues are not being displayed as you expected.

Here are a few points to consider and potential solutions:

1. Check Hierarchy Configuration in Advanced Roadmaps: Ensure that your hierarchy configuration in Advanced Roadmaps correctly reflects the structure you've described. Advanced Roadmaps allows you to customize the hierarchy above the Epic level. It's crucial that Initiative, Program, and Project issue types are correctly configured in this hierarchy to ensure they appear as expected in your plans.

2. Board Filter Configuration: The board's filter settings determine which issues are displayed. Make sure the filter query includes the issue types for Initiative, Program, and Project, or is broad enough to encompass all relevant issues. For instance, the filter should not explicitly exclude these issue types or be limited to specific projects if you want them to appear.

3. Parent Link Visibility: While the Parent Link field is used to establish a relationship between issues, the visibility of these linked issues on a board or plan might depend on the filter configuration and the hierarchy settings in Advanced Roadmaps. Ensure that the issues you want to appear are not being filtered out by the board or plan's filter criteria.

4. Permissions: Ensure that the users viewing the board or plan have the necessary permissions to view the linked issues. Permission schemes might restrict visibility of certain issues based on project or issue type.

[Matt Parks]

It's my understanding that the only issues that will show up in your Plan are the ones that are included in the 'Issue Sources' section of your plan, whether that's a Board, Project, or Filter. So, if you're pulling in the Epics but not anything higher up the chain, those higher level items won't be pulled in automatically.

Can you show what you're pulling in for the Issue Sources? And, if it's a filter, what is the JQL for that filter?