Overview
Azure and Jira have a different approaches to item hierarchy.
While Jira allows for a three-level hierarchy (Subtask → Standard Work Item Issue Type → Epic), Azure does not restrict the number of hierarchy levels, allowing for unlimited Parent-Child relations in a single hierarchy tree.
Visual representation of Azure hierarchy depends on the chosen process and is up to 4 levels.
...
Azure → Jira: When Parent/Child link is added to mapped work item for a mapped epic in Jira, there is EpicLink created between those work itemsissues.
Jira → Azure: When work item issue is linked to an epic there is Parent/Child relation link created in Azure.
...
In order to synchronize subtasks user has to check Subtasks synchronization checkbox in Configuration > Mappings > Hierarchy and map corresponding work item type in Azure to subtask item issue in Jira.
Azure → Jira: When Parent/Child link is created in Azure from work item mapped to Jira subtask, there will be Jira subtask created.
...
This relation can link to either Epic (making this epic a child issue), Subtask (making this subtask a parent issue) or any work item issue in between.
When neither Epic nor Subtask synchronization is enabled, Items Multi-level-hierarchy synchronization section serves standard link synchronization only (with forced Parent/Child link on Azure side).
...
Configuration > Mappings > Hierarchy:
<img here>
Azure → Jira: When Related To link is added in Jira between Story and Feature (custom type), then in Azure, there will be Parent/Child link created between corresponding User Story and Feature.
...
Three-level Azure configuration (Basic Azure DevOps process)
<img here>.png?version=1&modificationDate=1635310684926&cacheVersion=1&api=v2&width=500)
Configuration > Mappings > Types:
...
Configuration > Mappings > Hierarchy:
<img here>
Four-level Azure configuration (Agile Azure DevOps process)
Configuration > Mappings > Types:
...
Configuration > Mappings > Hierarchy:<img here>
(For custom link relates to)
