Hierarchy map visualisation

The Hierarchy map builds the structure based on issue link types and their direction (outward → inward).

Issue type hierarchy is not taken into consideration.

The structure is built from two or more issues (nodes). In each case, one issue is always displayed at the top (the source issue), and the other is shown below (the target issue).

Source issue: The issue that has an outward link to another issue is displayed at the top.
Target issue: The issue that is linked inward from the Source issue is displayed at the bottom.

Example:
If a Bug has an outward link to an Epic, then:
Bug is the Source
Epic is the Target
See the screenshot below:

Ordering of different link structures

The visual map that depicts the issue structures of different complexity automatically arranges them into three rows:

First row - Simple Relations (few linked issues)

When 2–3 issues are linked, they are grouped at the first row at the top of the map (see screenshot below - example 1).

Second row - Moderate Complexity (branching links)

When multiple source issues are linked to several targets and vice versa, the map builds a slightly more complex structure, expanding horizontally and it depicted in the middle of the map (see screenshot below - example 2).

Third row - High Complexity (densely interconnected issues)

When many issues are linked together in a dense network, the map displays a more complex structure at the bottom of the map (see screenshot below - example 3).