The Links Hierarchy app shows data from the root issue perspective.
Circular linked issue structures (like the one shown below) would produce infinite hierarchical structures.
To avoid this, Links Hierarchy loads issues once only per branch. This makes finite hierarchies.
However, the displayed issues could have different context (different ways to be linked to the structure). In large hierarchies, users could be confused by missing those removed circular issues if they were not painted.
Therefore the app includes circular issues as duplicated issues to ensure that all the issues in the structure have the same context (linked issues) regardless their location.
However, duplicated issues cannot be expanded to avoid infinite hierarchies.
Example: Hierarchy below shows that issue TALH-9 is duplicated (we can access to issue from different locations as it belongs to Epic TALH-6, it relates to TALH-10 and is an Subtask ).
...
Therefore the same link is duplicated in the hierarchy and the app uses an special icon
...
(in the more depth levels to highlight this) and those issues cannot load more data to avoid infinite hierarchies.
Displaying duplicated issues is important in large hierarchies as not all the data can be seen at a glance. Therefore duplicated issues must be depicted, otherwise the users would miss them and full context would be reduced everywhere.
...