Issue links are a significant part of Jira functionality and might hold a lot of business logic. You may import linked issues, whether they are in the same or another project.
Every issue in a custom hierarchy has a place. The issue type is the main tool for how eazyBI asserts in which custom hierarchy level issue belongs, and custom fields for links state the order of hierarchy levels. Therefore I do not recommend building a custom hierarchy if you have the same issue type for more than one hierarchy level.
In your case, first, you might want to change the issue types for project “Programme”, use custom issue types to represent what those issues mean. For example, use issue type “Programme” and “Change Project” instead of Epic and Story.
Then you may build a new issue hierarchy representing your use case:
=>Programme
==>Change Project
===> Epic
====> Parent
=====> Sub-task
Then, follow the instructions with examples on how to build a new issue hierarchy: https://docs.eazybi.com/eazybijira/data-import/advanced-data-import-options/additional-issue-hierarchies 14.
Check out also Community topic on how to build a hierarchy with a similar structure (two additional levels above Epic): Looking to get all issues by initiative
Best,
Zane / support@eazyBI.com